Friends,

As we know about info record and order unit.

In this blog we are going to learn how to make a info record with different price for different order unit.

Some times We purchase a material in different different order unit, Suppose BAG, KG, BOX etc etc. And the vendor will take the different amount for the different order unit.

As suppose vendor will take Rs. 50 for KG, Rs. 100 for BAG and Rs. 500 for BOX.

Here you can maintain the the price for different order unit in info record. So we don't have to maintain manually price for the different order unit.

Prerequisites

1. We have to maintain variable order unit in material master record.

Go to MM02, in purchasing tab

Maintain the variable order unit as 2-Active with own price.

Then maintain the unit of measure as per your requirement.

Go to Additional Data-Units of measure

Maintain conversion as per your requirement.

2. Create Info record

We have to create info record for this material with particular vendor.

Go to ME11. Give the vendor, material, purchase organization and plant and then press enter.

You can see in general data, the variable order unit as 2 is automatically copied from material master.

Then press enter, you will go to the Purch. Organization Data 1 tab.

Here enter you all information, and give the price for KG in net price field.

Then press Condition tab

After pressing condition tab, a pop-up will shown to you (like as above screen shot) with all unit which you have maintained in material master.

We have to maintain different price in condition for each unit of measure.

Now select the KG and press Choose (You can double click on KG)

Here maintain the price for KG (it will automatically picked because we have maintained price for KG in Purch. Organization Data 1 tab).

Then press back button.

You will go back to the Purch. Organization Data 1 tab. Then again press condition tab. Again you will see the pop-up box as shown in previous figure.

Now double click on the unit of measure BAG.

Here maintain the price for BAG. As I have already said we will pay Rs. 100 for order unit BAG.

Then press back again.

You will go back to the Purch. Organization Data 1 tab. Then again press condition tab. Again you will see the pop-up box as shown in previous figure.

Now double click on the unit of measure BOX.

Maintain the price for BOX. As I have already said we will pay Rs. 500 for order unit BOX.

Now save your info record.

Result

Now we are going to create a Purchase order for the same vendor and material.

Go to ME21N, fill the all details.

In line item, enter all details without price..

Firstly the default order unit will come PC and we can see the rate as well as maintained in info record.

We can see the price Rs. 50 has come to Purchase order as we have maintained Rs. 50 for PC in info record.

Now I am going to change the order unit as BAG in this PO.

Here you can see our price is automatically changed with Rs. 500, as we maintained Rs. 500 for BAG in info record.

Now I am going to change the order unit as BOX in this PO.

We can also see here, the price will changed automatically with Rs. 500 as we have maintained Rs. 500 for BOX.

Now you can save your PO with this order unit as per your requirement.

In this way we can maintain different price in info record for different order unit.

No need to do any configuration, Just create the info record properly. You will able to fetch the price according to the info record.

Thanks

Dev Patra

How to Add Custom Header Text in PR:

    In Standard SPRO path for PR texts, only item level texts can be defined. If you want to add new header text in PR, you may follow the steps explained below:

   Go to SE75 transaction. Select 'Text Objects and ID's' and click on change button. Now, select the object 'EBANH' and click on 'Text ID's'

   Now, click on create button or F5 .

/servlet/JiveServlet/showImage/2-14451767-301268/123.png

   Enter the Text ID and Description and save.

/servlet/JiveServlet/showImage/2-14451767-301269/123.png

   Now go to ME51N and check the header. The new text id will be displayed there.

/servlet/JiveServlet/showImage/2-14451767-301270/123.png

Please note that the request will be a work bench request.

Regards,

AKPT

LIS (Logistic Information Systems) for Purchasing:

Information Systems are tools for analyzing and gathering specific data in different areas like purchasing, inventory etc.

Concept of Info Structure:

The info tables will start with S, followed by 3 digit integer. Example for standard info structures are S012, S013, S031, S032, S033 etc. The same can be used for ZReports also. Apart from standard info structures, user can define user defined info structures too. The user defined info structures should start with S followed by a three digit number. From S000 to S500 are reserved for standard.

In case of user defined info structures, once the info structure is created with required updating, it will be updated along with standard tables during every relevant transaction. The same info tables can be used for other reporting purposes like zReports etc.

Analysis of Standard Info Structures:

Transaction: MCDG (Path: SAP Easy Access – Information Systems – Logistics – Purchasing – Tools – Flexible analysis – Evaluations – MCDG (Execute)

Enter the standard evaluation structure and evaluation method.

System will propose the standard characteristics.

Execute.

Output:

Apart from standard info structure, we can define user defined info structure based on business requirement. For example, we can define an LIS table to update full purchasing cycle - from PO to Invoice.

Creation of user defined Info Structure:

Step1: Create Field Catalog – Characteristic catalog.

        A field catalog defines a group of relevant fields from the application. You can thus use a mixture of fields from any document hierarchies.

        Here, you can define the key fields required in the table.

Transaction Code: MC18

• Enter name for field catalog.
• Select Application from F4 List.

Application 02 for purchasing.

Press ENTER.

Click on “Characteristics”:

Now, select the required field and click on “Copy”, or double click on the field.

The selected Items will be visible with tick mark:

The fields can be selected from multiple tables.

Once all the fields required are selected, click on “Copy+Close

Now, click on “ Copy”

Save the characteristics field catalog.

Step 2: Create Key Figures.

            Key figures are values with particular relevance to business. These will be output of the report / analysis.

Eg: Invoiced amount, net order value, number of deliveries

Transaction Code: MC18

Enter the field catalog name, description and select the application.

Press ENTER.

Click on “Key Figures”

Select the required fields as explained in the previous step and click on “Copy+close”

Save the key figures.

Step 3: Create Info Structure

            The area in which data is collected in the Logistics Information System.

            An information structure defines a group of fields and is used for collecting and reducing data from an operative application such as sales or purchasing. It forms the basis for analyses and evaluation and includes:

• A period unit, giving the structure a time reference
• Characteristics, information with reference to which other information is cumulated (In short, it is the selection screen – Selection Parameters)
• Key figures, information that is accumulated with reference to characteristics (This is the output fields)

Transaction Code: MC21

• Enter info structure name – A four digit key between S501 and S999 (up to S500, is reserved for standard)
• Info Structure description.
• Application – Press F4 and select the Application. 02 stand for purchasing. The Applications available are listed below:

• Select the info-structure type. The following are the examples:

          - Standard type ( ‘ ‘)

                      - Rebate Processing (B)

                      - Type 'Transfer to SAP BW' (T)

Please Note that the info structure type cant be changed once its created.

• Planning Possible Indicator: Indicator that determines if an information structure is relevant in flexible planning. If an information structure is created with this indicator, it can be supplied with planning data (standard).

It is not possible to change the planning characteristic after creating the information structure.

Enter the details and press ENTER.

• Click on characteristics. Here, you can select the fields to be displayed in the selection screen of the report.

Double click on the characteristics field catalog created in the first step.

Double click on the fields to be selected to the selection screen. The fields can be selected from any field catalog.

  You can select maximum of 9 field characteristics.

Once required fields are selected, click on “Copy + Close”

Now, click on “Copy”

Please follow the part 2 document: How to Create an LIS info structure - Purchasing - Part 2

This is a continuation for the document: How to Create an LIS info structure - Purchasing - Part 1

Now, Select the Key figures (Output fields)

Double click on the key figures created in the first step:

• Double click on the fields to be selected to the selection screen.
• You can select the fields from any key figures.

Click on Copy + Close.Click on “Copy”

Generate the info structure:

Now, click on “Generate” as shown below:

• System will ask the package name. Enter the package name and click on “save button”
• If it’s a test system and you don’t want to transport, you can save it as local object.

Table Generate Log will be displayed:

• If there is no error, the table will be generated.
• Go back to the previous screen and save .

• You may check the table created (here, S973) in SE16.

• Check the number of entries:

Step 4:Create updating:

     By defining the update process, you define the flow of statistical data from the application to the information system. Means you can define when the data to be updated in the info table created in the previous step.

            The definition of the update rules depends on the information structure and update group.

Update rules consist, for example, of the source field, the event which triggers the update, requirements and formulas.

            Once you have defined the update rules, the corresponding update programs are automatically generated.

Transaction Code: MC24

• Enter the info structure created in the previous step.
• Select the update group: (standard update group: PURCH - Purchase Order header Update Group)

• Press ENTER.

Now, you can define the update rules:

• Click on the “Rules for Key Fig”

Select the required fields from F4 list manually or click on “Suggest Rules”

  Click on next key figure as shown below:

Repeat the same process for all key figures and click on "Copy":

Now define the update rules for characteristics for each key figure:

Select the first key figure and click on "Rules for characteristics"

Repeat the Rules for the characteristics for each key figure.

Click on “Generate” as shown below:

Generation Log will be displayed:

Go back and click on “Activate Updating”

Place the cursor on the info structure created and go to details:

Maintain the update rules as shown below:

Note:

  In the update rules, you could find the following options:

1. Period split:

        Here, you can define the period for which the report / info table to be analyzed. If you select "day", you can analyze based on date, if you select week, you can analyze based on week and so on. The corresponding period only will be updated in the table.

2. Updating:

        Here, you can define the time / sequence when the info table to be updated. The following options are available.

• No Updating: The info table wont be updated.
• Synchronous Updating (V1 update): The info table will be updated simultaneously along with standard tables after every relevant transaction. In this case, the document update will be terminated in case there is any error in the info table update, as in case of standard tables.
• Asynchronous Updating (2) (V2 update) : Here, the info table is updated after actual document update, that is the document update and the statistics update take place in different tasks. In case any error occurs in info table update, it doesnt have any effect on actual document update. However,  It doesnt require any scheduled job for update.
• Asynchronous Updating (3) (V3 update) : Here, the document update and info table update are carried out separately. The difference between V2 update and V3 update is that in V3, the update can be carried out at a later time. In short, it is a collective update with a separate (scheduled) job.

     Here, I choose the period as "Month" in order to analyze the report on monthly basis and the update as "Synchronous Update" in order to update the table simultaneously along with standard tables.

Save the update:

Now, the configuration part is over:

Testing:

Complete a purchasing cycle and check whether the table is updated correctly: (Create PO – GR – Invoice) and check the table in SE16

To  Analyze the report:

Transaction Code:: MCSJ  (Path: Easy Access - SAP Menu - Information Systems - Logistics - Purchasing - Tools - MCSJ_User Defined Analysis

(for purchase - MCSJ, for Sales - MCSI )

Select  the info structure.

Enter the selection parameters and execute:

Click on “Switch drill down” for further analysis.

You may select any other analysis criteria for analysis.

You may change the output layout as below:

Go to MCSJ and select the info structure: and click on “User Settings”

Click on Key figures for setting the output layout.

Note: 1. You may follow the same logic for creation of info structure for other areas like inventory, LIV, sales  etc.

          2. For more details about LIS transporting, refer the documentation in the path: SPRO- Logistics General --> Logistics Information System (LIS) --> Logistics Data Warehouse - "Technical information about the transport of LIS objects"

Also, refer the notes: 37845 - Technical Information: Transporting Info Structures and 50237 - Techn. info.: transport of update, field catalog

          3. For further FAQ, please refer the following notes:

552152 - FAQ: General questions for LIS

552503 - FAQ: Questions for updating and reporting in LIS

Note: Currently, the info table will be updated from the date the info table is created. If you want the info table to be updated with previous data, you may follow the procedure explained in the doc: Update History Data to user defined LIS (Purchasing)

Reference: SAP Library - Logistics Information System (LO-LIS)

Please refer the below documents for how to create a user defined LIS info structure:

How to Create an LIS info structure - Purchasing - Part 1

How to Create an LIS info structure - Purchasing - Part 2

The scope of the current document is limited to historical data update to user defined LIS table.

Once a new LIS table is generated, the LIS table doesn’t contain historical data. If you check the table in SE16, the number of entries will show it.

In-order to update the historical data to this LIS table, you may proceed as explained below:

Follow the path: SPRO – Logistic General – Logistic Information System (LIS) – Logistic Data warehouse – Data Basis – Tools – Set up Statistical Data – Application Specific set up of statistical Data.

Transaction OLI3 for updating Purchasing LIS

Execute set up of the corresponding application.

Enter the info structure name to be updated along with other criteria as shown below:

The following are the important fields:

1. Save Under Version: Here, you can mention the version name. The version name will be displayed/updated in info table. You can save the new data update in a different version name. Also, you have the option of copy / delete versions.

    The version name for statistical set up should start with "&(" since other versions are used with planning.

    If you update with different version name, the same documents will be repeated with different version name.

2. Delete / Create Indices indicator: Here, you may set whether the secondary indices already existing in the info table are to be deleted and recreate. If you set this indicator, and if there is already data existing for a combination, the secondary indices (like vendor, order qty etc in the example) are deleted and recreated again. It is mainly for performance improvement.

3. Name of Run: Here, you can mention a name for the update run. This is useful when an update run is terminated and you use the same name as name of run next time, system will use the data which is already determined.

4. Re determination of update group: You can set this indicator, the system will redetermine the update groups for the documents which are processed at the time of the statistical set up. If this indicator is not set, there can be an inconsistency with the documents processed at the time of the statistical set up.

5. Update Documents: this indicator will update the update group in the already existing document. This indicator is mandatory if you modify the update group characteristics in customizing. If this indicator is not set, the existing documents will be updated in table as per previous update rules.

6. Block all Documents: This indicator is useful when you are updating the info structure parallelly to the business. If you set the indicator, all the documents relevant for the statistical update will be blocked till the update is completed. The block will be released once the update run is completed.

    If you are doing the info structure update in your business hours, this indicator is mandatory.

Execute.

Now, check the LIS table in SE16. The table will be updated with historical data.

The same details will be available for analysis in MCSJ transaction.

These days, I read documents related with M8 system messages , tolerances , invoice reduction etc.

In this document , i work on implementation and configuration SAP MM Logistic Invoice Verification. My example contains a example which it prevents different postings based on quantity and amount. We will get a problem that i want to post bigger amount, sap will not give permission with error messages finally invoice reduction will solve our this problem.

You can get details : MM-IV-LIV-CRE Set Tolerances for Incoming Invoice - ERP SCM - SCN Wiki

I have a PO , my person posted a material document 100 qty.

     In Miro , can you post more quantities and amounts ? Is it related your tolerances ? Not at all.

     If posting exceed your tolerances , you can post but it is blocked. If not, you can not prevent. Sometimes , you can not be aware of tolerances when you can post fastly. It is dangerous.

Examples :

1 - Amount is bigger than PO.

2- Quantity and amount are bigger than migo and po values.

     What can i do ?

     Firstly , check your LIV system messages.

     You can update your M8 / 81-82-83 messages with ERROR also if you get them.

     MM/Logistic Invoice Verification/Invoice Block/Set tolerance limits

     * Please check DQ and PP tolerance keys.

     However , it is not enough to prevent posting . You have to maintain your LIV system messages.

     * I configure M8 messages with ERROR.

     * When i post our invoices , sap will not give permission...

     ** Unfortunately , i have to post some like a weigher result , vendor errors invoices with variances , how can i solve this problem ?

     **Sometimes , you can post your invoices with tolerance even though you implement system messages. Invoice reduction can help you.

     *Select layout : Invoice reduction , Correction ID : 2 Vendor error - reduce invoice ,Invoice amount Acc to Vendor , however you can use similiar way for quantities. Sap will create one more fi record for differences.

     Results :

    ** Configurations :

     You have to configure your T030 table with RKA transaction (OBYC tcode) and invoice document types.

     I add RK document type for invoice reduction. (OMR4)

     However, if you want to update some datas to implement in your country like a tax rates ..

     You have to update records with enhancement implementation program LMRMCF07 .

     I hope that it can be benefical for your business life thoughts.

     Thanks a lot for spending times ...

     Regards.

     M.Ozgur Unal

We know about mass changes.

We can change a field value from mass changes with the given value..

But some business logic needs one field value should be same as a another field.

Here with the help of some coding we can carry mass changes from one field to another field.

Jürgen Sir replied in this thread the exact procedure, which helps me a lot to make the document, its almost help me 90% to make this document.

A lots of thanks to Jürgen Sir.

Lets discuss about requirement and step by step procedure.

Suppose we have two fields in material master.

1. Reorder Point (MARC-MINBE)

2. Maximum Lot Size (MARC-BSTMA).

We have some value in field Maximum Lot Size (MARC-BSTMA)..

Here we can see we have a value only field Maximum Lot Size (MARC-BSTMA), bur we haven't any value in Reorder Point (MARC-MINBE)

Now we have enter the value to Reorder Point (MARC-MINBE) field. But the condition will be that Value should be same as field Maximum Lot Size (MARC-BSTMA) with respective material.

It means for material TUPUCOZ5215, BSTMA value is 500, so the field value of MINBE will be also 500 for this material.

And also for material TUPUCOZ5216, BSTMA value is 600, so the field value of MINBE will be also 600 for this material.

Here we can change the value for field MINBE as respective to field BSTMA.

Use t-code MASS (you can use MM17 directly for material mass changes)

Use the Object Type as BUS1001

You can see the initial screen

Click on the tab Fields, and select the field MARC-MINBE and MARC-BSTMA

Now press Execute.

Give your all material with respective plant.

Then press execute.

You can see the initial screen appear for mass changes.

We can see our two fields Reorder Point and Maximum Lot size.

We can see we have some value in field Maximum Lot Size.

Now we have to fill out the field Reorder Point as copy from Maximum Lot Size with respective material.

Now Move your mouse pointer to Reorder Point, then click on Enter Formula/FORM Routines.

Press the option as shown in above figure or you can also find this from Application menu as shown as below screen.

Now you can see a pop-up will come which will be like below screen.

As we have to change the value for field Reorder Point, so we have to write a code for this field.

Now click on the ABAP which is right side of Reorder point.

Now the screen will be like below.

Its a ABAP FORM routine.

We have to just add our own logic here..

As we have to fetch the field value from field Maximum Lot Size (MARC-BSTMA), So we have write as like below screen shot.

As you can see I have just entered a line where X value will be as per value of BSTMA.

Don't forget to give the dot (.)at the last of this line.

Then just press Ctrl+S or you can select Save from table as below screen shot.

After press save, you will see the back screen as shown below

Then press continue or enter.

You can see a text will come on the Reorder point field.

Now our coding part is done.

Now you have to deselect the Maximum Lot Size field. If you continue without deselect this field, then the field value for Maximum Lot Size will remove.

Now press the option - Carry Out Mass Changes.

(Note : Press only one time on Carry Out Mass Changes, if you press twice on this option, then the value will remove)

Now we can see the result.

Our Reorder Point replaced with the same value as Maximum lot Size with respective material.

Now we can save our data.

Press or you can press Ctrl+S.

Now you can see a success message like as below

Now our all data saved.

Lets check the MARC table and the value for Reorder Point and as well as Maximum Lot Size.

Here we can see our Reorder Point (MINBE) changed as per Maximum lot Size (BATMA) as per respective material.

Its not only for material master..

It will applicable for all mass changes.

Thanks and Regards

Dev Patra

Scenario:

Many of the industries will have requirement to import goods free of cost. This may be free samples, warranty replacement etc. Even though the goods are sent free of cost by the vendor, company needs to pay duty to the customs based on the Assesable value of the material. Also, there can be other delivery costs also.

There is no standard solution to address this. There are many solutions for this in SCN like creating standard import PO and posting credit memo after vendor invoice verification, maintaining an amount of 0.01 for gross price in PO and changing the duty values in MIRO, posting customs invoice in FB60 etc. We have recently addressed this through a different way which seems to be more logical and convenient. Just thought of sharing this, as this may be helpful to you.

Process:

First of all, a new pricing procedure needs to be defined for this purpose.

1. Create a condition type copying PBXX for Material Assesable Value (Say ZBXX).

2. Create Pricing procedure without PB00 and PBXX. Include ZBXX and mark it as statistical. Subsequently add customs duty conditions and set subtotal 9 for customs duty condition.

3. There should be a purchasing org exclusively for free of cost import (This may look odd, but this is required to trigger different pricing for same vendor for FOC and normal purchase.)

4. Assign this schema to vendor schema group and the schema group for the above purchase org.

5. In vendor master purchasing data for the above purchase org, set currency as local currency (Customs vendor currency) and set invoicing party as customs vendor.

Now when you create PO for free of cost import, enter the vendor and purchase org created for FOC import. When you enter the material assesable value, customs duties will be calculated accordingly. When GR is posted, there will not be any liability on vendor. Liability of the customs duty will be on the customs vendor. Proceed with invoice verification as usual.

Regards,

Sudeep.

SAP MM / Partner Determination

This document explains the settings for partner determination in the vendor master. When you create a business partner, assign data to an account group. An account group decides the business partner. Partner roles refered as partner functions. Various partner roles can be stored in vendor master like Payee , Invoicing party , Goods Supplier and Ordering Address etc.

Related notes :

938652 : PI partner Pur.Org.Data not relevant for Partner Determination

673062 : Partner determination selects blockd/deleted partners

542645 : ME22N : No partner determination when checking/saving PO

431351 : ME22N : Change PO , no new partner determination

420058 : ME21N error ME366 after changing the document type

407600 : Message determination of partners in STO

401734 : ME21N  STO , partners disappear

394091 : Partners are not transferred from vendor master

376319 : ME21N partner from reference document not found

117537 : ME27 : No partner determination w.stock transp.orders

FAQ :

-- OSS Note 459350 - FAQ : Partner determination in purchasing

Info :

Some partner roles are predefined in SAP :

*Vendor (VN) , Ordering address (OA) , Invoicing party (IP) , Different payee (AZ), Contact person (CP), Employee responsible (ER) , Intrastat  declaration (GS )

Intrastat declaration : Intrastat is the system for collecting information and producing statistics on the trade in goods between countries of the European Union (EU)

Partner determination can be used for price determination, message determination, address determination, statistics. If you define a lot of partner roles, you can select one of them like a default. When someone creates a purchasing document, default value is seen in the list.

To use partner determination , you will need to define a partner schema for purchasing document. When you define schemas, the previously created partner roles are assigned to the schema. If account group is assigned a partner schema, sap checks whether the role you enter in schema or not. You can receive a error message, if sap does not find related role.

1- Define Partner Schemas :

SPRO / Materials Management / Purchasing / Partner Determination / Partner Settings in Purchasing Documents / Define Partner Schemas

Select partner schema 0002 and choose Partner Functions under the Procedure node in the Dialog Structure tree.

      INDICATORS:

      No change indicator : If you want to prevent changes in partner defined in the vendor master record and prevent deleting partner roles, it is set.

      Mandatory indicator : Whether a partner role is mandatory in a vendor master or PO.

      Higher level indicator : If partner role does not been found in plant or sub-range level, sap looks for partner role at purchasing organization level. Hpwever, higher level is used process of automatic creation PO.

     End indicator : If it is set , partner role is defaulted from vendor master when document is saved or checked. It is useful when different data is added in the vendor at the plant/vendor subrange. Whether all items contain same plant or subrange. Invoicing parties are not determinated until end of document process PO so end incator might change it.

2- Define Settings for Vendor Master Records :

Firstly , configure your 'Vendor Account Group' for Partner determination procedure.

SPRO / Logistics - General / Business Partner / Vendors / Control / Define Account Groups and Field Selection (Vendor)

     How can i select L1 partner schema for Purchasing organization ?

     Spro/ Mm / Purchasing / Partner determination / Partner Settings in Vendor Master Record

     Firstly , define partner roles.

     Secondly , Assign Partner Schemas to Account Groups .

3- Message Determination :

- Determine partner schema for account group.

- Ordering address partner role (OA) must be maintained. The role is allowed for account group.

- Check whether partner schema is used to determine partner roles for purchasing document type.

Output a message to  this partner , you need to create a message condition record in purchasing master data. MN04 will help you.

Firstly, decide output type , after that specify dependent information for message determination.

Related subjects :

You can enter alternative freight vendor for planned delivery costs when you post a good receipt.

M8 / 776 (IP must have allowed in partner role) and 777 (IP has partner role in Purchase Order) system messagescheck partner roles as soon as invoice verification. They can be configurated as a warning or error.

Configuration steps:

Access Sequences

SPRO > Material Management> Purchasing > Message > Output Control>Access Sequences>Define Condition Table for Purchase Order

Message Type

SPRO-> Material Management> Purchasing > Message > Output Control>Message Types>Define Message Type for Purchase Order

Message Determination Schemas

1. Message Determination Schemas

SPRO> Material Management> Purchasing > Message > Output Control > Message Schema >Define Message Schema for Purchase Order > Maintain Message Determination Schema

2. Assign Schema to Purchase Order

SPRO-> Material Management> Purchasing > Message > Output Control >Message Schema >Define Message Schema for Purchase Order> Assign Schema to Purchase Order

Partner Roles per Message Type

SPRO > Material Management> Purchasing > Message > Output Control > Partner Roles per Message Type >Define Partner Role for Purchase Order

**Condition Record

SAP Easy Access Menu > Logistics > Material Management > Purchasing > Master data >Messages > Purchase Order> MN04-> Create

Now you create PO (ME21N) and save it.

4- Allowed partner roles

You can do with Account group : Field reference , Permitted partner roles

After that specify partner role VN is allowed for account group ZVMU.

SPRO / Materials Management / Purchasing / Partner Determination / Partner Roles / Define Permissible Partner Roles per Account Group

Spro / MM / Partner Determination / Partner Settings in Purchasing Documents / Assign Partner Schemas to Document Types

*** Also , you can assign to UB document type for STO.

5- Vendor settings and an example for price determination

For instance , i used a vendor master 'T-K55001' also i maintained Partner Function datas in master data.

DP : Default partner

I set a discount for Invoicing party. MEKJ tcode will help us.

If a partner role is found at the end, the system does not update the prices.

I created a PO to Vendor , but discount is implementable for Invoicing Party.

     Thanks to Mr.Jurgen for his valuable feedback.

     Regards.

     M.Ozgur Unal

Hi all,

We know about purchase document text. This text can be maintain in header level and item level.

Text can be maintain on Info record, Material, PR, PO, SA, Contract etc..

Its stored into a table STXH and STXL, but its little difficult to find out with compare these two tables.

SAP has a another way where we can get a report for these texts with all details.

Lets discuss details about it.

Suppose we have a lots of material, some material has a text and some material hasn't.

How can I found the material which has a text and what is the text for those particular material.

Lets display one material for the tab Purchase Order text.

Here is the text for material master for this particular material.

Now just click on the Editor, You can find the option bottom of the screen in left side. Its look like

Now the screen will looks like as below screen shot.

Then in application bar, press Goto - Header

Now you can see a pop-up screen will appear. Which will contain some information.

Note the text id for Material.

Standard Text ID for material purchase order text is BEST.

Note that.

Now go to SE38 and give the program name RSTXTC3.

Now press execute.

Here enter the Text ID (which you have got from material master)

Then again press execute.

Here we can get a list of all material which has a purchase order text.

Now press the option Additional information

After pressing additional information, you can see all information including the purchase order text with respective to material..

Now you can also copy the all information into excel sheet for further process.

You can also change the text from here.

Just select the line item and press Change Text .

The above information for Material master - purchase order text.

We can also get a list for all purchasing document.

Like for Purchase Order/ Contract/ Sch. Agree./RFQ- Header Text:

The selection field will be

Because of header text, we have to select object as EKKO adn text ID as same as the way for material master - purchase order text.

You can also select the text as purchase order number+Line item number (Purchase order number will be 10 characters and line item number will be 5 characters)

For Purchase Order/ Contract/ Sch. Agree./RFQ- Item Text:

The selection field will be

For Purchase Requisition - Header Level : Use Object = EBANH and Text ID = B01.

For Purchase Requisition - Item Levem : Use Object = EBAN and Text ID = B01.

For Purchase Info Record - Info Record Note : Use Object EINA and Text ID = AT.

For Purchase Info Record - Purchase Order Text : Use Object EINE and Text ID = BT.

For Vendor Master - Accounting note : Use Object LFA1 and Text ID = 0001.

For Vendor Master - Purchasing memo : Use Object LFA1 and Text ID = 0002.

In this way we can get a report for all purchasing document's text and as well as master data's text.

Thanks and Regards

Dev Patra

Hello Friends.

As we know about the tables and fields.

We know all information are stored in a table and a particular field. Its very difficult to memorize all table and all field.

We can get this from F1 - Technical Information for table and field.

The fields names are always shown correct.. But for table name, sometime its shows the structure name instead of table name.

For an example

When we press F1 on field Short Text on screen ME51N. We can see as well the Short Text field name, but in table portion we can see a structure name not a table name.

As we know the field Short Text (TXZ01) is stored in EBAN table, but we can't find this from F1 screen.

Its shown a structure name as MEREQ3211GRID.

In that situation, we have to find the original table name for this field.

Here I am giving the 3 way to find the original table for any field.

Way 1:

When the above pop-up come, double click on the "Data Element".

Now you can see a screen of Display Data Element.

Now you can see the data element screen for the field Short Text.

Now Press Where-Used List. This is on application menu bar

You can see another pop-up screen will come Which is like below screen.

As we need the table name, so remove the all tick without  Table Fields.

Now press enter or continue.

After pressing enter, you will find a list..

This list shows you on which table the field is used.

It means in the listed tables, you can find the field Short Text (TXZ01)

We can see 15 Hits comes on the screen.

It means the field TXZ01 is used in 15 tables.

Now We can find the table as per our requirement. We need the table for ME51N (Purchase Requisition)..

We can see Purchase requisition is also listed in the list.

And we can also see the table name for Purchase Requisition.

If you have found a many number of hits, Then you can search for your table with given description.

Like as if you want to know the table for PR, then you can search as purchase requisition

In that way we can find the original table name for this particular field.

(Note : I know I have given an easy field and table name, But I am just sharing the procedure to see the original table name for a particular field)

Way 2 :

This is a similar way as way one.

Just First step is little different.

If you know the field name, then we can enter it directly in SE11 screen and we can get the Table name.

In SE11 screen, On the field Database Table, give the field name (Where usually we give the table name)

Now Press Display.

You can see the Display Data Element screen.

You can do the further process which we have already discuss in the Way 1 section.

Way 3 :

This is little different way..

Use t-code SE84 or SE15.

You can see a initial screen is appear for Object Navigator.

Now from here select the option

ABAP Dictionary-Fields-Table Fields.

-

Now Double click on Table Fields.

You can see a screen is will come on right side of the screen.

Here give the field name as TXZ01.

Then Press execute.

Now you will get the all table list for the field TXZ01.

Here you also use the search option which I have discussed in way 1.

In These above 3 way, you can find the original table name for a particular field.

So don't worry when you see a structure name in table field, just use one option from above and you will get the table original table name.

Thanks and Regards

Dev Patra.

Dear Friends,

In this document I have listed the possible accounting entries that can be achievable by using standard configuration in MM pricing procedure.

In this example I have taken a condition type similar to Freight condition type FRA1 and made changes to Condition Class, Condition category, Plus/Minus, Accrual Indicator & statistical indicator in calculation schema.

Where      Mat      is      Stock account,

               Gr/ir      is      GR/IR clearing account

               G/L       is      G/L Account assigned to Accruel TEK

               Ven       is      Vendor Account

There are always a different kinds of requirements from finance people about FI postings. If any such requirement which was not satisfied by above configuration please comment here. Also comment possible workarounds for such common requirements. Please also mention if I have missed some other standard configuration possibilities of Different G/L posting.

-End Of Document

Thanks For Reading. Please share your reviews & feedback....

Regards

Satish

Material status

A quantity of a given material at a Plant can exist in one of three basic stock statuses:

1. Unrestricted
2. Quality Inspection (QI)
3. Blocked

For the below explanation this is called ‘stock status’.

Batch status

When you activate batch management, this introduces a complication, a batch of a given material may have the status Unrestricted or Restricted, which is independent of the stock status.

This is the batch status.

Representation in MMBE

This can cause confusion for people when viewing stock using transaction MMBE.  If you know the following, then it will help:

For a material quantity with unrestricted stock status, the batch status will dictate which column the batch quantity is shown in (see NICK1 versus NICK2)

For a material quantity with the stock status QI or Blocked, the batch status does not effect which column the quantity is shown in.  The material batch is always shown in the appropriate stock status column.

If you want to know the batch status of material with a stock status of QI or Blocked:

Select the batch.

Select  Extras \ Display Batch from the menu bar.

And view the Batch status section of the Basic Data 1 tab.

Note backwards navigation is available and can be used to return to the MMBE display via the Back button.

Friends,

As we know about info record and order unit.

In this blog we are going to learn how to make a info record with different price for different order unit.

Some times We purchase a material in different different order unit, Suppose BAG, KG, BOX etc etc. And the vendor will take the different amount for the different order unit.

As suppose vendor will take Rs. 50 for KG, Rs. 100 for BAG and Rs. 500 for BOX.

Here you can maintain the the price for different order unit in info record. So we don't have to maintain manually price for the different order unit.

Prerequisites

1. We have to maintain variable order unit in material master record.

Go to MM02, in purchasing tab

Maintain the variable order unit as 2-Active with own price.

Then maintain the unit of measure as per your requirement.

Go to Additional Data-Units of measure

Maintain conversion as per your requirement.

2. Create Info record

We have to create info record for this material with particular vendor.

Go to ME11. Give the vendor, material, purchase organization and plant and then press enter.

You can see in general data, the variable order unit as 2 is automatically copied from material master.

Then press enter, you will go to the Purch. Organization Data 1 tab.

Here enter you all information, and give the price for KG in net price field.

Then press Condition tab

After pressing condition tab, a pop-up will shown to you (like as above screen shot) with all unit which you have maintained in material master.

We have to maintain different price in condition for each unit of measure.

Now select the KG and press Choose (You can double click on KG)

Here maintain the price for KG (it will automatically picked because we have maintained price for KG in Purch. Organization Data 1 tab).

Then press back button.

You will go back to the Purch. Organization Data 1 tab. Then again press condition tab. Again you will see the pop-up box as shown in previous figure.

Now double click on the unit of measure BAG.

Here maintain the price for BAG. As I have already said we will pay Rs. 100 for order unit BAG.

Then press back again.

You will go back to the Purch. Organization Data 1 tab. Then again press condition tab. Again you will see the pop-up box as shown in previous figure.

Now double click on the unit of measure BOX.

Maintain the price for BOX. As I have already said we will pay Rs. 500 for order unit BOX.

Now save your info record.

Result

Now we are going to create a Purchase order for the same vendor and material.

Go to ME21N, fill the all details.

In line item, enter all details without price..

Firstly the default order unit will come PC and we can see the rate as well as maintained in info record.

We can see the price Rs. 50 has come to Purchase order as we have maintained Rs. 50 for KG in info record.

Now I am going to change the order unit as BAG in this PO.

Here you can see our price is automatically changed with Rs. 500, as we maintained Rs. 500 for BAG in info record.

Now I am going to change the order unit as BOX in this PO.

We can also see here, the price will changed automatically with Rs. 500 as we have maintained Rs. 500 for BOX.

Now you can save your PO with this order unit as per your requirement.

In this way we can maintain different price in info record for different order unit.

No need to do any configuration, Just create the info record properly. You will able to fetch the price according to the info record.

Thanks

Dev Patra

This is a continuation for the document: How to Create an LIS info structure - Purchasing - Part 1

Now, Select the Key figures (Output fields)

Double click on the key figures created in the first step:

• Double click on the fields to be selected to the selection screen.
• You can select the fields from any key figures.

Click on Copy + Close.Click on “Copy”

Generate the info structure:

Now, click on “Generate” as shown below:

• System will ask the package name. Enter the package name and click on “save button”
• If it’s a test system and you don’t want to transport, you can save it as local object.

Table Generate Log will be displayed:

• If there is no error, the table will be generated.
• Go back to the previous screen and save .

• You may check the table created (here, S973) in SE16.

• Check the number of entries:

Step 4:Create updating:

     By defining the update process, you define the flow of statistical data from the application to the information system. Means you can define when the data to be updated in the info table created in the previous step.

            The definition of the update rules depends on the information structure and update group.

Update rules consist, for example, of the source field, the event which triggers the update, requirements and formulas.

            Once you have defined the update rules, the corresponding update programs are automatically generated.

Transaction Code: MC24

• Enter the info structure created in the previous step.
• Select the update group: (standard update group: PURCH - Purchase Order header Update Group)

• Press ENTER.

Now, you can define the update rules:

• Click on the “Rules for Key Fig”

Select the required fields from F4 list manually or click on “Suggest Rules”

  Click on next key figure as shown below:

Repeat the same process for all key figures and click on "Copy":

Now define the update rules for characteristics for each key figure:

Select the first key figure and click on "Rules for characteristics"

Repeat the Rules for the characteristics for each key figure.

Click on “Generate” as shown below:

Generation Log will be displayed:

Go back and click on “Activate Updating”

Place the cursor on the info structure created and go to details:

Maintain the update rules as shown below:

Note:

  In the update rules, you could find the following options:

1. Period split:

        Here, you can define the period for which the report / info table to be analyzed. If you select "day", you can analyze based on date, if you select week, you can analyze based on week and so on. The corresponding period only will be updated in the table.

2. Updating:

        Here, you can define the time / sequence when the info table to be updated. The following options are available.

• No Updating: The info table wont be updated.
• Synchronous Updating (V1 update): The info table will be updated simultaneously along with standard tables after every relevant transaction. In this case, the document update will be terminated in case there is any error in the info table update, as in case of standard tables.
• Asynchronous Updating (2) (V2 update) : Here, the info table is updated after actual document update, that is the document update and the statistics update take place in different tasks. In case any error occurs in info table update, it doesnt have any effect on actual document update. However,  It doesnt require any scheduled job for update.
• Asynchronous Updating (3) (V3 update) : Here, the document update and info table update are carried out separately. The difference between V2 update and V3 update is that in V3, the update can be carried out at a later time. In short, it is a collective update with a separate (scheduled) job.

     Here, I choose the period as "Month" in order to analyze the report on monthly basis and the update as "Synchronous Update" in order to update the table simultaneously along with standard tables.

Save the update:

Now, the configuration part is over:

Testing:

Complete a purchasing cycle and check whether the table is updated correctly: (Create PO – GR – Invoice) and check the table in SE16

To  Analyze the report:

Transaction Code:: MCSJ  (Path: Easy Access - SAP Menu - Information Systems - Logistics - Purchasing - Tools - MCSJ_User Defined Analysis

(for purchase - MCSJ, for Sales - MCSI )

Select  the info structure.

Enter the selection parameters and execute:

Click on “Switch drill down” for further analysis.

You may select any other analysis criteria for analysis.

You may change the output layout as below:

Go to MCSJ and select the info structure: and click on “User Settings”

Click on Key figures for setting the output layout.

Note: 1. You may follow the same logic for creation of info structure for other areas like inventory, LIV, sales  etc.

          2. For more details about LIS transporting, refer the documentation in the path: SPRO- Logistics General --> Logistics Information System (LIS) --> Logistics Data Warehouse - "Technical information about the transport of LIS objects"

Also, refer the notes: 37845 - Technical Information: Transporting Info Structures and 50237 - Techn. info.: transport of update, field catalog

          3. For further FAQ, please refer the following notes:

552152 - FAQ: General questions for LIS

552503 - FAQ: Questions for updating and reporting in LIS

Note: Currently, the info table will be updated from the date the info table is created. If you want the info table to be updated with previous data, you may follow the procedure explained in the doc: Update History Data to user defined LIS (Purchasing)

Reference: SAP Library - Logistics Information System (LO-LIS)

Please refer the below documents for how to create a user defined LIS info structure:

How to Create an LIS info structure - Purchasing - Part 1

How to Create an LIS info structure - Purchasing - Part 2

The scope of the current document is limited to historical data update to user defined LIS table.

Once a new LIS table is generated, the LIS table doesn’t contain historical data. If you check the table in SE16, the number of entries will show it.

In-order to update the historical data to this LIS table, you may proceed as explained below:

Follow the path: SPRO – Logistic General – Logistic Information System (LIS) – Logistic Data warehouse – Data Basis – Tools – Set up Statistical Data – Application Specific set up of statistical Data.

Transaction OLI3 for updating Purchasing LIS

Execute set up of the corresponding application.

Enter the info structure name to be updated along with other criteria as shown below:

The following are the important fields:

1. Save Under Version: Here, you can mention the version name. The version name will be displayed/updated in info table. You can save the new data update in a different version name. Also, you have the option of copy / delete versions.

    The version name for statistical set up should start with "&(" since other versions are used with planning.

    If you update with different version name, the same documents will be repeated with different version name.

2. Delete / Create Indices indicator: Here, you may set whether the secondary indices already existing in the info table are to be deleted and recreate. If you set this indicator, and if there is already data existing for a combination, the secondary indices (like vendor, order qty etc in the example) are deleted and recreated again. It is mainly for performance improvement.

3. Name of Run: Here, you can mention a name for the update run. This is useful when an update run is terminated and you use the same name as name of run next time, system will use the data which is already determined.

4. Re determination of update group: You can set this indicator, the system will redetermine the update groups for the documents which are processed at the time of the statistical set up. If this indicator is not set, there can be an inconsistency with the documents processed at the time of the statistical set up.

5. Update Documents: this indicator will update the update group in the already existing document. This indicator is mandatory if you modify the update group characteristics in customizing. If this indicator is not set, the existing documents will be updated in table as per previous update rules.

6. Block all Documents: This indicator is useful when you are updating the info structure parallelly to the business. If you set the indicator, all the documents relevant for the statistical update will be blocked till the update is completed. The block will be released once the update run is completed.

    If you are doing the info structure update in your business hours, this indicator is mandatory.

Execute.

Now, check the LIS table in SE16. The table will be updated with historical data.

The same details will be available for analysis in MCSJ transaction.

A frequent misunderstanding is the assumption that the unrestricted use stock is identical with available stock

Unrestricted use stock is a stock type, that can be used for everything, has no restriction based on its condition. Other stock types are quality stock and blocked stock.

Available stock can be equal, can even be more than unrestricted use stock, can be less than unrestricted use stock. You define yourself in the ATP checking rules how you calculate the available part of your stock

A look into our warehouse:

and the same in the stock overview transaction MMBE

You see 263 are in unrestricted use, 1 is in quality inspection.

But how much is available?

Depends on the point of view.

If you are a CSR and you want to check how much of this can be sold with the next order or if you are  checking the stock/requirements list e.g. as a planner.

On the left you see transaction CO09 availability overview used by the CSR, on the right the Stock/Requirements list from the planner

Click the picture to enlarge, if you can't read it

CO09 transaction shows 262 available, MD04 shows 264 available in the stock line on top. And both do not equal the 263 unrestricted use stock.

Why is this?

CO09 actually starts with 263, you can see this in Rec./reqd qty column, the ATP quantity got immediately reduced by the reservation of 1. And it did not include the quality inspection stock.

This is defined in OVZ9 Availability check control. The availability check 02 is coming from the material master, the 01 is my selected checking rule when executing CO09.

As you can see, safety stock is defined as available here, and on the right it is defined what is considered  as incoming and outgoing movements.

Contrary MD04, the stock requirements list shows 264 as available, but why? Because Quality inspection stock is included into available stock by definition of Net requirements calculation.

Additionally you can define in customizing transaction OMI8 Available stocks if you include even stock in transfer, blocked stock and restricted use stock (this is a batch status)

Let us enter a purchase order of 20 and see how the situation develops.

Both transactions show the purchase order as MRP element, both numbers go up by 20.

CO09 shows now 282 and MD04 shows 283

Wait...CO09 shows as well 262, why 2 different ATP quantities in CO09?

Because CO09 shows a total at plant level, and it shows a total at storage location level (and it will have a total at batch level if the material is batch managed)

And since no storage location was entered in the purchase order, only the available stock at plant level goes up.

And why is a purchase order considered as available stock? See your checking rule for CO09, purchase orders are marked to be considered as incoming movement. And in MD04 it is considered too, the available stock goes up at the date when the goods are planned to be delivered.

Next experiment. I add a safety stock of 50 in the material master MRP2 view. What happens to CO09 and MD04?

As expected, based on the checking rule definition, CO09 does not change because safety stock is defined as available.

But MD04 got a new line showing the safety stock, and reduces this quantity from the available quantity.

One last activity, I add a sales order for 100

And in both transactions the sales order can be seen as a reduction from the available quantity...at plant level

It is not reduced from the storage location level, because the storage location was not entered in the sales order.

I hope this rough overview with these small examples helps you to know that unrestricted use stock is different from available stock.

Friends,

As we know about info record and order unit.

In this blog we are going to learn how to make a info record with different price for different order unit.

Some times We purchase a material in different different order unit, Suppose BAG, KG, BOX etc etc. And the vendor will take the different amount for the different order unit.

As suppose vendor will take Rs. 50 for KG, Rs. 100 for BAG and Rs. 500 for BOX.

Here you can maintain the the price for different order unit in info record. So we don't have to maintain manually price for the different order unit.

Prerequisites

1. We have to maintain variable order unit in material master record.

Go to MM02, in purchasing tab

Maintain the variable order unit as 2-Active with own price.

Then maintain the unit of measure as per your requirement.

Go to Additional Data-Units of measure

Maintain conversion as per your requirement.

2. Create Info record

We have to create info record for this material with particular vendor.

Go to ME11. Give the vendor, material, purchase organization and plant and then press enter.

You can see in general data, the variable order unit as 2 is automatically copied from material master.

Then press enter, you will go to the Purch. Organization Data 1 tab.

Here enter you all information, and give the price for KG in net price field.

Then press Condition tab

After pressing condition tab, a pop-up will shown to you (like as above screen shot) with all unit which you have maintained in material master.

We have to maintain different price in condition for each unit of measure.

Now select the KG and press Choose (You can double click on KG)

Here maintain the price for KG (it will automatically picked because we have maintained price for KG in Purch. Organization Data 1 tab).

Then press back button.

You will go back to the Purch. Organization Data 1 tab. Then again press condition tab. Again you will see the pop-up box as shown in previous figure.

Now double click on the unit of measure BAG.

Here maintain the price for BAG. As I have already said we will pay Rs. 100 for order unit BAG.

Then press back again.

You will go back to the Purch. Organization Data 1 tab. Then again press condition tab. Again you will see the pop-up box as shown in previous figure.

Now double click on the unit of measure BOX.

Maintain the price for BOX. As I have already said we will pay Rs. 500 for order unit BOX.

Now save your info record.

Result

Now we are going to create a Purchase order for the same vendor and material.

Go to ME21N, fill the all details.

In line item, enter all details without price..

Firstly the default order unit will come PC and we can see the rate as well as maintained in info record.

We can see the price Rs. 50 has come to Purchase order as we have maintained Rs. 50 for KG in info record.

Now I am going to change the order unit as BAG in this PO.

Here you can see our price is automatically changed with Rs. 500, as we maintained Rs. 500 for BAG in info record.

Now I am going to change the order unit as BOX in this PO.

We can also see here, the price will changed automatically with Rs. 500 as we have maintained Rs. 500 for BOX.

Now you can save your PO with this order unit as per your requirement.

In this way we can maintain different price in info record for different order unit.

No need to do any configuration, Just create the info record properly. You will able to fetch the price according to the info record.

Thanks

Dev Patra

To create a new item text type for purchase orders  execute OLME to go get to the purchasing related IMG activities

Here drill down to Purchase order > Text for purchase orders > Define Text Types for Item Texts

Click the button "New Entries" , enter a sequential number and a description and save.

then go to next customizing step OLME > Purchase order > Text for purchase orders > Define Copying Rules for Item Texts

Select your text type then click the folder for Text linkages

Click New Entries , enter a sequence number then move the cursor to gray source text field and press F4. Find your text type in the pop-up, select it, save.

Continue with next customizing step OLME > Messages > Texts for Messages > Define Texts for Purchase Order

Open the folder for "Texts for Document Item"

Click New Entries , enter the print operation (this decides if the text is only printed when you create new message or when you create a change message - see F4 search help to see the alternatives)

Enter the combination of purchasing document type,  item category   which shall get your new text type.

then enter the Text object, which is EKPO for purchase order items and your text ID, which can be found in F4 search help. It is actually a F followed by the sequential number you used when defining the new text type.

Enter a print sequence. this defines where this text is printed on your form among the other item texts that you may have defined here.

Save.

Here you are actually done with customizing.

Next step is to create a new purchase order and make use of your new text type.

We had defined this text to be a manual text, not copied from any other source object, so just find your text type in the item text tab of your purchase order and enter some text.

Click the Print Preview button to see where this text is on your form:

With unchanged standard settings and print forms, the text will show up right away. This behavior may be different with modified or own print programs and forms.

Please refer the below documents for how to create a user defined LIS info structure:

How to Create an LIS info structure - Purchasing - Part 1

How to Create an LIS info structure - Purchasing - Part 2

The scope of the current document is limited to historical data update to user defined LIS table.

Once a new LIS table is generated, the LIS table doesn’t contain historical data. If you check the table in SE16, the number of entries will show it.

In-order to update the historical data to this LIS table, you may proceed as explained below:

Follow the path: SPRO – Logistic General – Logistic Information System (LIS) – Logistic Data warehouse – Data Basis – Tools – Set up Statistical Data – Application Specific set up of statistical Data.

Transaction OLI3 for updating Purchasing LIS

Execute set up of the corresponding application.

Enter the info structure name to be updated along with other criteria as shown below:

The following are the important fields:

1. Save Under Version: Here, you can mention the version name. The version name will be displayed/updated in info table. You can save the new data update in a different version name. Also, you have the option of copy / delete versions.

    The version name for statistical set up should start with "&(" since other versions are used with planning.

    If you update with different version name, the same documents will be repeated with different version name.

2. Delete / Create Indices indicator: Here, you may set whether the secondary indices already existing in the info table are to be deleted and recreate. If you set this indicator, and if there is already data existing for a combination, the secondary indices (like vendor, order qty etc in the example) are deleted and recreated again. It is mainly for performance improvement.

3. Name of Run: Here, you can mention a name for the update run. This is useful when an update run is terminated and you use the same name as name of run next time, system will use the data which is already determined.

4. Re determination of update group: You can set this indicator, the system will redetermine the update groups for the documents which are processed at the time of the statistical set up. If this indicator is not set, there can be an inconsistency with the documents processed at the time of the statistical set up.

5. Update Documents: this indicator will update the update group in the already existing document. This indicator is mandatory if you modify the update group characteristics in customizing. If this indicator is not set, the existing documents will be updated in table as per previous update rules.

6. Block all Documents: This indicator is useful when you are updating the info structure parallelly to the business. If you set the indicator, all the documents relevant for the statistical update will be blocked till the update is completed. The block will be released once the update run is completed.

    If you are doing the info structure update in your business hours, this indicator is mandatory.

Execute.

Now, check the LIS table in SE16. The table will be updated with historical data.

The same details will be available for analysis in MCSJ transaction.