This wiki page provides an overview about account assignment related topics in the SRM system.
Most of the accounting related logic and checks are not implemented in the SRM system. The SRM system based on the customizing could use either local or real-time backend validation for the FI data but certain checks are only part of the document creation in the ECC system.
The major topics related to the account assignment:
Default account assignment
In the SRM system there are multiple documents where the account assignment is required for the items. If the document related to another document like in case of confirmation the data will come from that document but in case of a new purchase order or shopping cart the system will determine a default accounting when the item created.
GL account determination
For the default GL account determination it is possible to maintain a static customizing or any kind of custom logic with BAdI implementation. The GL account determination in the SRM side only called during the item creation, accounting category or product category change.
About the GL account determination logic you could find detailed information in the GL account determination Wiki site.
Real-time backend validation of the FI data
If you choose the real-time validation of the FI data the SRM system will send the accounting data to the backend system for validation during the document creation or change. This requires RFC call as the relevant logic is not available in the SRM system. This validation could be used also to update the accounting data with the related secondary accounting fields during the item creation or after change in the accounting data. This RFC call could also use the substitution rules and default settings in the backend system to update the accounting data in the document.
There are further details about this accounting validation and possible impact to the SRM scenarios in the Accounting check and field update during Shopping Cart or Purchase Order creation Wiki site.
Accounting line indexes
Based on the used document and scenario you could see different system working related to the line number / index of the accounting lines when you delete one. In certain scenarios you could see renumbering within the document or just in the follow-on document.
You could find detailed information about this topic in the Accounting indexes Wiki page.
The account assignment descriptions are not stored in the SRM documents.
The documents have only the accounting values and the system checks the description in runtime for every displayed accounting objects.
You could find detailed information about this topic in the Account assignment descriptions Wiki site.
Search helps for accounting fields
Based on the maintained authorization you could use either a local search help based on the attributes in the organization structure or a backend search help. In case of backend search help the system uses RFC calls to the backend system to get the data. These calls use search helps implemented in the backend system but from SRM 7.0 and onwards you could experience some restrictions due to the used WebDynpro environment compared to the ITS that SRM 4.0 and 5.0 used.
You could find more information about the search helps in the Accounting field search helps Wiki site.
In the SRM system you could define new accounting categories or change already existing one through customizing.
The main information related every accounting category is its ID, name/description, the leading and non-leading accounting fields maintained for it and the associated backend accounting category.
You could find information about the extra steps that you need to make if you want to use a customer specific accounting category in the shopping cart default settings on the Account assignment tab in default settings Wiki page.
Accounting mapping during document transfer to the ECC system
When you order a classic scenario shopping cart or extended classic purchase order the follow-on document will be created in the ECC system.
The ECC system is in multiple areas different from the SRM system and due to this reason there is certain mapping logic to ensure the successful document creation.
These restrictions mainly related to the accounting distribution in case of multiple account assignment and the conversion of the accounting percentages from two decimal places to one.
Also in the document in the ECC system there is an item level accounting category that the SRM system should determine in case of multiple account assignment lines for an item.
Mapping the SRM category to ECC accounting category
When the follow-on document is created in the ECC system the accounting category of the item should be determined.
In case of a single accounting line the system uses SRM customizing of the accounting category to determine the backend accounting category.
If you use multiple account assignment lines with categories that are assigned to different backend accounting categories as there is no single associated accounting category the system will use the X accounting category.
You could also use the BBP_ACCCAT_MAP_EXP BAdI to overwrite the standard logic.
Mapping the ECC accounting category to SRM accounting category during confirmation creation
When you create a confirmation in case of classic and extended classic scenario the accounting data in the confirmation will based on the accounting information of the backend purchase order.
In case of classic scenario the system will try to map the ECC accounting category to the SRM category based on the SRM customizing for accounting categories.
In case of extended classic scenario the system will use the accounting categories in the SRM PO.
You could find more information about the accounting category determination during confirmation creation in the Accounting category determination for confirmation item Wiki site.
The limit items and the direct material items have specialties related to account assignment.
You could create a limit item with unknown account assignment option which means there is no accounting information available at the moment and you could order such items without accounting or maintain it later. This option means missing accounting information and not an accounting line with category Unknown.
If you set a normal item as direct material the system will delete the already existing accounting lines and hide the account assignment tab so unlike in case of limit items you could not add any accounting line to it.
Accounting lines in BBP_PD
The accounting lines have a separated section in the document in BBP_PD transaction.
The accounting lines are identified by the line number / index and the associated document item number.
It is important that if you delete a document item the accounting lines remain active.
PPOMA attributes for accounting fields
For the local search help and default account assignment determination is important to maintain the available values for the accounting fields in the PPOMA.
You could find the list of the PPOMA attributes that are related to accounting fields in the PPOMA attributes for accounting fields Wiki page.
There are 3 accounting related customizing option in the SRM system:
- Define Account Assignment Categories
- Define G/L Account for Product Category and Account Assignment Category
- Maintain Local Accounting Data
These options available under the account assignment section in SPRO:
SAP Supplier Relationship Management ->SRM Server -->Cross-Application Basic Settings --->Account Assignment
Also the FI validation type set in the Define System Landscape customizing is important for the accounting scenarios like validation and accounting descriptions.
Available accounting related BAdIs