Usin bapi BAPI_PRODORDCONF_CREATE_HDR material document number going to changed for each material and item is same for each material

[former_member477623]

HI,

   Please help. I am using bapi  BAPI_PRODORDCONF_CREATE_HDR  but facing some problem.

When confirm production order using transaction CO15, Its successfully confirmed. And when checking material document number in Transaction CO02 each material has one MATERIAL DOCUMENT NUMBER and ITEM is very to each material.

  Confirmation of production order in transaction CO15

Checking in transaction CO02 (path: Goto-Documented Goods Movements)

But when confirm from using BAPI (BAPI_PRODORDCONF_CREATE_HDR), Its successfully confirmed but material document number going to changed and item number is same for each material.

Checking in transaction CO02 (path: Goto-Documented Goods Movements)

Passing parameter value to the BAPI

Importing : post_wrong_entries  =  2

Table:

Athdrlevels: ordered = order no

            Yield = production qty

            pers_no = employee id

            postg_date = current date

            ex_created_by = user name

goodsmovements: material = material no

                                      plant = plant

                stge_loc = storage location

[dimasluis_defaria]

Hi,

Check:

• LinkConfGoodsmov The goods movements are linked to a confirmation via the LinkConfGoodsmov table. There must be an entry in this table for every entry in the Goodsmovements table. The index in the LinkConfGoodsmov-Index_Confirm field refers to the lines in the corresponding confirmation in the AtHdrLevels table and the index in the LinkConfGoodsmov-Index_Goodsmov field refers the corresponding good movement in the Goodsmovements table.

  If you want to prevent a goods movement being posted during a confirmation according to the standard logic, make an entry in the LinkConfGoodsmov table as well as in the AtHdrLevels table. The index in the LinkConfGoodsmov-Index_Confirm field refers to the lines of the corresponding confirmation in the AtHdrLevels table. Enter the initial value 0 in the LinkConfGoodsmov-Index_Goodsmov field. It is not necessary to make an entry in the Goodsmovements table, in this case.

  If no entry exists in the LinkConfGoodsmov table for a confirmation, goods movements are determined using the standard logic for backflushing and automatic goods receipt for confirmations.

Dimas Faria

[Caetano]

Hello

When posting a confirmation using a BAPI, the goods movements are always posted in the update process (background). In this case, system always use a different material document for goods receipts and goods issues. Please take a look on question 4 of the FAQ note 1586230:

Question: Is it possible to have the goods movements 101 and 261 in a material document when posting using a BAPI?

Answer: No, this is not possible in the BAPI. For technical reasons, goods receipts and goods issues must be transferred in separate packages of inventory management during the posting in a BAPI. This leads to the different material documents.

See also question 11 of the FAQ note 540392.

BR
Caetano

[former_member477623]

Hi Ceatano

  I  confirm production order through bapi   BAPI_PRODORDCONF_CREATE_HDR but but i am not getting expected result.please help me how i call the BAPI. I have to develop a APP for  production order confirmation.

Regards,

Suman

[Caetano]

Hello

If I understood the description of the issue correctly, you are observing exactly what is described on the note on your system: there are different material documents for the goods receipt and for the goods issue. This is according to the system standard design and it cannot be changed.

Best regards
Caetano Almeida

[former_member477623]

Hi Ceatano,

I want to confirm production order by using BAPI. Please help me which BAPI i have to use and what are the needed fields .I am totally new in pp module please help me.

Regards,

Suman