SAP FI TAX, BR NBS codes configuration

Services Codes (based on legal requirement LC 116)

Prerequisite:

There is no pre-configuration (customizing) needed.

SAP Configuration:

Transaction code: J1BTAX

Country: BR

Go to Entities menu and select NBS Codes option:

• In the Nomenclature Services Code column insert the codes numbers
• In the Description column insert the correct description of the NBS Code

Start entering NBS directory in above view manually.

Save.

SAP Material Ledger, Configuration of PU rule(s)

Issue description:

When posting of PU document for posted Invoice Receipt document via J1GP01 t-code, you’re getting error message stating that combination of Plant/Valuation class/Item category/Tax code entry is missing:

Root cause:

Missing configuration in J1GP02 view.

Solution:

Maintain missing entry in J1GP02 view. And then re-run J1GP01 t-code once again.

For more information on Materials Ledger t-codes check the following link.

Enjoy.

SAP Material Ledger t-codes

According to recent statistics, SAP Material Ledger topic is becoming the most viewed one...)

Okay, so below is the list of t-codes of Hellenization standard solution:

J1GVL_T01 t-code

Not needed any longer, but project should start with initial upload of stock to valuation table via J1GVL_T01 t-code (initial upload with 561 movement type);

MIGO/MIRO

Completion of GR/IR postings;

J1GP01 t-code

PU postings (FI postings that transfer the balance from SAP Stock account to the appropriate Greek purchasing account): update of foreign purchase accounts. It checks if the PU posting had already been done or not and then it continues to gather the necessary information needed to perform the posting;

J1GP05 t-code

Clearing of open items;

J1GVL_T04 t-code

Offline update of ML; 

J1GVL_T11 t-code

Initialize production run; 

J1GVL_T05, J1GVL_R3, J1GVL_RPU, J1GVL_RRV

Material valuation results check via running reconciliation reports; 

J1GVL_VL

Material valuation program;

J1GVL_P01 t-code

Running WHB analytical report; 

J1GVL_ALDI t-code

Reconciliation between WHB and ML: Analytical posing in testing/production modes;

J1GVL_S12 t-code

Compare valuation and AL postings; 

J1GVL_T15 t-code

WHB to CD utility. Export to .txt output file;

J1GVL_INVB t-code

to be executed during year end.

SAP PY and FI-AP, PA30 t-code issue when maintaining Bank Details infotype

When trying to create Bank Details (InfoType 0009) via PA30 t-code for ABCD employee, following error occurs: 

Please do not enter bank data for payment method Cash Payment 
Message No. RP568 
Diagnosis 
The bank data cannot be processed for the payment method specified ('). 
Procedure 
Please use a different payment method or delete the entries for bank key, bank account (and bank control key, if applicable). 

Basically solution here is to maintain payment method for bank account,which is very straightforward APP setting, but according to statistics of my posts, APP posts are the most viewed ones..? 

Anyways solution is as following:

FBZP t-code -Pmnt method in Country 

Following entry to be added: 

Country: XYZ

Pymt Method: ABC 

Description  Bank Transfer 

Description  Bank Transfer 

Payment method for: 

‘Outgoing payments’- checked 

Payment method classification: 

‘Bank transfer’- checked 

‘Allowed for personnel payments’- checked 

Required master record specifications: 

‘Street, PO box or PO box postal code’- checked 

‘Bank details’- checked 

‘Account number required’- checked 

‘IBAN required’- checked 

Posting details: 

Document type for payment: [  ]         

Clearing document type: [  ]              

FBZP t-code -Payment methods in Company code

Following new entry to be added:

Paying co. code 1234   CoCd Description

Pymt Method     ABC     Bank Transfer

Minimum amount                                 LC

Maximum amount    999,999,999.00   LC

Distribution amnt                                  LC

SAP PS, Project Budget Tolerance Limit

This post will be short and straightforward one and will be covering PS basics, but in case you find it useful, GOOD! :)

So, assume, you've set project budget tolerance limit to 15% for the Group and now certain entities are willing to change it to 10%, i.e. you they wanting system to hard stop any Project/WBS related activities, when budget exceeds 10%.

I'd do the following in this case:

(a) create additional Project Profile in V_TBPFD_P view (SM30 or check for configuration t-code in SPRO), you should be having something like following:

AS IS:

CoAr.    PROF.  DESCRIPTION            TR.GRP     ACT.      USAGE:
XYZ 0 General budget profile ++               1 105,00
XYZ 0 General budget profile ++               3 115,00

TO BE:
CoAr.    PROF.  DESCRIPTION            TR.GRP     ACT.      USAGE:
XYZ 0 General budget profile ++               1 105,00
XYZ 0 General budget profile ++               3 115,00
XYZ 1 General budget profile ++               3 110,00

(b) create new substitution step that is valid for Project System via OPSN t-code, substition to be something like following:

(c) activate the new substitution for all of the Project Profiles in following way:

And this is it. Now that you'll be creating new WBS element, system will be defaulting 'Budget Profile' field value to '0' initially, but once you save WBS element, 'Project Profile' field value will be replaced with '1' ,hence new project tolerance limit will be applied.

SAP FI, Defaulting of 'Tax Reporting Date' (BKPF-VATDATE) in FB01 t-code

As per SAP standard, Tax Reporting Date in Document Header section of FB01 t-code is being defaulted with Posting Date. Let's assume, you're required to enhance it so that it stops defaulting the value in Tax Reporting Date field or ,as an example, you want it to be defaulted with Document Date field value.
Note that below described approach is not supported by SAP standard, so I'd advise you to discuss the approach with your ABAP people.

SE18 t-code:
Enhancement Spot VATDATE_RULES with the BADI definition VATDATE_VALUES.
A default implementation: VATDATE_VALUES_DEFAULT_SAP

Create Z* enhancement implementation:

And add the following logic into it:

IF BKPF-BUKRS= 'this and that' then BKPF-VATDATE to be equal to BKPF- BLDAT when posting document through FB01, FB60, MIRO and VF01 t-codes.

That's about it :) 

SAP MM, Material Ledger, post New G/L migration issue with J* reports

Suppose New G/L migration is happening in FY 2020, and ,out of the blue, J1GGL report stops displaying data for the specified ledger(s) for G/L accounts, which is linked to GLT0 table update post New G/L migration.
When asking SAP, they might advise you to take a look at the following SAP note # 923946 with some correction instructions provided in it, which ,in fact, is not solving the issue with J* reports. Programs that can be affected are as following:
J_1GALTB Ledger Trial Balance (Official)
J_1GALTL Update A/L (FI) from SPL
J_1GGL000 Detailed Ledger
J_1GJR_ROUTINES Document Journal
J_1GSL000 Summarized Ledger
J_1GTBAC0 Ledger Trial Balance in ASCII file
J_1GTBGL0 Ledger Trial Balance (Unofficial)
J_1GVL_ALPOST_DI Analytical Ledger (A/L) postings for Materials
J_1GVL_WHBT05 Read actual values for given WHB column

In reality workaround to the issue is as simple as below:

(1) Execute J1GGL for ALL of the the prior to FY 2020 fiscal years (i.e. all of the FYs prior to New G/L migration). I believe, some FM is being re-generated at this step. If you know FM technicalities, then just re-generating it via SE37 should be enough (and share FM naming in comments section!:))

(2) Execute J1GGL for the FY 2020 and validate whether now data is being displayed correctly.