E-Book: SAP Enterprise Structure Concept and Configuration Guide


E-book: SAP Enterprise Structure (MM and related modules such as FI, Logistics, and SD) Concept and Configuration Guide

SAP enterprise structure is organizational structure that represents an enterprise in SAP R/3 system. It consists of some organizational units which, for legal reasons or for other specific business-related reasons or purposes, are grouped together. Organizational units include legal company entities, sales offices, profit centers, etc. Organizational units handle specific business functions.
Organizational units may be assigned to a single module (such as a sales organization assigned to Sales and Distribution (SD) module, or to several modules (such as a plant assigned to Materials Management (MM) and Production Planning (PP) module).
SAP ERP system can represent a complex enterprise structure. Its flexibility can integrate the structure of an enterprise by linking its organizational unit. Enterprise structure design is a fundamental process in a SAP implementation project. The design is mainly determined by the business scenarios performed in an enterprise. Once the design is determined, it will affect many things such as how to perform a transaction and generate reports on SAP system. Although it’s possible, it requires great effort to change the enterprise structure. So , we must ensure that the enterprise structure designed in the SAP implementation project can accommodate all business scenarios and enterprise’s requirements for current and future situation.

Purchase Requisition (PR) Release Strategy – Basic Concept


Purchase Requisition (PR) is an internal purchasing document in SAP R/3. It is used to give notification to responsible department (purchasing/procurement) of requirements of materials and/or external services and keep track of such requirements. PR must contain information about quantity of a material or a service and the required date.


It can be created directly (manually, through ME51N T-code) by a person or indirectly by another SAP component (such as material requirement planning/MRP, maintenance order of Plan Maintenance/PM module, production order of Production Planning/PP module).


PR then can be processed to be an external purchasing document (such as Purchase Order/PO) or internal purchasing document (such as Stock Transport Order/STO).


In SAP R/3, PR can be processed directly to be PO/STO or must be approved/released before it can be processed to be PO/STO.

Continue reading

Message No. M7001 – Check table 169P: Entry xxxx does not exist

Have you ever see the following error when you’re just implemented a new company code?


SAP error message No. M7 001 – Check table 169P: Entry (company code) does not exist will appear when you try to perform Goods Receipt in a plant which its corresponding company code has not been maintained in Logistic Invoice Verification configuration.

To maintain it you can use OMRG or S_ALR_87001785 tcodes in SAP SPRO IMG menu path. Continue reading

All SAP SPRO IMG configuration activities – with menu path and transaction code

Have you ever need to know the SAP SPRO IMG menu path for a specific Transaction Code (t-code)? By knowing the SPRO menu path of an SAP configuration activity, we can see the corresponding SAP help documentation. It can help us a lot.

Actually, you can search the SAP SPRO menu path of an activity if you know the description of the activity. On SAP SPRO IMG screen you can click the “find” button (  ) and type the description in the “search term” field. Continue reading

Stock Transport Order – Without Sales & Distribution (SD) Delivery

In the previous post about stock transfer between plants, I have explained that we can transfer stock between two plants in SAP ERP with:

In this post I will explain stock transport order without Sales & Distribution (SD) delivery function. Continue reading

SAP Directory: a collection of SAP Links

Do you have SAP blogs, SAP Websites, SAP Forum, SAP books, SAP videos, SAP Training provider, or any other SAP resources that you want to promote to SAP communities?


Do you know any SAP blogs, SAP Websites, SAP Forum, SAP books, SAP videos, SAP Training provider, or any other SAP resources that you think are worth sharing to SAP communities?

If the answer is yes for any questions above, you can submit the links at http://Links.ofSAP.com, a human-edited SAP Directory.

You can submit any good quality SAP-related links to the corresponding category available at the directory. I will review all the links submitted before approving them.

The cost for submitting SAP links is free. This SAP directory is not a links-exchange program, so there is no need any reciprocal links. As long as the links you submitted are good quality SAP-related ones, I will approve and publish them to the directory.

The objective of this SAP Directory is to share good quality SAP links to SAP communities, so it can help us to find good resources of SAP that available on internet. I hope this directory can help our SAP learning process.


Intra and Cross Company-Codes Stock Transfer Posting

In term of organizational structure level, stock transfer posting between plants can occur in a same company code or cross-company codes.

Stock Transfer Posting between plants in a same company code

  • If the material transferred between plants is not-valuated material (“value update indicator” is not set in the material type configuration for the plants), the stock transfer posting does not affect accounting.
  • If the material is valuated for the plants where stock transfer posting occurs and the valuation level is company code, stock transfer posting also does not affect accounting. It’s because the value of a certain material in all plants in the company code is the same.
  • If the material is valuated for the plants where stock transfer posting occurs and the valuation level is plant, stock transfer posting will affect accounting.If the procedure used is one-step transfer posting, the transaction will create accounting journals when it’s posted. The inventory account in the issuing plant will be credited and the one in the receiving plant will be debited.If the procedure used is two-steps transfer posting, the “Remove from Storage” transaction will create accounting journal when it’s posted. The inventory account in the issuing plant will be credited, and the one in the receiving plant will be debited (although in term of quantity it’s still on “stock in transfer” in the receiving plant, not in “unrestricted-stock” yet).
    The “Place in Storage” transaction will not create accounting journal as it only transfers “stock in transfer” to “unrestricted-stock” in the receiving plant (in a same plant).