Hi All,

This is my first document in the forum. So please go through this and provide your valuable comments on this.

We create a new tax codes with revised rates and the old tax codes no longer useful for posting. But these tax codes will display in the input help while invoice posting through MIRO,FB60,F-43,FB70 etc. Due to this the users will get confused and also might chance to select the wrong tax code for posting. To over come these type of errors SAP has provided 2 SAP Notes i.e.2074351 & 2095960.

As per note 2074351, first we have to implement the note 2095960. After done this, we have to execute the report NOTE_2095960 as mentioned in the note 2074351. The screen shot of the report execution attached here:

Here you have to run the report step by step as mentioned in the above screen shot. After successfully done this, you have to implement the note 2074351. Then after if we check the t.code FTXP, the new field will appear as mentioned in the below screen shot.

If you select the check box, then it no longer display while posting. For details you go through the above mentioned notes.

BR

Mukthar N

Hello all,

I want to share with you a new scenario that you could face during the SFIN migration.

You are executing SFIN Migration:

a) FINS_MIG_MONITOR_RC0

b) FINS_MIG_MONITOR_RC1

And you are receiving error message F5557 - "Local currencies for company code && cannot be completely determined

If you ignore this message you will receive message FINS_ACDOC_POST002:

The cause for this error is that the currency type of controlling area '20' is assigned to the company code as parallel currency in FI (Tcode OB22) and CO (TCode OKKP).

For this scenario we can have 3 resolution scenarios:

Solution 1) Use currency type 30 for the controlling area. Currency Type 30 is supported by both FI and CO, and you get integrated amounts for both application in your universal journal. (recommended setting).

Solution 2) Use another currency type  - currency type  40 - , which is supported by both applications FI and CO, if the currency key of currency type 30 does not fit to all controlling areas.

Solution 3) Use currency type 20 in the controlling area. But this is then an "CO-only" amounts in the universal journal, which we allow for compatibility reasons. This is not the recommended setting. In all line items, with G/L Accounts, which are is not a cost elements,   the amount in currency type  20 will be 0.

Solution 1) or Solution 2) is the better choice and recommended by SAP. But if you want keep with Solution 3 you should apply the corrections of note 2187380. With this note you can use currency type 20. But the amount will be filled in cost elements only.

For Solution 3 follow the steps:

1)     Apply the corrections of note 2187380.This note will avoid inconsistences in the future.

2)     Check in SE16 the of table T001A. In T001A you should not find any entry which has currency type '20' assigned. All values should be empty (no parallel currency used).

3)     Check it with SE16  table FINSC_LD_CMP, if the record for Ledger 0L and Company Code contains space in field CURPOSK. (Currently there is '2' in this field.)

I hope this content can help you when you are planing your migration. It is important check you CO/FI customizing before the migration.

Kind Regards,

Raquel

Hello Experts,

This is my first blog post, hence may be it is not perfect but I am ready for your inputs/suggestions for future improvements.

Issue/Observation: While posting customer credit memo in FI (FB75), payment term has no influence to calculate net due date.

System Behaviour: Net due date calculation will be done based on input parameter of field "Inv.ref." under "Payment" tab:

Generally, following will be the business requirement:

• Net Due Date based on Invoice: FI document number of an invoice to be entered in "Inv.ref." field to derive "Baseline Date", "Payment Term" and "Net Due Date" from invoice.
• Net Due Date based on Payment Method: "V" to be entered in "Inv.ref." field to "Net Due Date" as "Baseline Date" + "Payment Term".
• Net Due Date as Baseline Date: Keep "Inv.ref." field blank to calculate "Net Due Date" as "Baseline Date".

Update "Net Due Date" in already posted documents: Select all credit memos in FBL5N > Environment > Change document > update the field "Invoice ref." > + Next  item (Ctrl+F1) > Save (Ctrl+S).

Best Regards,

Chirag Panchal

Hi guys, this is my first blog in the community here.  This time I will share my experiance for resvoling CK466 error which puzzled me a lot once before.  I was serach CK466 in this community and found quite often questions casued by missing activity price in KP26.  In this case, you can use COFC to postprocess the CO document when you update price without reverse previouse confirmation.

However still some CK466 casued by mistical reason behind.  The solution given by the blog is not only valid for CK466 also valid for other CK errors during confirmation process.

Once we confirm the order, the correspondence CO document will be generated at the same time. The following prerequisites must be fulfilled for logistics so that Controlling documents (CO documents) can be created during a confirmation:

• The order must have a costing variant for actualcosts (field CAUFVD-KLVARI).
• The confirmed operation must be relevant to costing (T430-KALKZ = "X"). This indicator is set in the operation control key.
• The order itself must have the "fully relevant to costing" attribute set (AFVGD-SELKZ = "X"). This indicator is copied from the routing and cannot be changed in the production order. For this, refer to SAP Note 378052, if necessary.
• The confirmed operation must have a work center.
• The work center must be assigned to a valid cost center.
• In the work center, a valid activity type as well as a formula must be defined for every activity whose costs you want to determine.
• These activity types also have to be specified accordingly in the order operation.
• For the activity types used in the work center, the prices must be maintained for the cost centers of the work center (transaction KP26).
• The confirmed operation must not be an external processing operation.
• During the confirmation, you must enter activities.

For example,CK466 error occurred may due to different reason, one of them is due to plan price set too small.

e.g.cost center1074502 with activity type 74RM1 in 2016 01, the price in object currency is CNY 0.05. With the exchange rate, the price in controlling area is CHF 0. This will cause error CK466 happens

Then you can use  either transaction CO1P or the report CORUPROC to post CO document.

The other reason may due to activity type is changed or of which valid date is not fitable.  For example, the valid period of activity type defined in work center is bellowing:

However, the order planning cost was occured during order creation on 16-Dec-2015

As a result, no valid activity type is copied into order :

The planning cost of order had no value of activity.  During the confirmation, the CK466 occured due to no valid actitity type used.  You can apply SAP note 162906 which is forced that during the determination of actual costs in general the activity type of the work center valid for the posting date is used. Thus, the activity documented in the activities of the order is used only for the standard cost estimate but not for the actual costing.

How to find out root cause of actual costing errors and resolve it? You can check the following

1. Have errors occured in the actual-cost calculation for the confirmation? If this is the case, you must use transaction COFC to postprocess the incorrect records. The table AFRC contains the incorrect records.
2. The actual-cost calculation may be processed separately from the confirmation. You can set this separation in the Customizing for the confirmation (transaction OPK4). You can enter a process control key in the "Process Control" field to specify that the actual costs are to be calculated in the background. If this is the case, the system writes only future change records to the table AFRP3 for the confirmation. You can use either transaction CO1P or the report CORUPROC to post these future change records. However, a decoupling of the actual costs is not possible in case of:
   1. Run schedule header
   2. Header confirmation
   3. Cancellation

If errors occur in this case, error records are again created for them for the reprocessing.

If you want to change CO document posting date due to some reason, you shall use program 'ZAFRC' to further process.

Program 'ZAFRC' provides the following functions:

• Issuing errors of the calculation of actual costs in a list. Every error occurred is listed only once.
• Transferring error records into an indicator table and deleting the error records.
• Changing the posting date in the confirmation.You should only use this option if error records of the calculation of actual costs are in the blocked posting periods.

Parameter:

You can execute program ZAFRC in the test mode (parameter 'TESTRUN'). No database changes are made in this mode.

The number of the records to be edited can be entered into parameter 'NUMBER'. On the one hand, you can divide into portions, on the other
hand, you can test with a small dataset (for example, 1) first. This procedure is highly recommended by SAP!

If you want to change the posting date, you must enter the new posting date into parameter 'PDAT_NEW'. All records are changed for which
its date is before the date entered into parameter 'PDAT_TO'. We recommend to select the date in field 'PDAT_TO' so that every earlier date falls into a
completed posting period. You must always enter parameters 'PDAT_NEW' and 'PDAT_TO' together. Remark: the changing of the posting date has no effect on the reprocessing of failed goods movements via Transaction COGI. After run, the new posting date will be update:

If all costs errors are issued in a list, you must enter parameter 'PROTOCOL'.

You can restrict the processing to certain order types (for example, network) via parameter 'ORDERTYP'

3.Have you changed activity types or the work center of the confirmed operation after releasing the order? When you create an order, the system copies activity types that are valid at this time from the work center. Nevertheless, if you create confirmations at a point in time at which the validity is expired or work center data was changed manually, the determination of actual costs occurs with the original activity types in the order. Therefore, the confirmed activities are either incorrectly valuated, or a valuation cannot occur because the activity type is no longer valid in the meantime.

You can subsequently update the data if you change (and save) the work center in the production order for a short time and immediately reset it
to the original work center. The subsequent confirmation then generates the updated data and activities.

If confirmations were made for the wrong activity types then you must take account of the following:

In general the confirmations should be cancelled in the production order before the work center is changed. The work center is then updated using the procedure mentioned above. Then the confirmations have to be created again.

CAUTION !!!

If confirmations have mistakenly been created for activities for which no costs have been calculated - for example because no activity types
were maintained in the work center - then the confirmations must be cancelled before changing the work center in the production order! Otherwise when you
cancel the confirmations negative costs are generated! Only then can the confirmations be created with the corrected activities.

4.If you confirmed to a different work center than you have planned, this work center would be proposed for this operation during all further confirmations. For example, if no activity types are assigned to this work center, no costs will be posted during the confirmation although costs could have been planned.

5.Have you changed the attributes of an operation control key involved in the Customizing after creating an order? Example: When
you create an order, an operation is not relevant to costing because of its operation control key. This is noted in the operation data (AFVC-SELKZ = " "). If you change the operation control key in the Customizing afterwards so that it is relevant to costing, this information cannot be transferred to the orders involved. If you enter a confirmation for the corresponding order, no costs will be posted.

If you want to further check program, you can refer bellowing :

Branching from the confirmation to CO:

You call the form routine DET_CONF_COST (LCORFFD1 or LCORFF40) in the function module CO_RU_CONF_POST.

No reprocessing possible using transaction COFC:

When you enter confirmations via the time sheet (CATS), you could transfer times that are in a locked posting period. You can display these
records in transaction COFC after the transfer. For these records, you must either reopen the posting period or change the posting date in the confirmation
records as specified in SAP Note 212705 or in SAP Note 301574.

Debugging help:

Subroutine DET_CONF_COST (LCORFF40):

• Check whether the actual costing variant is set:

* Istkostenermittlung nur wenn "Kalkulationsvariate Ist

* gesetzt" ist

          CHECK NOT CAUFVD_TMP-KLVARI IS INITIAL.

• Dynamic call of CO, usually a call of function module CK_F_ACTUAL_COST_CALC

*  CO-Baustein zur Kostenermittlung aufrufen

CALL FUNCTIONTKOMP-FUNCTION

        EXPORTING            
CAUFVD_IMP = CAUFVD_TMP

PROTOCOL  = SPACE

        EXCEPTIONS           
NO_COSTING = 01.

Function module CK_F_ACTUAL_COST_CALC (LCK00U05):

• Repeated check whether an actual costing variant exists:

* Keine Kostenermittlung ohne Kalkulationsvariante

PERFORM CHECK_KLVAR USING CAUFVD_IMP-AUART

CAUFVD_IMP-KLVARI

SYSUB.

• Call of function module CK_F_AFRU_AMOUNT_CALC. This function module sets up the internal table KALKTAB. This table contains all activities
  whose costs are to be determined.

* KALKTAB-Einträge zu Rückmeldungen generieren.

  CALL FUNCTION 'CK_F_AFRU_AMOUNT_CALC'

      EXPORTING       
CAUFVD_IMP  = CAUFVD_IMP

          
CKCOUEB_IMP = CKCOUEB_HDR

         
OPS_SETTEL  = VORGANGSKONTIERUNG

      EXCEPTIONS

            NO_ENTRY =01.

Function module CK_F_AFRU_AMOUNT_CALC (LCK01U06):

• Check whether a work center was entered for the confirmation.

* Arbeitsplatz gesetzt ?

    CHECK NOT AFRUD_TMP-ARBID IS INITIAL.

• Only take operations into account that can be determined. The "relevant to costing" indicator (T430_TMP-KALKZ) comes from the operation control key.

* Nur kalkulierbare Vorgänge

    CHECK NOT T430_TMP-KALKZ IS INITIAL.

    CHECK NOT AFVGD_OPR-SELKZ IS INITIAL.

• Check for external processing

* Fremdbearbeitung obligatorisch ? Oder optional und

*  keine Eigenbearbeitungsdaten ? Dann abbrechen.

    CHECK (T430_TMP-LIEF IS INITIAL ) OR

          (T430_TMP-LIEF = 'X' AND

          ( NOT AFRUD_TMP-ARBID IS INITIAL ) ).

• Check whether the actual work center confirmed has a cost center assigned.

IF RCR01_TMP-KOSTL IS INITIAL.

  CALL FUNCTION 'CM_F_MESSAGE'

      EXPORTING

            ARBGB =C_MSGID

            MSGNR ='282'

            MSGTY ='E'

          MSGV1 =AFRUD_TMP-WERKS

            MSGV2 =RCR01_TMP-ARBPL

      EXCEPTIONS        
MESAGE_TYPE_NOT_VALID = 01        
NO_SY_MESSAGE = 02. Der Arbeitsplatz <(>&<)> hat keine Kostenstelle  RAISE NO_ENTRY.

    ENDIF.

Hello all,

SAP note 2083799 provides a composite scenarios involving posting with Accounting BAPIs. But I want to share with you more details related foreign currencies scenario:

The currencies are maintained in transaction OB22 for each company code. You can also see the 2-digit currency type keys here, which are used in accounting interface as well.

Currency type = 00 (document currency) and Currency type = 10 (local currency) are the only real hard-coded keys. You can also see this in OB22, as you cannot change the currency type key for local currency. For 2nd and 3rd local currency, the value depends on the kind of currency you are using. You can find a complete list of the different currency types in SE11 by checking the value range of the domain CURTP.

You see in currency type that basically it always ends with a 0. So the typical values are 10, 20, 30, 40... You also have a valueation field directly underneath with a single digit. This can indicate legal valuation, profit-center valuation and so on. For FI only legal valuation is relevant. If another valuation is maintained, then this value in valuation field will be added to currency type. So you can have a customizing like this:

2nd LC, Currency Type 30, Valuation 0 – legal valuation, currency USD
3rd LC, currency type 30, valuation 2 – profit-center valuation, currency USD

In this case LC2 would be currency type 30 and LC3 would be currency type 32. Only LC2 would be transferred to FI. LC3 would be relevant for profit-center accounting. Eventhough the amounts in LC3 are not relevant for FI, they are determined in FI-Interface (function FI_DOCUMENT_CHECK) if they have not been passed to accounting interface.

You do not have to provide the local currency amounts to accounting interface. Only the document currency is mandatory. But of course you CAN submit local currency to accounting (as MM does for example) then only the missing local currencies are determined in FI-Interface. Only important fact is: IF you submit at least one local currency, you should submit it in all line items and not just at single items. Otherwise a balance issue can occur.

More information on correct setup of OB22 is listed in note 335608.

I hope this helps!

Regards,
Raquel

Hi all,

We already have new notes just released for 1099 reporting, where Print Forms Layouts in Smartforms and PDF format are available.

Two notes are available:

2227185 - US Legal Change 2015 - 1099 and 1042 Smartforms and Adobe Forms (600 and above)

2227186 - US Legal Change 2015 - 1099 and 1042 Smartforms and Adobe Forms (current releases).

Those notes are the main notes which will contain the relevant details to be adjusted in order to correct and update 1099 and 1042 report including Smartform and Adobe Forms.

The major changes include:

1. 1099INT - Box 13 "Bond Premium on tax-exempt bond", "FATCA filling requirement" checkbox introduced and year changed to 2015;

2. 1099MISC/MISC1- "FATCA filling requirement" checkbox introduced and year changed to 2015;

3. 1042S - Numbering of the boxes are changed and year changed to 2015;

4  1099G - year changed to 2015;

5. 1099K - Box 1b is renamed and year changed to 2015.

Also notes containing the newest changes for 1099 Files were released:
2250865 - US 2015 LC - 1099 File Changes
2250866 - US 2015 LC - 1099 File Changes ( for lower releases).

Please follow up on those notes for latest updates about 1099 and 1042 updates for the Tax Year 2015 to be submitted in 2016.

I hope it helps to address you your concern about this subject.

Danton Prestes.

Hi all,

When scheduling the payment run, error message F0250 is generated 'Job scheduling terminated; read SYSLOG for details'. However, there is no corresponding entry in the SYSLOG and you have already performed the recommendations from SAP Note 170429.

In this case, the issue may be happening due to the incorrect print parameter setting for user XXXXX , where the storage mode is set to Archive only.

Please, set the storage mode to print only for user XXXXX which should resolve this issue.

Ask the user to follow the exact same procedure to revert the "Archive only" setting. This is what she/he should do:

- Display any list on the system

- Go to System -> List -> Print

- Set an output device name

- Click on 'Properties'

- Open the 'Output Options' folder

- Double click on 'Storage Mode'

- Change to "Print only"

- Click on 'Specifications'

- Make sure that the option 'Valid for all reports' is selected

- Both the 'Dialog' and 'Background' checkboxes should be on

- Click on 'Copy settings'

- Then confirm all the changes.

As alternative, Please execute the program RSPRIPARCOPY to copy the default print settings from any user to the affected user. This should overwrite the 'Archive only' setting in that user."

Best Regards,

Carolina

Hello all,

SAP note 2083799 provides a composite scenarios involving posting with Accounting BAPIs. But I want to share with you more details related foreign currencies scenario:

The currencies are maintained in transaction OB22 for each company code. You can also see the 2-digit currency type keys here, which are used in accounting interface as well.

Currency type = 00 (document currency) and Currency type = 10 (local currency) are the only real hard-coded keys. You can also see this in OB22, as you cannot change the currency type key for local currency. For 2nd and 3rd local currency, the value depends on the kind of currency you are using. You can find a complete list of the different currency types in SE11 by checking the value range of the domain CURTP.

You see in currency type that basically it always ends with a 0. So the typical values are 10, 20, 30, 40... You also have a valueation field directly underneath with a single digit. This can indicate legal valuation, profit-center valuation and so on. For FI only legal valuation is relevant. If another valuation is maintained, then this value in valuation field will be added to currency type. So you can have a customizing like this:

2nd LC, Currency Type 30, Valuation 0 – legal valuation, currency USD
3rd LC, currency type 30, valuation 2 – profit-center valuation, currency USD

In this case LC2 would be currency type 30 and LC3 would be currency type 32. Only LC2 would be transferred to FI. LC3 would be relevant for profit-center accounting. Eventhough the amounts in LC3 are not relevant for FI, they are determined in FI-Interface (function FI_DOCUMENT_CHECK) if they have not been passed to accounting interface.

You do not have to provide the local currency amounts to accounting interface. Only the document currency is mandatory. But of course you CAN submit local currency to accounting (as MM does for example) then only the missing local currencies are determined in FI-Interface. Only important fact is: IF you submit at least one local currency, you should submit it in all line items and not just at single items. Otherwise a balance issue can occur.

More information on correct setup of OB22 is listed in note 335608.

I hope this helps!

Regards,
Raquel

Hi all,

We already have new notes just released for 1099 reporting, where Print Forms Layouts in Smartforms and PDF format are available.

Two notes are available:

2227185 - US Legal Change 2015 - 1099 and 1042 Smartforms and Adobe Forms (600 and above)

2227186 - US Legal Change 2015 - 1099 and 1042 Smartforms and Adobe Forms (current releases).

Those notes are the main notes which will contain the relevant details to be adjusted in order to correct and update 1099 and 1042 report including Smartform and Adobe Forms.

The major changes include:

1. 1099INT - Box 13 "Bond Premium on tax-exempt bond", "FATCA filling requirement" checkbox introduced and year changed to 2015;

2. 1099MISC/MISC1- "FATCA filling requirement" checkbox introduced and year changed to 2015;

3. 1042S - Numbering of the boxes are changed and year changed to 2015;

4  1099G - year changed to 2015;

5. 1099K - Box 1b is renamed and year changed to 2015.

Also notes containing the newest changes for 1099 Files were released:
2250865 - US 2015 LC - 1099 File Changes
2250866 - US 2015 LC - 1099 File Changes ( for lower releases).

Please follow up on those notes for latest updates about 1099 and 1042 updates for the Tax Year 2015 to be submitted in 2016.

I hope it helps to address you your concern about this subject.

Danton Prestes.

Fellow SCN users,

I'd like to share with you a new electronic book (E-Bite), which is published by SAP Press (Rheinwerk Publishing)

Configuring Funds Management for SAP Public Sector. of Eli Klovski - by SAP PRESS

A budget is only as powerful as it is customized. Given your organization's unique business structure and requirements, set up Funds Management in SAP PSM to keep your costs and expenses on track. First set up your master data and define a budgetary structure; then integrate budgetary management, actuals and commitments updates, and AVC processes.

• Configure SAP PSM-FM for your budget needs
• Set up a budget structure that reflects your organization
• Customize budgetary management, actuals and commitment updates, and availability controls

I hope you will find this guide helpful and I'll be glad to receive your feedbacks. It will be very a great contribution both to myself, in my new role as SAP guides author, and, which is more important, to SCN in its mission to support and evolve SAP products.

Thanks in advance,

Eli

Recently our client has issue with goods receipt value. Simple formula applies to get goods receipt value = Goods receipt quantity X rate in PO

We have check rate in PO and also in material master but can not identify where the rate in MIGO picked up. We also checked and confirmed that user can not manually change rate\value while doing goods receipt.

Purchase order quantity 15 and rate 1635.68 per unit

Goods receipt quantity 15 and value is 2474.07

Moving average price in material master is 1,694.21

In the above example per unit rate is 164.94 (2474.07/15) in goods receipt. It does not match with rate in PO or material master.

Purchase order history

MIRO date 31/12/2015 Quantity 20 Amount 3,298.76

MIGO date 22/01/2016 Quantity 15 Amount 2,474.07

*Indicator Goods receipt based invoice verification is not set for the PO.

Solution

System calculates goods receipt value with specific formula.

Goods Receipt Quantity multiply by (GR/IR values in MIRO less Goods Receipt value) divided by (invoiced quantity less goods receipt quantity)

=15 multiple by (3,298.76 less 2,474.07) divided by (20 less 15)

=15 multiple by (824.69) divided by (5)

= 15 multiple by 164.94

= 2474.07

Initially you may find it difficult to understand the formula, however with some exercise it will be easy to work.

Hope this blog will be helpful to you.

Regards,

Deepak

Hello all,

SAP note 2083799 provides a composite scenarios involving posting with Accounting BAPIs. But I want to share with you more details related foreign currencies scenario:

The currencies are maintained in transaction OB22 for each company code. You can also see the 2-digit currency type keys here, which are used in accounting interface as well.

Currency type = 00 (document currency) and Currency type = 10 (local currency) are the only real hard-coded keys. You can also see this in OB22, as you cannot change the currency type key for local currency. For 2nd and 3rd local currency, the value depends on the kind of currency you are using. You can find a complete list of the different currency types in SE11 by checking the value range of the domain CURTP.

You see in currency type that basically it always ends with a 0. So the typical values are 10, 20, 30, 40... You also have a valueation field directly underneath with a single digit. This can indicate legal valuation, profit-center valuation and so on. For FI only legal valuation is relevant. If another valuation is maintained, then this value in valuation field will be added to currency type. So you can have a customizing like this:

2nd LC, Currency Type 30, Valuation 0 – legal valuation, currency USD
3rd LC, currency type 30, valuation 2 – profit-center valuation, currency USD

In this case LC2 would be currency type 30 and LC3 would be currency type 32. Only LC2 would be transferred to FI. LC3 would be relevant for profit-center accounting. Eventhough the amounts in LC3 are not relevant for FI, they are determined in FI-Interface (function FI_DOCUMENT_CHECK) if they have not been passed to accounting interface.

You do not have to provide the local currency amounts to accounting interface. Only the document currency is mandatory. But of course you CAN submit local currency to accounting (as MM does for example) then only the missing local currencies are determined in FI-Interface. Only important fact is: IF you submit at least one local currency, you should submit it in all line items and not just at single items. Otherwise a balance issue can occur.

More information on correct setup of OB22 is listed in note 335608.

I hope this helps!

Regards,
Raquel

Dear all,

Recently I faced a lot of projects requesting Accounting Posting Automation not only requested by Finance Department but other departments in our company.

Facing this challenge to create new projects to automate the business accounting process we had the chance to review some old programs and we realize high number of SHDB programming logic.

So, this post will be designed to give the opportunity to use the BAPI_ACC_DOCUMENT_POST and raise the benefits instead of SHDB.

SAP Role and Access Management

The first issue that we faced using the SHDB for example to call FB01 transaction code and create an accounting posting is the Access Security and compliance. Because it will be necessary to release the access to transaction code FB01 to the user to avoid the authority check issue.

This first point we find out when we faced a project to create accounting posting that will be used by logistic users. There is not compliance to release access to FB01 for Logistic Users.

Field Status Group

During the system life cycle, many changes can occur and one of them is the management of field status group assigned in the posting keys and G/L account.

When you record an SHDB and is used by the ABAP as call transaction, error can be generated if the field has been suppressed in the field status group requesting more ABAP fix.

Error Management

The BAPI_ACC_DOCUMENT_POST returns the error messages for all line items with error and can be easly handle by the user to correct them. The call transaction (SHDB) fill out line item by line item, generating error by each posting tentative.

Check Functions

You can use the function module BAPI_ACC_DOCUMENT_CHECK to check if the document has any issue before perform the post or even simulate your posting.

Skip User Default Settings

The call transaction (SHDB) will use user parameters such as currency and date format which can be different for each user and the ABAP code should treat that.

Generally, the BAPI and SAP standard functions should be used if possible and if exists.

Note that BAPI_ACC_DOCUMENT_POST will not commit the transaction, you have to use BAPI_TRANSACTION_COMMIT after it.

I hope it helps you.

Best regards,

Gabriel Coleti

Hi all,

We already have new notes just released for 1099 reporting, where Print Forms Layouts in Smartforms and PDF format are available.

Two notes are available:

2227185 - US Legal Change 2015 - 1099 and 1042 Smartforms and Adobe Forms (600 and above)

2227186 - US Legal Change 2015 - 1099 and 1042 Smartforms and Adobe Forms (current releases).

Those notes are the main notes which will contain the relevant details to be adjusted in order to correct and update 1099 and 1042 report including Smartform and Adobe Forms.

The major changes include:

1. 1099INT - Box 13 "Bond Premium on tax-exempt bond", "FATCA filling requirement" checkbox introduced and year changed to 2015;

2. 1099MISC/MISC1- "FATCA filling requirement" checkbox introduced and year changed to 2015;

3. 1042S - Numbering of the boxes are changed and year changed to 2015;

4  1099G - year changed to 2015;

5. 1099K - Box 1b is renamed and year changed to 2015.

Also notes containing the newest changes for 1099 Files were released:
2250865 - US 2015 LC - 1099 File Changes
2250866 - US 2015 LC - 1099 File Changes ( for lower releases).

Please follow up on those notes for latest updates about 1099 and 1042 updates for the Tax Year 2015 to be submitted in 2016.

I hope it helps to address you your concern about this subject.

Danton Prestes.

Hi All,

This is my very first blog in the Forum and initially I was bit hesitant to put a blog but logging in to forum and understanding the rules of forum has given me confidence to share my part in forum.

For the Italian tax report  S_ALR_87012357 normally a lot of us face issue with the page automation, where the correct page number is not updated in the table RFUMSV00_BAL_IT and we need to sometimes do it manually also from the table which is not a best practice.

I know there may be several threads on this topic in the forum already but with this blog I want provide a staraight forward approach to how to deal with this issue when it comes.

Please use this information when it works for you and give me feedback for the betterment of my future efforts. I am open to the feedback.

When you run the report S_ALR_87012357, report 30 ends at page 51 for October Month.

Now, report 30 for November should start with page 52 and SAP should automatically do this.

So, go the report and run the report and select the parameters as per the requirement.

Now select the check box under Document numbering and give the report number under the Posting Parameters.

Now select "Execute and Print" or "Execute in Background", rather than just "Execute".

Now you can see that the report 30 starts with page 52 and ends with page number 53.

After this when you run the report for Dec, the report 30 will automatically start with page number 54. So you can create a variant of your own and include the page number check box setting so that it happens for you automatically and no manual effort would be required after this to change the page numbers.

The page numbering in the RFUMSV00 for Italy is based on the assumption that it is run once per calendar month, with the selected posting date ranging between the first and the last day of the month. The BAdI-implementation for Italy, RFIDIT_TAX_BADI_010, reads the month from the lower value of the selected posting period. It then reads the last page number from table RFUMSV00_BAL_IT for the previous calendar month, continues incrementing it, and then saves the last page number of this run to table RFUMSV00_BAL_IT. Therefore, if we select over a posting period larger than one calendar month, we must select "NO" in the following pop-up in order to indicate that this is just a test run. If we select "YES", we will save the wrong page number to the data base table. We can, however, correct the last page number in the data base table, either by rerunning the report for the correct reporting period, or manually via transaction se16. In order to run report RFUMSV00 for Italy, select "Execute and Print" or "Execute in Background", rather than just "Execute".

Hope this helps.  Kindly provide feedback for improvement in future.

Regards

Seema

Hi all,

We already have new notes just released for 1099 reporting, where Print Forms Layouts in Smartforms and PDF format are available.

Two notes are available:

2227185 - US Legal Change 2015 - 1099 and 1042 Smartforms and Adobe Forms (600 and above)

2227186 - US Legal Change 2015 - 1099 and 1042 Smartforms and Adobe Forms (current releases).

Those notes are the main notes which will contain the relevant details to be adjusted in order to correct and update 1099 and 1042 report including Smartform and Adobe Forms.

The major changes include:

1. 1099INT - Box 13 "Bond Premium on tax-exempt bond", "FATCA filling requirement" checkbox introduced and year changed to 2015;

2. 1099MISC/MISC1- "FATCA filling requirement" checkbox introduced and year changed to 2015;

3. 1042S - Numbering of the boxes are changed and year changed to 2015;

4  1099G - year changed to 2015;

5. 1099K - Box 1b is renamed and year changed to 2015.

Also notes containing the newest changes for 1099 Files were released:
2250865 - US 2015 LC - 1099 File Changes
2250866 - US 2015 LC - 1099 File Changes ( for lower releases).

Please follow up on those notes for latest updates about 1099 and 1042 updates for the Tax Year 2015 to be submitted in 2016.

I hope it helps to address you your concern about this subject.

Danton Prestes.

I recently had the requirement to activate sensitive fields for a specific vendor account group but found that there was no possible way of doing it through standard config.  From what I've been seeing in the forums it appears SAP has no intention of changing this for the time being, and it looks like many companies have the same requirement or a similar one with with company codes. 

This blog Dual Control Functionality in SAP gives us good insight on how sensitive fields work and mention that an enhancement can be done in order to make it specific for one vendor account group, but doesn't mention how to do it.  I've seen a lot of people asking how it can be done, so I did some work and figured out a fairly simple way to do it.

User exit MF02KFEX was defined for us, and gets called in MF02KFS0 but unfortunately it can't do the job since the logic that checks the sensitive fields config comes after the exit. 

I was able to do the trick by creating an implicit enhancement at the end of FORM SENSIBLE_AENDERUNG in MF02KFS0.

Through debugging I found that the XSENSIBEL flag controlled whether or not the popup and the confirmation process would be initiated.

With just the following code inserted at the end of the form, I was able to enable sensitive fields specifically for account group V001 (hardcoded here for this example).

IF XSENSIBEL IS NOT INITIAL AND LFA1-KTOKK NE 'V001'.

     XSENSIBEL = ''.

ENDIF.

Note: for vendor account group you'll be checking LFA1-KTOKK, and for company code you'll be checking LFB1-BURKS.

Need help creating implicit enhancements? Take a look here: How To Do Implicit Enhancement - ABAP Development - SCN Wiki

Hope this helps!

Dear SCN Members.

Recently we develop a project for our customer which requested us to develop a Budget Transfer functionality between Internal Orders (CO-OM) and Fund Center/Commitment Items (FM-PSM), in this case they use the Former Budget.

Business scenario:

Our customer use FM-PSM to control expenses budget from departments and basically, all Cost Element and Cost Center are used in the derivation rules. As many other companies, the budget assigned to these objects are planned every year.

During the year, some special expenses(as the call here) are needed such as business trip, events, etc. In these cases, the planned year budget cannot be used since many departments have already planned the use of these amounts. So, in this case, Internal Order are used for that specifically expense.

Our customer budget and cost department creates the internal order for that expense and assign the requested budget for that.

According to the policy, after the use of this Internal Order budget, if some remaining amount exists, it can be transferred to the department budget, in this case Fund Center/Commitment Item.

As we analyzed, only FM has the Transfer budget functionality, and this transfer is between the same object (Fund to Fund).

Our business requested us to make the possibility to transfer budget cross-object IO <-> FM and FM <-> IO.

Functional Solution:

The functional solution that we found for this request, is to apply the Supplement and Return functions for each object and control these assignments in a Z table.

So, when our business transfer from IO to FM, we do a return budget in IO side and a supplement in FM side and vice-versa.

In a technical perspective, we had to think in how we could develop this to post only if both posting will be done. For example, the budget supplement has to be done only if the return have done. Since this is a transfer, the receiver must receive only if the sender has been sent.

Technical Solution:

The achievement of the best solution that we found, it was the CHECK function modules before the commit posting.

To Supplement and Return budget for FM we used FM: KBPI_BUDGET_ENTER

To Supplement and Return budget for IO we used FM: KBPP_EXTERN_UPDATE_CO

Before commit both transactions we run KBPI_BUDGET_ENTER in test run mode (there is a parameter to run in test mode) and KBPP_EXTERN_UPDATE_CO without commit option and finally we check the Return messages with both will be run without errors.

Using this way we will make sure that Receiver and Sender will posted successfully.

I hope this can help you in a scenario like this one.

Best regards,

Gabriel Coleti

On SAP, some tables are delivered as “customizing tables” when they supposed to be set as “Master Data tables” and allow you to maintain those tables in Production environment, instead following the “normal” path DEV-QAS-PRD system using transport requests.
One good example for this are the tables mentioned on my posting about Tax Dynamic Exception tables. Those tables are considered “Tax Master Data” on Brazilian Localization (and they are only used for Brazil).
A good reason to make those tables “maintained” in Production is for example if you have to create a dynamic exception to a certain tax table, J_1BTXCOF for instance, to calculate a different tax rate to a combination of Customer and Material (or even to a specific material or a specific Customer/Vendor)…
You will not be able to do that in DEV, since you don’t have (or you supposed not have) master data in DEV, that you can add to the table and transport it to PRD.
Many companies in this case they make the PRD environment “open” to allow the maintenance on those tables, which is a high risk, and for lack of information, knowledge or even lack of time to discuss this subject during an implementation, the subject is left behind and the PRD is open for change for a long period (or open and close every time when the change is needed, very painful for users and Basis right?)
What many people doesn’t know is that SAP has a OSS Note to support allow specific tables to be maintained in PRD without needing to open the environment for changes or transporting data from other clients.

By doing that, you increase the security on your PRD system and increase the business process speed to maintain the data when it is required without having to wait someone open the client, wait the user do the maintenance and close the client again.

1 – Open system with transaction code:
Example of transaction to “open” in PRD:
SPRO > Financial Accounting > Financial Accounting Global Settings > Tax on Sales/Purchases > Calculation > Settings for Tax Calculation in Brazil >Tax Rates >

> Maintain Default Tax Rate Values tcode: S_ALR_87003324
> Maintain IPI Values tcode: S_ALR_87003326
> Maintain IPI Material-Dependent Exceptions tcode: S_ALR_87003329
> Maintain IPI Dynamic Exceptions tcode: S_ALR_87100870
> Maintain ICMS Values tcode: S_ALR_87003332
> Maintain ICMS Material-Dependent Exceptions tcode: S_ALR_87003334
> Maintain ICMS Dynamic Exceptions tcode: S_ALR_87100868
> Maintain ICMS-Complement Exceptions tcode: S_ALR_87003230
> Maintain SubTrib Values tcode: S_ALR_87003232
> Maintain SubTrib Material-Dependent Exceptions tcode: S_ALR_87003236
> Maintain SubTrib Dynamic Exceptions: S_PL0_09000292
> Maintain ISS Values tcode: S_P6D_40000012
> Maintain PIS Values tcode: S_P6D_40000013
> Maintain COFINS Values tcode: S_P6D_40000014
> Maintain Withholding Tax Rates and Assign Official Collection Codes: S_P6D_40000030

To change the status for a transaction to “open” for maintenance in PRD while keeping the client closed, follow the steps below:
a) Check the table name that the transaction use
b) At Production Client, run transaction SE54, inform the table or view name and check “Generate Objects” and then click “Create/Change”. Select “No, or user, recording routine”, click in Save (create the change request) and hit enter
c) This procedure has to be done in a client where PRD is “closed” for changes.

2 – Open system without a transaction code
This is used to the activities that are reachable only via SPRO, but it doesn’t have a specific transaction assigned. It is possible to add the SPRO Activity to a Menu that the user can access. To do that, follow the procedure:
• Go to the IMG, and display the IMG structure.
• Position the cursor on the corresponding IMG activity and select the menu options “Edit -> Display IMG activity”.
• On the following screen, select the tab page “Maint.objects”.
• There you can see a list of the assigned Customizing objects.
• By double-clicking on the corresponding line, you navigate to the Customizing object and can directly set the flag ‘Current settings’ there.
• As an alternative you can also call Transaction SOBJ. There, you must directly enter the Customizing object and can then set the flag directly.

Oss Notes that you can use for reference: 78329 / 135028 / 77430

Leandro da Pia Nascimento

Hi all,

If there are special characters, as #, or unwanted spaces in the file generated by F110, probably there is something wrong with the code page for the format used.

In this case, you may follow the steps below to solve this kind of scenario:

1) Set code page 4110 in OBPM3 for the format used.

2) Implement notes 1954679 and 1841190.

3) Execute RFPAYM_RESET program for F110 run, and the generate again the DME file.

Best Regards,

Carolina