Responsibility area: Perform product costing monthly closing-ML
Table of contents
Scope
ERP
PF2
Frequency
References
Forms
Attachments
Previous OP << I run the Outbound Stock In Transit >> Next OP
1. Objective and Scope
1.1. Objective of this Operation
Usually the goods issue and the invoice is done in the same period so in the end of the month there is no need to make any additional postings to adjust stock accounts and profit and loss accounts.
However there are some situations in which goods issue is done in one month and the invoicing is done in another month. In these situations the stock is already issued but the customer may not yet have received it so it can be considered as stock in transit.
1.2. Scope
This procedure is applied to all companies WW.
2. Definitions
3. Tasks description
3.1. I understand the process of stock in transit
When there is an invoice, the cost of goods sold is posted in FI when the goods issue is done, but the amount in COPA it is only posted when invoice is done. So when there is stock in transit at end of the month, there will be differences in FI and COPA regarding COGS:
In theses cases it's necessary to run transaction Z1F_CLOSURE_CORR in order to eliminate this difference.
The program will analyze the deliveries already invoiced (in next month) and deliveries not yet invoiced (billing due list) and will automatically create a posting and reverse it in following month.
Until the invoice is issued the program will post and reverse a document every month.
The Cost G/L’s to be posted shouldn’t have cost element created because the posting should not have impact in CO module.
The Profit G/L won’t have any cost element because the COPA posting will be done in a separate document.
In some scenarios Z1F_CLOSURE_CORR will create automatically a posting that will reverse the FI posting done by the goods issue. This will postpone the goods issue posting to the month where the invoice will be issued so the cost of goods sold will be updated in COPA and FI exactly at the same time
In other cases the program will create a post to simulate the Invoice (IC) and update COPA. This will anticipate the Invoice to the month where the goods issue were done.
With this adjustment there won't be any differences between FI Module and COPA Module.
3.2. I correct the stock in transit side effect
Tasks to be completed when documenting an SAP Transaction, Report or Message code.
1. Title of the page = SAP Transaction code, SAP Report or SAP Message
2. Add the following Labels, respectively:
SAP Transaction => "sap_transaction", Transaction code "xxxx"
SAP Report => "sap_report"
SAP Message => "sap_msg"
3. On the left section, describe the steps. On the right section, insert respective print screens and additional guidelines, if needed (e.g. Main selections of the transaction...)
STEP 1
Use transaction code:
Z1F_CLOSURE_CORR - Correction Stock In Transit Effect: Initial Screen
Go to transaction Z1F_CLOSURE_CORR and fill the fields according to the screen on the right
STEP 2
When running the transaction in test mode there are some useful information that can be checked:
Procedure:
1 - ITBI missing invoice to customer
2 - ITBI missing sales cross-cy invoice in production company to commercial company
3 - ITBR missing purchase cross-cy invoice in commercial company from production company
4 - ITBI missing invoice to customer on Third party SB order
5 - ITBR missing purchase invoice from vendor on third party SB order
9 - Error (no posting)
Error:
BEFO - Invoice date before goods issue period
GR - Goods receipt for third party delivery
MUGI - More than one goods issue (period g.i<> period cancellation)
MUL - More than 1 invoice
SB - Neither purchase, nor customer invoices in this period
UNIT - Error while converting quantity to Sales Unit
ML - Material Ledger was not closed
When no errors exist, it should be analyzed whether the delivery has the accounting document generated :
If the accounting document is not generated, the accrual will be made by CLOSURE_CORR;
If the accounting document is generated, the delivery must be set is STOP by XSTOP -XSTOP in transaction Z1F_CLOSURE_CORR.docx
Some useful information:
Source of amount: explanation of how amount to be posted was calculated
Document Nº - FI document number of Goods Issue
STEP 3
By selecting F3 it will be displayed another list with more details about the errors and the documents already created:
STEP 4
Run the transaction in Real Mode
When the program is run with the option “Call Transaction” the same list will appear but with the information in the last columns of the documents that were created:
FI Document in the period executed
FI Document Reversed in the following period
COPA Document in the period executed (if applicable)
COPA Document Reversed in the following period (if applicable)