Configuration Steps in IDOC

 IDOC or Intermediate Documents are commonly used in case of data migration between SAP systems or between SAP and legacy system or vice versa.This blog details the steps involved in configuring a new IDOC and also list’s down the various transactions that are used while working with IDOCs.

IDOCs can be classified into two . Inbound IDOCs and Outbound IDOCs.

 

Inbound IDOC   : These are IDOCs which get the data into SAP system from external source i.e PI system  or any other external system.

Outbound IDOC: These are IDOCs which are sent out from SAP system to any other system. i.e PI system or any other external system.

 

Step 1 : We need to check the RFC connections to the target system , it can be PI system or any external system. If it is to a PI system then we need to check the connection under ABAP connections in SM59 transaction and for external system under HTTP Connections to External System.

 

 

Step 2: Create a port in transaction WE21 which shows the target system’s RFC destination.

 

 

Step 3 : In transaction WE20, create a partner profile and mention the message tpe details .In case of Oubound IDOC’s , mention the message types under Outbound Parameters.In case of Inbound IDOC’s , mention the message types under Inbound Parameters. For outbound parameters ,maintain port and IDOC details, because port describes to which system the IDOC has to flow. Whereas in Inbound IDOC,mention the process code details which determines the inbound function module for processing the data.

 

 

Step 4 : Message type SYNCH is the default message type for outbound parameters. Choose a particular message type and maintain the below settings. Under the receiver port mention the port created in transaction WE21. In Output mode, choose Transfer IDOC immediately. In IDOC type mention the IDOC associated with the Message Type.

 

 

Step 5: For Inbound IDOCs, mention the process code as APL1 and choose option Trigger Immediately under Processing by Function Module.

 

 

Step 6 : In transaction BDFG, we can see which ALE function module we need to enhance for our requirement. In case, we are working with Business Partner we can choose the FM as CRMXIF_PARTNER_SAVE and the Business Object Type as ‘BUS1006’. In IDOCs , SAP by standard provides us to exchange the business partner master data details , BP relationships and BP Hierarchies.

 

 

Step 7: In case we are working with Business Transactions we can choose the FM as CRMXIF_ORDER_SAVE and the Business Object Type as ‘BUS20001’.

 

 

Step 8 : In our example let us work upon Business Partners. Select the FM name and the Business Object type and click enter. By default all standard messages types would be displayed out.Now to create a new message type , click on Create button as shown below. You will get a popu where in you can enter a Z name.

 

 

Step 9 : Once the Z message type is created. Release it as shown.

 

 

Step 10 : Select  the  Z message type and click on the Display button to view the details.

 

 

Step 11 : With Z Message Type , Z FM’s for both Inbound and Outbound gets created.

 

Step 12 : In transaction WE30 we can check the IDOC  created.

 

Step 13 : In transaction WE31 we can check the IDOC  segment .

 

 

Step 14 : For Inbound IDOCs in transaction code WE42 , select the process code APL1 and click on display . Assign a Z Fm-ZAPPL_IDOC_INPUTI . Create a copy of the standard FM APPL_IDOC_INPUTI into ZAPPL_IDOC_INPUTI .

 

 

Step 15 : Under Logical Message , mention the Z message type created.

 

 

Step 16 : In  transaction WE81 , we can see the message type details.

 

Step 17 : In  transaction WE82 , we can see the message type and basic type details.

 

 

Step 18 : For outbound IDOCs in transaction BD64 , create a distribution model. Goto change mode and click on ‘Create Model View‘. Enter a description and Technical name.

 

 

Step 19 : Add the message type under the Distribution Model and maintain the sender and receiver system details.

 

 

Step 20 : In transaction BD82, generate the partner profile for the newly created distribution model.

 

 

Step 21 : In  transaction SMOEAC , we create the sites and subscriptions.Site is the destination where the data needs to be sent. Subsricption is to identify what is the object to be exchanged. (In case of BP data it will be All Business Partner MESG).Subscriptions are assigned under Sites. Type would vary based on our need.

 

 

Step 22 : In transaction CRMXIF_C1 , we maintain the message type details against the Site name.

 

 

Step 23 : We can even restrict an Outbound IDOC flow based on any condition to a particular Site. A times there could be multiple sites in a system , we can control the flow of IDOC here as well.This can be achieved by maintaining an entry in table – SMW3FDCUST, we assign a copy of standard FM – SMW3_OUTBOUNDADP_CALLADAPTERS against BDoc Type BUPA_MAIN,  which is  used to do any further customizations. We can do the same for other IDOC types.In the Z FM ,input parameter HEADER we get the Site ID details , based on that we can control the changing parameter – RECEPIENTS.

 

Step 24 : Apart from the above steps we can use Transaction WE02/WE05 to display any IDOC and WE60 for IDOC Documentation.To reprocess any IDOC use transaction WE19 adn inoput teh IDOC number, a new number gets generated.

 

Step 25 : Any IDOC has 3 records types – Control, Data and Status.Control Records displays the direction of the IDOC, message type/basic type details.

Data record display the data under multiple segments. In Status Record we can check the IDOC status whether it is a success or failure.

 

Tables for these 3 record types are as below.

 

Control Record – EDIDC

Data Records    – EDIDD

Status Record   – EDIDS

Source: https://blogs.sap.com/2016/07/05/steps-in-idoc-configuration-for-beginners/

SAP Readiness Check for SAP S/4HANA – Functional Review

 SAP Readiness Check for SAP S/4HANA is a powerful tool executed in your existing SAP system that supports several scenarios including SAP S/4HANA conversions and SAP S/4HANA upgrades. Focusing on system conversion scenarios from a functional perspective, the tool provides meaningful information that can be used for a high-level estimation of the amount of work your team will be required to complete to prepare for your transition of SAP S/4HANA.  SAP Readiness Check also helps identify the skillsets of the experts that must be involved in your project.  Mandatory tasks, tasks that can be resolved prior to project start, and tasks that can be left to future project phases are clearly identified.

Sometimes when you receive the result of your SAP Readiness Check your first question is, “So, now what do I have to do?” If that is your case, then this blog is for you! I will try to explain how to consume SAP Readiness check from a functional view.

The first thing you should be aware of is that this tool is more focused on “how to move to SAP S/4HANA through a system conversion” than “why to move to SAP S/4HANA through a system conversion”. This means It won’t necessarily help the business/final users to understand the business value of moving to SAP S/4HANA. For that, we have other tools like Process Discovery for SAP S/4HANA Transformation. SAP Readiness check is more technical; therefore, it must be used by the IT department/Center of Excellence (or any other name you may use to define a similar team in charge of your ERP).

Let’s focus on consuming SAP Readiness Check.  Let’s assume you are in the Discover or possibly in the Prepare phase of your transition.  To start getting ready for your conversion, you need to identify the most relevant priority work tasks for your functional experts.  “In [the] Discover [phase], the Simplification items along with the Financial Data Quality and Customer Vendor Integration Analysis are the main inputs for a functional review of your system”.

The next step will be to prepare and run what we called the “Simplification item workshops”.  For that, you must schedule individual sessions by business unit.  For example, a workshop for finance and another workshop for procurement topics.

In these sessions, you should go through each simplification item. For better planning, we suggest using the following classification:

• Need functional/technical remediation: Most simplification items fall into this classification, and all must be addressed before the technical conversion. Normally the required changes do not disrupt the end-to-end processes. For instance, it could be the need to remediate inconsistencies at the database level.
• Need fit-to-standard workshop: In SAP S/4HANA we have functionalities that replace features our customers use in SAP ERP. Some of them are mandatory, such as Settlement Management to replace Rebates. Also, we have others that are optional. For example, customers using Logistics Execution Transportation (LE-TRA) should strategically consider moving to TMS (SAP Transportation Management System) since LE-TRA is no longer the target architecture within SAP S/4HANA and SAP has no plans for further innovations. However, customers may elect to continue to use this functionality (via Compatibility Scoping) until 2030 (see SAP Note 2270199 – S4TWL – Transportation (LE-TRA) for additional details). Adoption of those new features has the potential to disrupt current business processes. Therefore, it is needed to carry out fit-to-standard workshops (as you would in a greenfield project) to implement the new functionalities.
• Non-relevant: SAP Readiness check could list some simplification items that in the end are not relevant for you. So, you must double-check and confirm that indeed is not relevant to your system. Why could this happen? Because SAP Readiness check validates things like master data and configuration, it could be that your system has configuration/master data of functionality that you are currently not using. Therefore, it is your responsibility to confirm the simplification item is a “false positive”.

Here you can find a summary of these groups:

 

The outcome of those workshops should include information such as the activities to be performed, when those activities will be carried out, the estimated effort, and who will be involved:

 

Let me explain this with one example. In the logistics workshop you will discuss the simplification item S4TWL – Business Partner Approach supported by the result of Customer Vendor Integration Analysis

First, this Simplification item will be assigned to Group 1: Need functional/technical remediation because it must be completed before carrying out SUM (the conversion) and it won’t need Fit-to-standard workshops because the sales or procurement end-to-end processes will not be impacted by this change. Of course, it will impact the way you create/update customers or vendors, but the final users responsible of the purchase or sales orders creation will not notice that change.

The result of this discussion should address who, how, and when you are going to tackle Customer Vendor integration. Below you can find some examples of the conclusions after this workshop:

According to the errors identified by Customer Vendor Integration Analysis, it was decided to execute an initial CVI setup and synchronization in a sandbox system. Therefore, the synchronization will be run as a pre-project considering:

• This pre-project will not be only about data remediation and configuration, but it will also include business decisions, custom code remediation and testing.
• The master data error will be remediated in the sandbox system and the PRD system. But the synchronization will be run only in Sandbox.
• Other tasks like final user training and change management will not be part of this pre-project. But they will be included in the system conversion project.

Based on the previous analysis you can create the following outcome chart:

 

In SAP Activate Methodology for RISE with SAP S/4HANA Cloud, private edition, we have created a task called Conduct Functional Review Workshop presenting in detail other examples that will help you to better understand how to classify each simplification item, and how to run those workshops. Those examples are:

I hope this blog post was helpful for you. If so, click on “like” or “share”. I’m looking forward to your feedback and comments. If you have any questions, I encourage you to post into the Q&A using the tags: SAP S/4HANA and SAP Readiness check. We will try to answer all your inquiries as soon as possible.

Special thanks to Monica Reyes, Vivian Mafra, and Thiago Zanguetin for your great contribution!

Brought to you by the SAP S/4HANA RIG team.

Source: https://blogs.sap.com/?p=1586210?url_id=text-global-profile-inbox-mod

Prepare your SAP S/4HANA System for an Upgrade

 It’s been almost 7 years since the first SAP S/4HANA product version was released. Meanwhile SAP S/4HANA is mature enough as thousands of customers around the world have adopted it one way or another, regardless whether they chose a new implementation or a conversion as the right path for them to transform their businesses.

Remember every SAP S/4HANA product version is under mainstream support by SAP for a period of 5 years through our so-called Support Package Stacks with the latest corrections and bug fixes. This means that SAP S/4HANA 1511 and 1610 are out of maintenance and by the end of 2022 SAP S/4HANA 1709 will be out of maintenance, too.

For us at SAP this means that we have already started supporting our growing base of SAP S/4HANA customers with their Upgrade Projects to help them get the latest product innovations and of course run their businesses in a supported SAP S/4HANA version. In the next couple of years, we will be supporting a growing number of customers willing to upgrade their solutions.

SAP S/4HANA Upgrades should be strongly considered for several motives and advantages:

1. Maintenance reasons: e.g., Stay on a supported release as per SAP S/4HANA maintenance schedule or replace classic SAP ERP Compatibility Packs (that expire end of December 2025) with alternative new capabilities.
2. Improve and increase value: Customers will benefit from new features and new business requirements. With each new release, more products are embedded within SAP S/4HANA, e.g., SAP Transportation Management. It is also a great opportunity to improve and grow your SAP Fiori User Experience with new Fiori apps delivered with each release. (SAP S/4HANA 2021 has more than 2400 Fiori apps available).
3. Technical Improvements: Major performance benefits for both SAP GUI for HTML and SAP Fiori Launchpad. General improvements to all SAP Fiori apps based on SAPUI5 technology improvements. New mobile capabilities on touch-enabled devices. More innovation scenarios can be leveraged, and you can also benefit from improved database with SAP HANA 2.0 to leverage its capabilities on the functional side.

 

Important Pre-Upgrade Tooling

Perhaps you *as a customer* are wondering what you need to consider for preparing and planning the efforts needed for a system upgrade. The intention of this blog is to give you the basic insights on this. SAP has developed and prepared a set of tools that will help you with these tasks. These tools that can be used (and it is strongly recommended to leverage them) many months before the upgrade project starts and will give you amazing, detailed analysis about your current SAP S/4HANA installation.

These tools are:

• SAP Readiness Check for Upgrades
• SAP Innovation and Optimization Pathfinder for SAP S/4HANA
• SAP Maintenance Planner
• Simplification Item Checks
• Software Update Manager – Prerequisite Check Extended
• ABAP Test Cockpit

Let’s review each of them in more detail:

SAP Readiness Check for Upgrades

As you might remember, SAP Readiness Check was first developed as a self-service tool to analyze the overall status of an SAP ECC System towards a system conversion. Last year SAP delivered the SAP Readiness Check for Upgrades, which provides a holistic analysis of an SAP S/4HANA System towards a successful and smooth upgrade.

The SAP Readiness Check will help you analyze among other things: the relevant simplification items for the target SAP S/4HANA product version, Add-On compatibility, basic Custom Code analysis (which can be enhanced by using ABAP Test Cockpit) and an Integration Analysis. Readiness Check will also suggest selected SAP Fiori applications to be activated according to the system usage.

You should check the documentation and instructions for using SAP Readiness Check for Upgrades in SAP Note 3059197

SAP Readiness Check for SAP S/4HANA Upgrades

SAP Innovation and Optimization Pathfinder for SAP S/4HANA

As newer SAP S/4HANA releases deliver simplifications and innovation opportunities, a great tool to take full advantage of SAP S/4HANA innovations is a Pathfinder report. The purpose of the SAP Innovation and Optimization Pathfinder is to deliver Innovation recommendations, suggest Business Improvement Opportunities and to help you Optimize IT, which of course will accelerate innovation adoption.

To start your way into obtaining a Pathfinder report about your SAP S/4HANA system you should:

• Check the Pathfinder landing page at Pathfinder landing page
• Check the how-to-guide.
• Implement SAP notes 2745851 and 2758146 into your productive system.

SAP Maintenance Planner

The SAP Maintenance Planner is the central planning tool for Updates, Upgrades, Migrations and Installations (and in the context of SAP S/4HANA, conversions as well) of any SAP ABAP or Java based systems. SAP S/4HANA isn’t the exception.

SAP Maintenance Planner is an important tool for planning and preparing the Upgrade of your SAP S/4HANA installation and it will help you with the following important tasks:

• It will verify the compatibility of Add-Ons and Business functions for the target SAP S/4HANA release.
• It will provide the software archives and Stack.xml file later to be used by the Software Update Manager during the upgrade process.
• SAP Add-Ons can be now planned for uninstallation (see Note 2911053)

If SAP Maintenance Planner detects that there are incompatible Add-Ons, the upgrade planning cannot continue. In this case it is important to verify SAP Note 2974663 and clarify which Add-ons are compatible with your target SAP S/4HANA release.

If an add-on is no longer required, please check with the vendor if a package for uninstalling the Add-on is available. See SAP Notes: 2011192 and 2911053.

SAP Maintenance Planner

Simplification Item Checks

A new Simplification Item Check run is needed to see how the Simplifications in the new release will affect your current functionality.

As mentioned earlier in this blog, the Simplification Item Check report can be run manually in advance. If the check result indicates items with red status, the reported inconsistencies must be resolved mandatorily. Items in yellow should be reviewed, but will not stop the Upgrade procedure.

• In order to run the latest Simplification Item Check version you will need to implement SAP Notes 2399707 and 2502552. For additional information see the following blog.

Software Update Manager – Prerequisite Check Extended

Many of you know the Software Update Manager is the tool needed to install the software archives that were previously downloaded with the SAP Maintenance Planner Upgrade calculation. However, since SUM 2.0 SP08, there is a valuable functionality that will allow you to collect a list of major issues without requiring to resolve each of them before proceeding to the next issue. This functionality is the Prerequisite Check Extended of SUM:

The Prerequisite Check Extended can be called by running SUM and choosing Prerequisite Extended Check Tool in the Scenario Strategy screen at the start of the run. The SAP Maintenance Planner Stack.xml will have to be provided.

This check will provide information like:

• Check if the current SAP S/4HANA Application server OS and SAP HANA database version are outdated for the target release
• Inactive objects in the system
• Simplification item checks report
• Missing SAP notes

At the end of the run you can collect the logs and reset SUM.

For additional information see the following blog.

SUM dialog screen on how to make use of Prerequisite Check Extended

ABAP Test Cockpit

Remember I mentioned that with each new SAP S/4HANA release, new simplifications are delivered? Well, this will possibly have an impact on your Custom Code.

ABAP Test cockpit will help you analyze the affected Custom Code objects and give you in advance the opportunity to estimate the needed effort for the relevant code remediation. With this said, it is important to emphasize that there is no need to wait for the first Upgrade cycle (Sandbox or Dev) to finish analyzing the code.

ABAP Test Cockpit can be set up beforehand in many ways:

• Remote ATC with SAP GUI: A standalone Netweaver 7.52 or higher (SAP_BASIS >= 7.52) can be setup as the Central Check system.
• SAP Fiori Custom Code Migration App: A fresh SAP S/4HANA 1809 or higher can be setup as the Central Check System.
• SAP Fiori Custom Code Migration App in SAP BTP: If you are a BTP customer, a Central Check System can be based on an SAP BTP ABAP environment.

Since Custom Code remediation and ABAP Test Cockpit is a big topic, I highly suggest checking the following materials and blogs:

Custom Code Migration Guide for SAP S/4HANA 2021

SAP S/4HANA System Conversion – Custom code adaptation process

ABAP Test Cockpit in the Cloud – What is already possible

Options to run the Custom Code Analysis

Having reviewed these tools: again, it is strongly recommended to leverage them before your project starts as it will save you valuable time.

Further recommendations

Last, but no least: I have some additional recommendations to help you ensure a smooth SAP S/4HANA upgrade:

Integration Analysis

The Integration analysis offered by SAP Readiness Check needs to be enhanced with an additional review. Reasons for this are:

• Most integration is covered by integration testing
• Version interoperability between SAP S/4HANA and other SAP NetWeaver systems should be validated with the help of SAP Note 2251604
• Check dependencies for older releases of SAP products with the Upgrade Dependency Analyzer (UDA)
• Integration to analytic platforms like SAP BW or SAP BW/4HANA should be checked as well. Refer to SAP Note 2500202

Sizing

With features delivered by SAP S/4HANA such as SAP Embedded Analytics and the embedded deployment of SAP Fiori, the demand for additional hardware resources is increased. Because of this, sizing should be reviewed accordingly to avoid performance issues.

The landing page for benchmarking and sizing can be found here and it will guide you through many of the aspects that need to be considered to properly size your SAP S/4HANA solution. The HANA-based quick sizer has to be used for this. You can also check this video to get an idea on how Quick Sizer works.

Downtime Optimization Options

Depending on different factors, the system downtime duration in an SAP S/4HANA upgrade is an important topic for several customers. SAP offers different downtime optimization options to help our customers meet their business continuity expectations:

1. Standard: SUM already offers several optimizations with the standard approach, as several upgrade phases occur while the system is still operational.
2. nZDM: near-Zero Downtime Maintenance is also included in SUM. This approach extends downtime optimizations by partly moving time consuming activities into the uptime phases and uses a Record & Replay technique for selected applications tables. Check SAP notes 1678564 and 1678565 to review restrictions, prerequisites, terms and conditions.
3. ZDO: Zero Downtime Option is included in SUM as well. This approach reduces the technical system downtime to an application restart. In general, this approach will further reduce the overall upgrade downtime compared to the standard and nZDM approaches. Several prerequisites and restrictions should be considered. Review these in SAP Note 2707731

 

Best Practices Guide for Upgrades

An amazing asset available for all our customers. I’m talking about the Best Practices guide for upgrading SAP S/4HANA. This guide provides lessons learned, guidance and best practices for upgrading your current S/4HANA release to a higher one.

The guide includes as well great advice for those who want to manage the pace of organizational change by running multiple, repeatable Continuous Improvement Projects after upgrade to drive more business value out of their SAP S/4HANA solution over time.

SAP Support Continuous Quality Checks

Customers are entitled to Continuous Quality Checks as part of their SAP Enterprise Support agreement. This means that when an SAP S/4HANA upgrade Go Live date is close, customers can book the following CQC services by creating an incident under component SV-BO-REQ:

• CQC for Upgrade, consisting of:
  • Analysis session: includes a parameter setting check and sizing (delivered 5 – 6 weeks before the upgrade Go-Live)
  • Verification sessions: Parameter setting check and performance analysis (delivered 6 weeks after the Go-Live)

• CQC Going Live Support:
  • Monitors your system on the first 3 – 5 productive days after Go-Live to detect issues before they arise.

I hope you found this blog post helpful. We have reviewed important information on tooling and great assets that will help you fast-start your SAP S/4HANA Upgrade project. Feel free to leave comments and feedback. You can follow the Software Logistics – System Maintenance tag to receive updates on blog posts here.

Wishing you all a successful Upgrade project!

Brought to you by the SAP S/4HANA RIG

Source: https://blogs.sap.com/2022/08/05/prepare-your-sap-s-4hana-system-for-an-upgrade/

What is Account Assignment Category in SAP MM, How to configure?

 This Blog Post will give the overview on what is Account Assignment Category in SAP MM and How to configure it within SAP system. I will explain configuration step by step in SAP configuration.

This article will guide you through step by step procedure and will give you the complete idea on usage of Account Assignment Category and Item Category.

Account Assignment Category:

It indicates what type of purchase the company is doing in Purchasing Documents, whether it is for consumption or anything relation to orders, projects etc. The nature of this also indicates which accounts it needs to be charged for when the incoming invoice and Goods Receipt are posted.

Path	spro – Material Management – Purchasing – Account Assignment – Maintain Account Assignment Categories
Tcode	OME9

Depending on the requirements you can create customized ones as well. Select one line item and click on the icon (with the magnifying class). Or if you want to create one Hit the “New Entries” icon.

Certain configuration needs to be maintained for a particular account assignment category and the screen selection. Below image shows the configuration and screen selection..

The above screen will pop-up to maintain the configs. For now, lets consider K- Cost Center

So, for “K” only GL Account, Cost Center needs to be mandatory i.e. user need to specify the respective value for this and for rest can be maintained as optional/hidden/display.

In the detailed Information tab, we can see certain options

• assg.changeable (Account Assignment Changeable) – It indicates whether the specified Account Assignment category can be changed in Goods Receipt/Invoice Receipt or not.
• Consumption Posting – It specifies whether the goods that are procured are used for which purpose like for personal usage or for a project. Some options include Consumption, Asset, Unknown, Accounting via Project/ Sales Order
• Distribution – It is used whether we can distribute the ordered qty on Percentage basis, Amount or Quantity basis.
  • For example, let say you need to buy 300 chairs for IT dept but HR dept also needs 200 chairs. So, you will create a purchase order for 500 chairs with Account Assignment Category ‘K’. If distribution is configured than you can split the qty in 300 – 200 and assign them to their respective GL Account/ Cost Center in Purchase Order. Since each department would be having it’s own Cost Center.
• Account Modification – IT indicates what GL account it will be posted through the Account Determination
• acct.assgt (Derive Account Assignment) – If this is configured for an account assignment category, then the GL account and Cost Center will be pulled automatically by the system. (Pre-requisite: In Acct Modification whatever value is maintained for that a corresponding GL account should be defined in Tcode OBYC) This can be used for both materials having MMR or without MMR.
• ID: AcctAssgt Scrn (Account Assignment Screen) – Defines whether it is a single or multiple account assignment.

After this we have certain checkboxes like Goods Receipt/ Invoice Receipt – Defines whether Goods Receipt will be relevant or not for the items created with this account assignment category.

After completing all the steps you can create the Purchase Orders using an Account Assignment Category.

So here we complete the configuration about the Account Assignment Categories.

Let’s move to what combination of Account Assignment and Item Category is allowed in Purchasing document.

Path	Spro – Material Management – Purchasing – Account Assignment – Define Combination of Item Categories/Account Assignment Categories
Tcode	OMG0

It is a mapping between the Item Categories and Account Assignment that indicates what are the relevant and correct combination that can be used in purchasing document.

Okay, now you might be wondering what are item category?

Item categories are defined to provide additional control functions for the documents to meet the demands resulting from different business transactions.

Basically it has the same functions as of Account Assignment but with a different set of usage.

There are different Item categories configured in system. You can define/create them here

Path	spro – Material Management – Purchasing – Define External Representation for Item Categories
Tcode	OMH4

The above are some standard Item category defined by SAP, but always open to create a custom one as per the requirements.

Here I complete the detailed explanation of Account Assignment,  Item Category & it’s configuration in SAP MM.

Please do provide your valuable feedback on this post in comments section, this will help me in improving my content and share more knowledge with this community, also you can follow me for more content related to SAP!

Till then Happy learning!

Source: https://blogs.sap.com/2022/07/29/what-is-account-assignment-category-in-sap-mm-how-to-configure/