topic BAPI_MOSRVAPS_SAVEMULTI3 in Application Development and Automation Discussions

BAPI_MOSRVAPS_SAVEMULTI3

kumaro412 — Fri, 18 Mar 2011 13:25:57 GMT

Dear all,

In APO, I use function BAPI_MOSRVAPS_SAVEMULTI3 to create planned orders ... This is working fine as long as I use 'normal' materials with default configuration ... But when I try to create a planned order based on a configurable material, I get an error starting as follows : "No configuration for configurable PP/DS ..." and followed by the material ...

Does this sound familiar to someone ?

What can I do to create a planned order with configurable materials ?

Thanks for all answers !

Greetz,

Kurt.

Re: BAPI_MOSRVAPS_SAVEMULTI3

Former Member — Thu, 24 Mar 2011 05:45:25 GMT

Please check whether Configuration exists for that particular material or not because PDS explosion raises error for configurable materials without configuration.I guess system is using this FM to check whether configuration is exist or not for any material ID.Just check with this FM /SAPAPO/CONFR_GET_CFG_SCENARIO.

Regards,

saurabh

Re: BAPI_MOSRVAPS_SAVEMULTI3

kumaro412 — Thu, 24 Mar 2011 15:52:06 GMT

When I try to use the function you mentioned, it doesn't seem to work ... Whatever material I enter, it doens't give a result ... Can you give me en example of what I have to fill and where I can find the correct values ?

Thanks in advance !!!

Re: BAPI_MOSRVAPS_SAVEMULTI3

Former Member — Thu, 24 Mar 2011 16:12:30 GMT

For this FM /SAPAPO/CONFR_GET_CFG_SCENARIO, you have to pass the Material ID which you will get from /sapapo/matkey table for any material.

Also please let me know in which parameter table of BAPI you are getting that error for Configurable PP/DS...

In Return table of BAPI you will see the parameter table name also in which you are passing the data to BAPI.

Regards,

Saurabh

Re: BAPI_MOSRVAPS_SAVEMULTI3

kumaro412 — Fri, 25 Mar 2011 08:10:01 GMT

Dear Saurabh,

First of all thanks for your assistance !

When I execute the BAPI, I get the error in the Return table of the BAPI ... These are the values of the errorline :

- Id = /SAPAPO/CULL1

- Number = 19

- Message = "No configuration for configurable PP/DS PDS FLXTATA03500Z BAWE FLXTATA03500Z"

- Message_v1 = "FLXTATA03500Z"

- Message_v2 = "BAWE"

- Message_v3 = "FLXTATA03500Z BAWE0001"

- Parameter = "ORDER_HEAD"

- Row = 1

The other fields have an initial value ...

Concerning the FM /SAPAPO/CONFR_GET_CFG_SCENARIO, I filled the IV_MATID with the MATID from /SAPAPO/MATKEY but I get no result at first ... I was forgotten to flag the upper-/lowercase ... At the end, the FM returns with "I" for ev_scenario and also "I" for ev_cfg_sys ...

Hopefully you know something more now to give me a solution ?

Thanks in advance !!!

Greetz,

Kurt.

Re: BAPI_MOSRVAPS_SAVEMULTI3

Former Member — Fri, 25 Mar 2011 12:57:01 GMT

Hi Kurt,

It seems the error is in ORDER_HEAD table while passing data into it.In Order_head you are only passing data which is mandatory as per documentation right? Yes.

I think the problem is with the fields starting with MASTER_<..> Becasue in Documentation,It is mentioned like that,

Fields that specify the primary product. This product is used for source determination (in-house production) and explosion

In RETURN table we are getting error for Configurable PDS, Is it checking whether PDS exists for this MATERIAL or not ?

I am not sure about it.Sorry I do not have further answer for this issue

you can try to pass the SOURCE_NAME field also in this BAPI because if this is empty then it is determining from MASTER_Product,MASTER_Location...

Regards,

Saurabh

Re: BAPI_MOSRVAPS_SAVEMULTI3

kumaro412 — Fri, 25 Mar 2011 13:27:39 GMT

Dear,

Thanks again for answering ...

I tried a lot of things, but it still doesn't work ...

This is how I call the function :

1) import parameters :

- LOGICAL_SYSTEM -> SCD800 (this is our APO-system)

- ORDER_TYPE -> 5 (this is for planned orders)

- EXT_NUMBER_ASSIGNMENT -> ' ' (I also tried this with flag on, but no change)

- COMMIT_CONTROL -> E

- PLNG_VERSION -> 000

- STRATEGY_PROFILE -> ' '

- NO_CREATE -> ' '

- CHECK_SOURCE_EXISTENCE -> X

- PLANNING_MODE_USAGE -> 0

- EVENT_CONTROL -> 1 (I also tried this with initial value, but no change)

2) export parameters :

- ORDER_HEAD -> 1 Entry (see below)

- ORDER_HEAD_X -> 1 Entry (see below)

- CFG_HEADERS -> 1 Entry (see below - to try it out)

- CFG_INSTANCES -> 1 Entry (see below)

- CFG_PART_OF -> 0 Entries

- CFG_VALUES -> 1 Entry (see below)

- CFG_VAR_KEYS -> 0 Entries

- CFG_BLOB -> 0 Entries

- CFG_REF_OBJECT -> 0 Entries

- MAPPING_DATA -> 0 Entries

- RETURN -> 0 Entries

- EXTENSION_IN -> 0 Entries

2a) order_head (fields with values - others are initial) :

ORDER_NUMBER : 1

ORDER_START_DATE : 03.09.2010 00:00:00

ORDER_END_DATE : 04.09.2010 00:00:00

MASTER_PRODUCT : FHVHTTA42400Z

MASTER_PLANT : BAWE

MASTER_SPEC_STOCK_IND : E

MASTER_SPEC_STOCK_KEY : 0050989453000010

MASTER_ORDER_QUANTITY : 1,000

MASTER_ATPCAT : AI

POSEX : 000001

2b) order_head_x (fields with values - others are initial) :

ORDER_NUMBER : 1

ORDER_START_DATE : X

ORDER_END_DATE : X

MASTER_PRODUCT : X

MASTER_PLANT : X

MASTER_SPEC_STOCK_IND : X

MASTER_SPEC_STOCK_KEY : X

MASTER_ORDER_QUANTITY : X

MASTER_ATPCAT : X

2c) cfg_headers (fields with values - others are initial) :

POSEX : 000001

CONFIG_ID : 000001

ROOT_ID : 000001

2d) cfg_instances (fields with values - others are initial) :

CONFIG_ID : 000001

INST_ID : 000001

OBJ_TYPE : MARA

CLASS_TYPE : 400

OBJ_KEY : FHVHTTA42400Z (configurable material)

2e) cfg_values (fields with values - others are initial) :

CONFIG_ID : 000001

INST_ID : 000001

CHARC : WIDTH

VALUE : 4

Hopefully this says a lot more than my description of the problem ?

Thanks in advance for any solution !!!

Greetz,

Kurt.

Re: BAPI_MOSRVAPS_SAVEMULTI3

Former Member — Fri, 25 Mar 2011 15:18:56 GMT

Hi Kurt,

One last chance I am taking Can you please check the below points..

1) Have you tried to change the CLASS_TYPE from 400 to 300 which is for configurable with the same Product.

2) To create an order using this BAPI ORDER_HEAD and ORDER_HEADX are sufficient tables...have you tried whether it is creating an order without any configuration data for this material or not? if it is creating then we will see to change the configurations later on...

3) Also please try to pass the MATERIAL ID(CHAR22 from MATKEY) in OBJ_KEY instead of Material Name or is it the material name which exists in /sapapo/matkey table? (check for any leading zeros...before FHVTT..)

because I am sure it is checking somewhere internally for PDS Config on basis of Material entered and throwing that error.

2d) cfg_instances (fields with values - others are initial) :

CONFIG_ID : 000001

INST_ID : 000001

OBJ_TYPE : MARA

*CLASS_TYPE : 400

OBJ_KEY : FHVHTTA42400Z (configurable material)*

This is first time I am seeing this problem.... thanks for this post..

Regards,

Saurabh

Re: BAPI_MOSRVAPS_SAVEMULTI3

kumaro412 — Fri, 25 Mar 2011 15:46:47 GMT

Thanks ...

I will look at this on Monday... I have to go now, so this will be the first thing to do next week ...

Have a nice weekend and thanks for your help this week !

Greetz,

Kurt.

Re: BAPI_MOSRVAPS_SAVEMULTI3

kumaro412 — Thu, 31 Mar 2011 13:08:46 GMT

Dear Saurabh,

I couldn't work on this earlier than today ...

But your second suggestion was a great help !

I only fill table ORDERHEAD and ORDERHEADX and there has been created a planned order, but I am not able to take a look at it ? In the mapping table I received a number in the field ORDID, but I don(t know how I can find the corresponding number of the planned order ?

Where can I find the link ? If I try to use table /SAPAPO/ORDKEY, I can' t enter the value of ORDID because it is too long ?

Thanks for the assistance !

Greetz,

Kurt.

Re: BAPI_MOSRVAPS_SAVEMULTI3

kumaro412 — Wed, 06 Apr 2011 14:49:50 GMT

Dear Saurabh,

We (an external consultant en I) found the solution of this problem ...

It is quite simple if you know what you have to do ...

Below are the values we pass to the function BAPI_MOSRVAPS_SAVEMULTI3 :

1) import parameters :

- LOGICAL_SYSTEM -> SCD800 (this is our APO-system)

- ORDER_TYPE -> 5 (this is for planned orders)

- EXT_NUMBER_ASSIGNMENT -> ' ' (this is also the default value)

- COMMIT_CONTROL -> E (this is also the default value)

- PLNG_VERSION -> 000

- STRATEGY_PROFILE -> ' ' (this is also the default value)

- NO_CREATE -> ' ' (this is also the default value)

- CHECK_SOURCE_EXISTENCE -> X (this is also the default value)

- PLANNING_MODE_USAGE -> 0 (this is also the default value)

- EVENT_CONTROL -> 1 (this is to say that we want to send the data from APO to R3)

2) export parameters (only those with entries) :

- ORDER_HEAD -> 1 Entry (see below)

- ORDER_HEAD_X -> 1 Entry (see below)

- CFG_REF_OBJECT -> 1 Entry (see below)

2a) order_head (fields with values - others are initial) :

ORDER_NUMBER : 1 (variable number - only relevant for mapping)

ORDER_START_DATE : 11.04.2011 00:00:00 (somewhere in the future)

ORDER_END_DATE : 12.04.2011 00:00:00 (somewhere in the future)

MASTER_PRODUCT : FHVHTTA99400Z (our configurable material)

MASTER_PLANT : BAWE

MASTER_SPEC_STOCK_IND : E

MASTER_SPEC_STOCK_KEY : 0050989466000020 (our reference sales order and -item)

MASTER_ORDER_QUANTITY : 1,000

MASTER_ATPCAT : AI

POSEX : 000001 (to know the link with table CFG_REF_OBJECT)

2b) order_head_x (fields with values - others are initial) :

ORDER_NUMBER : 1 (same as in table order_head)

ORDER_START_DATE : X

ORDER_END_DATE : X

MASTER_PRODUCT : X

MASTER_PLANT : X

MASTER_SPEC_STOCK_IND : X

MASTER_SPEC_STOCK_KEY : X

MASTER_ORDER_QUANTITY : X

MASTER_ATPCAT : X

2c) cfg_ref_object (fields with values - others are initial) :

POSEX : 000001 (same as in table order_head)

LOGSYSTEM : AWQ800 (our R3-system where the planned orders are created)

ORDER_TYPE : 3 (this is for sales orders)

ORDER_NUMBER : 0050989466

ITEM_NUMBER : 000020

2d) The other cfg_tables are not filled !!!

When I execute the function with all this values filled, we get a planned order as result ! And with configuration !!!

Thanks for all the assistance !!! Hopefully this information can be a great help for you too in the future !!!

Greetz,

Kurt.

Re: BAPI_MOSRVAPS_SAVEMULTI3

Former Member — Sat, 16 Apr 2011 05:52:16 GMT

Hi Kurt,

Thanks a lot for sharing the knowledge, definitely this will help me in future while working with this BAPI...

Thanks once again.

Regards,

Saurabh