Intra and Cross Company-Codes Stock Transfer Posting

Posted on by
3

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).

Procedures of Stock Transfer Posting between plants

Posted on by
5

SAP One-step and two-steps stock transfer posting procedures

In the previous post about stock transfer between plants in general, I have explained that it can be done with Stock Transfer Posting (which solely in SAP MM Inventory Management component) or Stock Transport Order (which also involves SAP MM Purchasing and SAP SD components).

In this post, I will explain Stock Transfer Posting in more details.

Unlike stock transfer posting from one storage location to another storage location which can be carried out for all stock types, plant to plant stock transfer posting can only be carried out from unrestricted-stock to unrestricted-stock in both plants.

In term of how to do the transaction, stock transfer posting can be done in one-stop procedure or two-steps procedure.

Stock Transfer Posting in One-step Procedure

The advantage of one-step stock transfer posting is the simplicity that we only have to do a single transaction for it.

In that single transaction, the unrestricted-stock in issuing plant is reduced and the unrestricted-stock in receiving plant is increased. The unrestricted-stock quantity in one storage location of a plant can be seen in MARD table – LABST field.

Continue reading →

Quick update on Tables.ofSAP.com

Posted on by
4

List of all SAP tables by category

After categorizing all SAP Tcodes by modules at http://tcodes.ofsap.com (that I’ve explained on previous post), I’ve also updated another section of ofSAP.com at http://tables.ofsap.com.

At that section, I have categorized the SAP tables whether they are:

  • Transparent table.
    From SAP help: There is a physical table on the database for each transparent table. The names of the physical table and the logical table definition in the ABAP/4 Dictionary agree. All the business and application data is stored in transparent tables.
  • Structure.
    From SAP help: No data records exist on the database for a structure. Structures are used for the interface definition between programs or between screens and programs.
  • Cluster table.
    From SAP help: Cluster tables contain continuous text, for example documentation. Several cluster tables can be combined to form a table cluster. Several logical lines of different tables are combined to form a physical record in this table category. This permits object-by-object storage or object-by-object access. In order to combine tables in clusters, at least part of the keys must agree. Several cluster tables are stored in one corresponding table on the database.
  • Pooled table.
    From SAP help: Pooled tables can be used to store control data (e.g. screen sequences, program parameters or temporary data). Several pooled tables can be combined to form a table pool. The table pool corresponds to a physical table on the database in which all the records of the allocated pooled tables are stored.
  • General view structure.
    From SAP help: A structure is generated for a view during activation. This structure is used as the interface for the runtime environment. It is not usually displayed in the ABAP Dictionary.
  • Append structure.
    From SAP help: An Append structure defines a subset of fields which belong to another table or structure but which are treated as a separate object in the correction management. Append structures are used to support modifications.

Stock Transfer between plants in SAP ERP

Posted on by
1

Stock Transfer from a plant to another plant in SAP – Intra Company and Cross-Company Codes

For some reasons, we may need to transfer stock from one plant to another plant. In SAP ERP, it can be done using several procedures. Each procedure is different with others and may fit with a certain situation or business requirement. In this post I will explain about the procedures of how to transfer stock between plants in SAP ERP, so you can choose the best procedure according to your business requirement.

In SAP ERP, stock transfer from one plant to another plant can be done through:

  1. Stock Transfer Posting

    Stock transfer posting can be done from one plant to another plant. The plants can be in a same company code, or cross company codes.

    Stock transport posting can be done solely with SAP MM Inventory Management component, no other SAP components or modules involved.

    The main advantage of this procedure is the simplicity of the process.
    We can transfer stock between plant with:

    • One-step procedure

      • With one-step procedure, we can transfer stock from one plant to another plat in a single transaction. The transaction can be done with MIGO, MIGO_TR, or MB1B tcodes. The movement type for the transaction is 301 (and 302 to cancel it).
      When the transaction is posted, the stock in issuing (from) plant will be decreased and the stock in receiving (destination) plant will be increased directly.

    2. Continue reading →

Automated procurement in SAP ERP software

Posted on by
1

An SAP MM user can create a Purchase Requisition (PR) with ME51N transaction code (t-code). In SAP, the PR can be processed automatically into a Purchase Order (PO) with less effort by buyer/purchaser (which often the different party than the PR creator). But, to make this run well, there are some prerequisites that must be fulfilled before, which are:

Continue reading →