1 Objective and Scope
1.1 Objective of this Procedure
1.2 Scope
2 Reference Documents
3 Definitions
4 Transaction ZZF_CICCIBA
4.1 Principle
4.2 Frequency & timing
4.3 Selection
4.3.1 Selection screen
4.3.2 Relevant fields
4.4 Result
4.4.1 List of errors (level 1)
4.4.2 List of errors (level 2)
4.4.3 List of errors (level 3)
4.5 Forms to access the List errors
4.5.1 Modification in the header of the list
4.5.2 Modification in the line items
4.5.3 Modification – validation
4.5.4 Display of original information
4.6 Forms to access the List of errors
4.6.1 Difference too Large for Clearing
4.6.2 E G/L Account xxxxxxxxxx does not exist
4.6.3 E G/L Account xxxxxxxxxx in company code does not exist
4.6.4 E Account xxxxxxxxxx requires an assignment to a CO object
5 IBA Reconciliation Differences & GL Account 5080900000
5.1 Principles
5.2 Receivables
5.3 Payables
5.4 Other IBA adjustments
5.5 Balancing & Clearing of GL account 5080900000
6 Tables
7 Appendix
The purpose of this document is to describe the transaction for automatic posting of the operations on Internal Bank Account
This operating procedure (OP) applies to all companies in PF2 and WP2
N/A.
IBA – Internal Bank Account
The transaction reads the specific table (ZZF_CICC_ABSTRAE) containing the IBA posting in error and gives the opportunity to manage the different item of the IBA statement in order to complete / modify the proposed posting.
Transaction ZZF_CICCIBA posts in PF2 and WP2 the IBAs downloaded overnight from PI2 IHB Finance (cc 2232), simultaneously enforcing the IBA reconciliation with IHB.
IBAs correspondent to 591XXXYYYY accounts.
XXX – IBA currency (e.g. EUR, USD, GBP, etc…)
YYYY – IBA financial relay (e.g. 5835 for Italy or 2232 if no relay exists)
The transaction is processed every day by Accounting Platform team.
Display mode | N : process the transaction without display of the transaction screens |
Process file | Always "blank" |
Process errors | Always "marked" |
Company code | Companies to be treated |
The first list is at company level. If the flag is red 
, it means that some statements are in error for the company concerned.
Click on 
to obtain more detail.
The second level is by statement. If the point is red 
, it means that at least 1 line of the statement is in error.
The information at this level is :
Click on to obtain more detail
The third level is by line item of the statement. The information at this level is:
Click once on the line with error in order to modify different field in the header of the screen.
The errors can be managed with 3 different methods.
It will depend of the kind of errors and to the solution.
In the header of the list you may modify 2 fields :
|
After correction, Click on |
|
|
|
|
After validation and correction of all the screens; the document is posted and the document numbers appears in the list with a green point 
By click on 
, it is also possible to see, in the table ZZF_CICC_ABSTRAE, the original information coming from the IHB.
This message appears when it exist a difference between the amount to be cleared and the selected document. The analysis and action depends of the operations :
If the decision is to post the amount without clearing then the correction can be done in the header of the list (see 4.5.1).
E G/L account xxxxxxxxxx does not exist
This message appears if the account determined automatically via table ZZF_ABSTRACT doesn't exist in the chart of account. It is intentionally foreseen for some operation which demand a manual intervention (Forex contract – Swap of currencies). After analysis of the question with the local accounting, the modification can be post by correction in the line items.
E G/L account xxxxxxxxxx in company code does not exist
This message appears if the account doesn't exist at company code level. In this case ask the for creation of the account and then you can modify the account in the header of the list.
The request should be sent to DT team.
E Account xxxxxxxxxx requires an assignment to a CO object
This message appears if the account requires a CO object
If you want to post the document before the update of transaction OKB9, the correction can be done in the line items.
On posting daily IBAs differences may exist caused by financial postings triggered in PI2 Finance (2232) which are un-determined to the SBS SC RTR team.
To allow IBA reconciliation, these differences are temporally posted in GL 5080900000 (IHB Positions to clear) waiting for clearing.
Open items on this account should be reconciled at month-end and its responsibility is shared between SBS SC RTR and Local Accountants.
Most frequent IBA adjustments coming from the receivables area are:
Debit 5080900000
Credit IBA
Debit IBA
Credit 5080900000
Debit 5080900000
Credit IBA
Debit IBA
Credit 5080900000
Note: On the cases mentioned above, postings are assuming a customer's invoice. If it is a customer's credit note, postings are reversed.
If SBS SC team un-doubtfully identifies the customer's documents, the postings may be done directly not generating a reconciliation difference in account 5080900000. E-mail is sent to SBS SC OTC, communicating postings done. SBS SC OTC informs Credit Management network.
For doubtful situations (not possible to identify the customer, the invoices, the action, etc...), e-mail is sent to SBS SC OTC requesting further clarification. SBS SC OTC contacts Credit Management network.
Most frequent IBA adjustments coming from the payables area are:
If SBS SC RTR team un-doubtfully identifies the vendor's documents, the postings may be done directly not generating a reconciliation difference in account 5080900000. E-mail is sent to SBS SC PTP, communicating postings done. SBS SC PTP informs Credit Management network.
For doubtful situations (not possible to identify the vendor, the invoices, the action, etc…), e-mail is sent to SBS SC AP requesting further clarification. SBS SC PTP contacts Credit Management network.
Most typical IBA adjustments are:
Check the open items in GL account 5080900000 through transaction FBL3N.
Use transaction F-03 to clear open items.
Remaining non balanced open items have to be analysed in order to balance and clear them.
The table ZZF_CICC_ABSTRAE contains all the statement's line items not yet posted in the ERP (with the original informations coming from the IHB). Those informations are:
N/A.
End of document
to reprocess the posting. 
to reprocess the posting with display mode "Display all screens" or "Display errors only" which authorized the direct modification in the different screens of the transaction FB05. 
