ABAP Performance Test: Hashed Tables vs Database Buffers

There are two significant techniques to avoid repetitive access to database records: Hashed internal tables and database buffers.

If we decide to use the former method, we need to get the database record into a hashed internal table. Whenever we need to access the record, we read the internal table instead of the database table.

If we decide to use the latter method, all we need to do is to activate the table buffer in SE11. If we do that, the accessed data is cached on the application server, and the cache is used whenever possible. Thus, database access is reduced. There are exceptional cases where the buffer is bypassed, but that’s beyond the scope of this article.

Wondering how they compare in terms of performance, I created a fully buffered database table with example data.

I also wrote a program, which accesses the data using both techniques and compares the runtime.

It turns out that hashed access is 3-4 times faster than database buffering.

You can use the attached source code yourself and repeat the test; I would like to hear about any disproving results.

REPORT  zdummy01.

CLASS main DEFINITION.

  PUBLIC SECTION.

    CLASS-METHODS execute.

  PROTECTED SECTION.

  PRIVATE SECTION.

    CONSTANTS:

      c_do_times TYPE i     VALUE 100,

      c_matnr    TYPE matnr VALUE 'M1'.

    CLASS-DATA:

      go_text  TYPE REF TO cl_demo_text,

      gv_begin TYPE i.

    CLASS-METHODS:

      hash,

      select,

      start_chrono,

      stop_chrono.

ENDCLASS.                    "main DEFINITION

CLASS main IMPLEMENTATION.

  METHOD execute.

    go_text = cl_demo_text=>get_handle( ).

    start_chrono( ).

    hash( ).

    stop_chrono( ).

    start_chrono( ).

    select( ).

    stop_chrono( ).

    go_text->display( ).

  ENDMETHOD.                    "execute

  METHOD hash.

    DATA:

      lt_dummy

        TYPE HASHED TABLE OF zdummy01

        WITH UNIQUE KEY primary_key COMPONENTS matnr.

    FIELD-SYMBOLS:

      <ls_dummy> LIKE LINE OF lt_dummy.

    go_text->add_line( 'Starting hash read' ).

    SELECT * INTO TABLE lt_dummy FROM zdummy01.

    DO c_do_times TIMES.

      READ TABLE lt_dummy

        ASSIGNING <ls_dummy>

        WITH TABLE KEY primary_key

        COMPONENTS matnr = c_matnr.

    ENDDO.

  ENDMETHOD.                    "hash

  METHOD select.

    DATA ls_dummy TYPE zdummy01.

    go_text->add_line( 'Starting select' ).

    DO c_do_times TIMES.

      SELECT SINGLE *

        INTO ls_dummy

        FROM zdummy01

        WHERE matnr EQ c_matnr.

    ENDDO.

  ENDMETHOD.                    "select

  METHOD start_chrono.

    GET RUN TIME FIELD gv_begin.

  ENDMETHOD.                    "start_chrono

  METHOD stop_chrono.

    DATA:

      lv_diff  TYPE i,

      lv_difft TYPE cl_demo_text=>t_line,

      lv_end   TYPE i.

    GET RUN TIME FIELD lv_end.

    lv_diff = lv_end - gv_begin.

    WRITE lv_diff TO lv_difft LEFT-JUSTIFIED.

    go_text->add_line(:

      'Runtime result:' ),

      lv_difft ).

  ENDMETHOD.                    "stop_chrono

ENDCLASS.                    "main IMPLEMENTATION

START-OF-SELECTION.

  main=>execute( ).

Continue reading

Unified Legacy Decommissioning using SAP Information Lifecycle Management

Introduction

In today’s Enterprise Information is critical to business with multiple SAP and Non SAP Enterprise applications. These applications have both structured and unstructured data used for business, legal and audit requirement.

The challenge now before all Enterprise, is to understand how their data evolves, determine how it grows, monitor how its usage changes over time, and decide how long the data should be retained in the system. Whilst adhering to all the rules and regulations that now apply to that specific structured and unstructured data.

ILM has become especially critical to enterprises in the last two or three years. Compliance mandates, and especially legal reporting requirements, have changed and increased dramatically in number. This forces companies to think more carefully about how they compile their legal reports, what the ideal legal reporting process should look like, and how this all fits into the management of information.

SAP Information Lifecycle Management (ILM) is designed to address these challenges with a combination of processes, policies, software and hardware so that the appropriate technology shall be used for each phase of the lifecycle of the data.

Typical challenges (or) risks that are to be addressed in a data lifecycle:

◉ How to ensure that the data that is required for an audit or regulatory compliance are readily available or the data that must be deleted have actually been purged from the systems?
◉ How to ensure that data from the legacy systems is still be reported
◉ How to address the increasing TCO of the unsupported legacy application and unstable legacy infrastructure?

SAP NW ILM is introducing a new approach to streamline Productive SAP System archiving and legacy system decommissioning, new support for consolidated data storage environments using SAP Sybase IQ, and a new tool to helps ILM administrators efficiently manage the information life cycle and data archiving processes.

SAP Information Lifecycle Management (SAP ILM) is based on the following pillars: ·

◉ Data archiving (active data and system)
◉ Retention management (end-of-life data)
◉ Perform e-discovery and set legal holds
◉ System decommissioning (end-of-life system)

SAP ILM Key Features: ◉ Policy Management ◉ Data Destruction ◉ Legal Holds & eDiscovery ◉ Support for Sybase IQ ◉ Audit compliant decommission of legacy SAP and Non-SAP systems ◉ Flexible reporting on legacy systems tax content and product liability content

SAP ILM Key Benefits: ◉ Archive obsolete data to enhance performance ◉ Reduction in HANA appliance footprint. ◉ Support data retention rules by creating separate archives based on varying data lifetimes ◉ Preserve compliance auditing and reporting capabilities for decommissioned systems ◉ Reduce the cost and risk of legal discovery ◉ Reduction in overall TCO

Unified approach for Legacy Decommissioning for SAP and Non-SAP environment

SAP NW ILM provides a new unified approach for retiring the Legacy SAP and Non SAP environment using the SAP SLT (System Landscape Transformation), Legacy Extraction workbench (CDE archive Objects) and SAP ILM Retention warehouse with ILM Certified stored based on Sybase IQ / SAP HANA or any SAP Certified ILM Store.

The new decommissioning solution helps to automate many manual steps, reduce the risk of errors, increase the overall data quality, and lower the overall costs and duration of decommissioning projects. The typical legacy decommissioning process is as below:

◉ Perform Data profiling to identify the scope of the data / tables to be archived

◉ Extract and load data from legacy system using SLT into the mapping tables in to target SLT environment.

     ◉ The process of mapping non-SAP content to SAP structures is automated, but can be fine-tuned to ensure correct reporting and data display later in the decommissioning process.

◉ Perform Legacy Extraction workbench (LEW) configuration to define archiving objects

◉ Define Audit Area, ILM Policies and Rules

◉ Perform LEW run to create archive objects with retentions rules

◉ Transfer Archive files to SAP ILM RW and store in ILM Certified store (Sybase IQ)

The Meta information of the legacy tables are transferred through special archiving objects that enables to retain the Meta information of the legacy tables in ILM RW for retrieval and reporting.

Retrieval and Reporting

In the newer version of SAP NW ILM, delivers enhanced reporting to address various legal and auditing reporting requirement. There are multiple reporting options including local reporting, accelerated / business user reporting and BW reporting

ILM Provides a Choice for Different Reporting Needs

• Flexible
• Use pre-delivered/existing BW content or check out increasingly available HANA content
• Use available BO portfolio and existing export functions (AIS)
• Choose between basic (local) reporting or complex queries based on (easy) modelling
• Load only data that is needed for the reporting purpose
• Comprehensive
• Extend the scope of reporting by SAP HANA (e.g. open items without sec. indices
• Report both live SAP and legacy data (SAP and Non-SAP data)Support of new scenarios (e.g. partial migration/conversion)
• Fast
• Increase the overall performance with SAP HANA (DB)
• Shorten project implementation time through content reuse

Innovative Integrate archiving solution using SAP ILM and Sybase IQ for Production environment

The customer used to use NLS for OLAP and Archivelink (or) WebDAV storage for OLTP applications. With the new SAP ILM Retention management solution for operational (live) archiving with Sybase IQ, address the challenge of having two dedicated storage for OLAP and OTLP environment.

Netweaver ILM functionality has the option to store operational data on Sybase IQ (using ILM Store Retention Services), along with the new analytical data using new native BW NLS interface for Sybase IQ (available as of SAP NW 7.30 SP09 and NW 7.31 SP07).

Storing your data in SAP Sybase IQ enables customer to consolidate the storage infrastructure on a single platform and avoid the software, hardware, network, and operations requirements associated with the integration of third-party compliant stores.

Key Benefits

◉ Unified Storage for OLTP and OLAP archiving

◉ Reduction of the volume of data and archive indexes stored

◉ Improved Performance for data archiving and accessing archived data

◉ Increased search capabilities

Continue reading

How to Create and Read Flat IDocs from Files in SAP

I have recently come  across the need to “manually” move an IDoc for testing purposes form one SAP system to another. The two systems were in two different environments and not planned to be connected network wise. So we needed a way to export and import an IDoc.

The idea was to export the IDoc on system A to a file and then import it in system B from that file. It seemed an easy task, but turned out to be quite tricky. I haven’t found much help from searching online or in SAP docs but enough to put something together that worked at the end. I’d like to share this here in a step-by-step guide.

Please note that this is only for manual testing purposes for single cases and not intended to serve as any kind of IDoc interface.

We firsts export an existing IDoc from source system, download the file to the local computer and then upload it to another system:

1. How to export a flat IDoc file in SAP ERP:

SAP GUI, Transaction Code: WE19

1. Load an existing Idoc (see we02) via idoc number.

2. Click on “inbound file” (note: this is actually confusing. You’re going to write a file to the file system, but the function is called inbound file. But it’s all right and you can go ahead.)

3. Enter a path on the server (use transaction AL11 to find a suitable path) and a filename. The file name can be chosen freely. Execute the function and ignore the error about the not found port!

4. Download the exported file to your local machine using Transaction Code: CG3Y (or FM ARCHIVFILE_SERVER_TO_CLIENT as per a reader’s comment).

You can also use AL11 which displays a list of all available files. Select the file and then click the button marked below (“Download File as Text”):

5. Target is a patch on your local machine.

6. Choose ASC for ASCII mode.

7. Execute the download.

8. You can now edit the file on your PC if needed, or further process/distribute it. Or you can now upload it e.g. to another SAP system and edit it there before processing (see next chapter).

2. Upload and Inbound Process a Flat IDoc File

1. Upload the file using transaction code CG3Z (or FM ARCHIVFILE_CLIENT_TO_SERVER as per a reader’s comment) e.g. to a temp directory.

2. Use t.code WE19 and select “File as Template”.

3. Enter the path where you’ve uploaded the file and the filename.

4. The test tool displays your IDoc, you can also change it here.

5. You also need to create the control record (I don’t go into details of this here as this is required knowledge about the standard IDoc processing and can be found elsewhere). To create the control record, click on the first line in the editor and enter the data as needed (of course, change the name to your IDoc’s message type. Here it’s a business partner IDoc) :

6. When you’re ready, click “Standard Inbound”. If a partner profile (WE20) exists, it will be processed after executing the function (or collected for later processing). See the status of the new IDoc in WE02.

Continue reading

SD Pricing : Cross Module Reference Condition Type (Config)

Some times we may need to copy price from MM Condition record to SD condition Record. There can be various reasons as mentioned below:

1) In India, Excise calculation Base needs to be kept same for Intra Company STO / Inter Company STO and Billing Document.

2) Base Price needs to be kept same Bet’n STO and Invoice.

3) Certain Discount or Surcharge needs to be copied from MM to SD or Vice Versa.

When first time I tried , I faced difficulty but got successful in the same, so thought to share it with you also.

Below are the steps which I had followed:

1. Created Identical Condition Type in SD and MM. It needs to be identical considering SAP needs controlling point like Condition Class / Calculation Type.

MM Condition Type:

MM Access Sequence:

SD Condition type: (It is identical to MM Condition type, Only Ref. Condition Type field is updated with MM Condition type and Application as Purchasing.)

SD Access Sequence: (Observe here, I have used Same Condition Table which was created in MM., If you will press F4, You will not see those Condition Table but If you will directly enter the same, System will allow MM Condition Table in SD as well.)

SD Pricing Procedure:

2) Maintain Condition Record for MM Condition Type by MEK1 T-Code.

3) Maintain Condition Record for SD Condition type by VK11 with Zero Price. (Why Do we need to maintain this ?? 

Ans: In SAP For Populating condition value from Other Module condition record, system search that if this condition has been proposed in Pricing or not. That’s why we need to maintain Condition record with Zero value so it get’s Populated in Pricing.)

4) Create STO and reach till Billing Creation with Standard way. Check the Pricing now in Invoice.

As per above Screenshots, system has called MM Condition record to SD Pricing.

Continue reading

Free Goods Determination in SAP CRM

This document will cover steps for creating free goods determination procedure and conditions in SAP ERP and downloading the same in SAP CRM. The Sales order would be created in SAP CRM and the free goods would be determined for the same.

SAP ERP:

1. Maintain Free Goods Condition Table:

SPRO – SD – Basic Functions – Free Goods – Condition Technique for Free Goods – Maintain Condition Tables

Select the fields combining which you want the free goods conditions to be created. For eg. you can check the standard condition table, 010, wherein  the fields Sales Org, Distribution Channel, Customer and Material is used for creating free goods conditions.

2. Maintain the Access Sequence:

SPRO – SD – Basic Functions – Free Goods – Condition Technique for Free Goods – Maintain Access Sequence

Select the condition tables created above and maintain them in the desired sequence in the access sequence.

3. Maintain the Condition Type

SPRO – SD – Basic Functions – Free Goods – Condition Technique for Free Goods – Maintain Condition Types

Create a Condition Type and assign the Access Sequence created above to it.

4. Maintain Free Goods Procedure

SPRO – SD – Basic Functions – Free Goods – Condition Technique for Free Goods – Maintain Pricing Procedure

Create a Procedure and maintain the Condition Types created above in desired sequence.

5. Activate Free Goods Determination:

SPRO – SD – Basic Functions – Free Goods – Condition Technique for Free Goods – Activate Free Goods Determination

Maintain the Free Goods Determination Procedure created above against the combination of Sales Area/Doc. PP and Cust. PP.

6. Create Free Goods Record

Go to Transaction VBN1. Create a free goods record. The below screenshot shows a record which would give inclusive free goods. Suppose a customer purchases 2 quantities, then 1 quantity would be considered as free. The Customer would be charged for only one quantity.

This will be stored in table, KOTN<condition table>. In our case, condition table was 010, hence the table will be KOTN010.

SAP CRM:

1. Download the condition record by using adaptor object: DNL_COND_N010. If you are using custom condition tables then create a new adaptor object same as this and maintain the custom table in it.

2. Download access sequence, condition tables and condition types by using: DNL_CUST_CND_FG.

The condition records when downloaded from ERP will appear in CRM in table, /1CN/CCF<condition table>. In our case the table is SAP010 as it is standard table which was used, hence the table will be /1CN/CCFSAP010. The records once downloaded can be seen in it.

Create Sales Order in CRM WebUI for the same combination of Customer/Sales Area and Material:

A Sub-item gets created automatically as soon as it meets the criteria of free goods determination. In the below case, actually 2 quantities were entered, the system detects the free goods determination and creates a sub-item of quantity 1 as free item. The customer is charged for only one quantity. This is inclusive free goods scenario. In Exclusive, the customer would have got an additional quantity as set by the conditions. 

Continue reading

Key performance efficiency for a work center in SAP PP R3

Every manufacturing line works with certain amount of efficiency and every industrial engineer or production departments knows this well in manufacturing shop floor about it. And while doing capacity planning and production planning in shop floor, planners will consider this factor to calculate the processing time of a production of a product. This efficiency factor percentage can be considered for any standard value key in a work center in SAP.

Most of us may be aware of it, but this is an attempt to make people who are in search of it & looking for it. Many people asked this question in the forum on how to introduce this OEE or key performance factor.

Apart from advanced options of SAP OEE & MII, if you considers option available in SAP PP R3, We can build this in work center.

Calculating this factor through SAP PP R3 is not possible, but if we know the percentage factor we can input this as a key performance efficiency in work center in front of standard value key, which can be considered for scheduling.

What it does? Considering this factor, wherever this work center is used and this standard value key timings are maintained in routing, while creating planned order or production order, overall time for this operation gets multiplied by this factor and increases operation processing time by this factor.

For example i maintain 50% efficiency for below standard value keys

Find below are the routing master data for base quantity 1

See the result of it in production order for order quantity of 1 EA, standard routing ti me for machine & labor gets doubles due to 50% efficiency.

Configuration for this scenario in SAP:

You can define key performance efficiency rate in below configuration path or in transaction OP28

Define performance efficiency factor

Click on Performance efficiency rates & validity and select this efficiency rate validity and with settings of whether this parameter considered while calculating cost of the operation or activity wherever this work center with efficiency rate is used and whether this parameter to be considered in Scheduling.

What are the benefits of it?

1. We can consider the performance efficiency rate for a work center, which is equal to actual in shop floor.

2. Production planning times are accurate, and planning will consider actual timings of the operations.

3. Helps in scheduling of production orders on shop floor etc

We can also do this for the combination of recipe (routing) and material, if you do not want this at work center level. Any feedback or questions welcome on this, and i am happy to share this with you all. Few of automotive or other industry look for this efficiency factor to be considered in planning, so i believe this will be good input.

Continue reading

Production Planning Innovations in SAP S/4HANA for Faster and More Efficient Manufacturing

Manufacturing is under increasing pressure to deliver faster, better, and smarter. From the rise of additive manufacturing and robotics, to e-commerce and same day delivery, the list of technology and market trends reshaping the manufacturing function is only growing. These disruptions create new challenges for classical manufacturing especially around production planning processes.

But as these new technologies present new challenges, they also present new opportunities. 3D printing may be disrupting centralized manufacturing, but it also gives manufactures more freedom to bring new more complex geometrical designs, that have been difficult to create with subtractive manufacturing techniques, all while reducing inventory levels, time to market and waste. By simplifying the underlying data model of their manufacturing systems, companies can better tap into their data supply and capitalize on new trends. All of this is possible now, with the application support that allows for streamlined, agile manufacturing.

SAP S/4HANA has come a long way since its first iteration as a purely financial module. Starting with the 1511 release, we began focusing on simplified supply chain and manufacturing solutions, architectures, and data models. Now, with the release of 1610, we are taking these enhancements and innovations to another level. In this post, I want to focus on material requirements planning (MRP), the process by which a manufacturing company analyzes its sales orders, demand forecasts and inventory to determine which materials and components it needs to purchase, produce in house or transfer from a neighboring plant to deliver on its order commitments.

Classical ERP vs. S/4HANA

In the classical ERP solution, MRP has been extremely effective in offering manufacturing customers with basic production planning capabilities that were quick to implement and easy to use. The downside is that MRP assumes infinite manufacturing resources. MRP’s lack of acknowledgement of production environment constraints such as skilled labor pool or manufacturing capacity sets up an obviously unrealistic scenario that must then be addressed by a secondary application such as Production Planning and Detailed Scheduling (PP/DS) in SAP Advanced Planning and Optimization (SAP APO). This is one of the manufacturing inefficiencies we are addressing with the 1610 release.

To better illustrate the difference between old and new, let us look at a hypothetical bicycle manufacturer called Speedy Bikes. Let us say, Speedy Bikes gets an order to build a bicycle and deliver it by noon the same day. Let’s also assume for simplicity that the Bill of Material (BOM) of Speedy Bikes consists of only 3 components as in figure 1.

Figure 1. Bicycle Simplified Bill of Material

In the classical ERP solution, the sales order is passed on to MRP which explodes it into its BOM, compares that against inventory levels and then determines what components need to be built in house, transferred from another plant or ordered externally to deliver the bicycle. Taking into account the dependability between the different BOM levels, MRP works its way backward from the delivery date and builds a production plan like the one in Figure 2.

Figure 2. Infinite MRP Planning in Classical ERP

That’s all fine, but now let us assume that one of the production lines used to build the wheels is unavailable or occupied between 9:30 to 10:30, and the chain cannot be installed until the wheels are ready because of the BOM dependency. The classical ERP solution in MRP would not be able to deal with such a constraint, because of its assumption of infinite resources. So, the MRP controller now has to rely on an advanced production solution, such as SAP Advanced Planning and Optimization (APO), to build a constraint based plan for the wheels and then go back into MRP to consolidate both plans. It is a cumbersome, time-consuming process that slows down production (Figure 3 and Figure 4).

Figure 3. Current Functional Model in Classical ERP

Figure 4. Finite Planning in APO PP/DS

If we look at the same scenario using SAP S/4HANA, that now has both constraint and unconstraint based planning embedded in one system, we see a much simpler and more efficient process (Figure 5). Now an MRP controller can build the entire bicycle and factor in the constraints on a particular material in a single place. In addition to being obviously simpler for the controller in terms of time, effort and user-experience, there are fewer errors in terms of transferring and consolidating data between two systems.

Figure 5. Unified Production functionality in SAP S/4HANA

If all this seems a little too confusing then watch this 2 min explanation video.

Innovation beyond integration

We have done more than take advanced functionalities from other areas of the SAP portfolio and embed them into S/4HANA. We are also delivering new innovations and functionality. One example of an innovation that we are bringing with MRP is the Truckload Optimized Purchase Orders Fiori app (Figure 6.).

Figure 6. Screenshot of new Truckload Optimization Fiori App

If your company places multiple orders for different materials with the same vendor, the truckload optimization app can bundle these orders in a way that optimizes the shipments of these materials. The app allows the MRP controller to enter in the load capacity of the trucks that the vendor uses to transfer the materials to your site, and the app considering the priority of the materials – optimizes them so that they consume fewer trucks or fewer shipments from the vendor.

Of course, the vendors bill for every truck transaction, so by minimizing the number of transactions, you can save on supply chain and transportation costs and, at the same time, ensure that you are fulfilling the orders of the highest priority among your sales orders.

The next level of efficiency

Essentially, when you look at the changes that S/4HANA has brought to production planning, it has simplified things by integrating constraint and unconstraint planning and it has offered users new capabilities and innovations that will make a big difference in manufacturing efficiency and effectiveness and the overall ability to respond to new technology and market trends.

Continue reading

Milestone Confirmation of the Process Order with Multiple Operations & with Multiple Phases involved

Business Process with Milestone Confirmation in the Process Order

For a Process Order, with multiple Operations & each Operation contains multiple Phases. During the confirmation of the last Phase of the last Operation, (which contains Milestone confirmation) System should automatically confirm all preceding Phases in all the Operations

Please find the sequence of steps involved in executing this Business Process/Requirement

 ---------- Requirements of the Master data settings ----------

1.Create Material Master for the FG/SFG & Raw Materials required, Transaction code: MM01

Created the below Materials for this scenario
For Example : Finished Product: FNP1 & Raw Material: QMATR1

2. Create the BOM for the finished Product, using he Transaction Code: CS01

Created the BOM for the Finished Product : FINP1, with the required set of components

3. Create the Resource using the Transaction Code: CRC1

Created/Used the below mentioned three Resources: 1111, 1112 & 1113, in the Plant 1100

Now, all the required Resources were set in the System

4. Create the Master Recipe, using the T Code: C201

Master Recipe settings plays important role, for this Milestone Confirmation, with the Multiple Operations with Multiple Phases. Need to maintain the Relationship between the Phases of all the operations involved.

This Mater Recipe creation can be the generic one, which can be used/assigned for multiple Header Materials that were going to be produced (or) specific to any one of the FG/SFG Material

In the initial screen, that is displayed, enter all the required fields & Press Enter

In the next screen, that is displayed, enter the required fields, then Press Enter

In the Next screen that is displayed, enter the required data

Enter all the sequence of Operations & the Phases of the respective Operations

Look at the details of the Control key settings

maintain the Relationship, between the Phase with Milestone Confirmation (0080 Phase), in all the other Phases (0020, 0040, 0060, 0070)

How to Maintain the Relationship (for Ex: for the Phase 0020)

Select the Phase & Click on the Relationships Icon (as shown)

In the next screen, that is displayed, enter the required data

Continue the same, for all the remaining Phases: 0040, 0060, and 0070

Make Sure, all the relationships are also updated in the Phase: 0080, as Predecessors

Click on Materials Tab, Enter the required Data

the Next Screen, that is displayed, If required, Check for Consistency & then save

Recipe was saved with group 50000162 and material FINP1.

Make sure, Material Master of the FG, is correctly updated with Production Version details

---------- Execution of the Transaction data ----------

1. Create the Process Order using the Transaction code: COR1

Create the Process Order using any of the standard steps/methods

Make sure, all the required data is entered, then Click on Save

Make sure, all the required data is entered, then Click on Save

2. Release the Process Order using the Transaction code: COR2

Go to Change mode of the Process Order,Click on Release Flag, then Click on save

3. Goods issue of the required components to the Process Order suing the T Code : MIGO

Material document 4900002598 posted

4. Confirmation of last Phase of the last Operation of Order, using Transaction Code: COR6N

With Milestone Confirmation

Enter the Process Order Number, Phase & Click on Actual data

In the Next Screen, that is displayed

Click on Save

Confirmation of order 70001034 saved

Look at the Operation confirmation details of the Order Now

5.Goods Receipt of the Header Material, can be done using the Transaction Code: MIGO

Enter the Process Order Number & the required details, press Enter

Click on Check & then Post.

Material document 5000000461 posted. & Process Order is updated with the Status: DLV

6. Confirmation of the Stock update using the Transaction Code: MMBE

Continue reading