Condition Idoc COND_A02

[Former Member]

Hi,

I am using BLAORD03 and COND_A02 IDOC to upload (INBOUND) the contract data as well condition data through custom program. But after posting both IDOC, the price given in condition record is not reflecting to the net price of line item screen of contract, while when I am changing the Condition price manually in transaction ME32K it is getting reflect to net price (NETPR) of line item of contract.

The condition is in validity period.

Could you please suggest the answer .........Urgent?

[Former Member]

Hi,

I am using BLAORD03 and COND_A02 IDOC to upload (INBOUND) the contract data as well condition data through custom program. But after posting both IDOC, the price given in condition record is not reflecting to the net price of line item screen of contract, while when I am changing the Condition price manually in transaction ME32K it is getting reflect to net price (NETPR) of line item of contract.

The condition is in validity period.

Could you please suggest the answer .........Urgent?

[christian_wohlfahrt]

Hi!

Do you book the IDOCs in the order of BLAORD03, COND_A02 (bad) or COND_A02, BLAORD03 (good)?

Regards,

Christian

[Former Member]

Hi Christian ,

I am booking both idocs in order of BLAORD03 then COND_A02.

As per your suggestion it is bad , so I need to use in order of COND_A02 then BLAORD03, but then what value should be placed for the contarct No ( VAKEY field of e1komg segment) as contract no is genetrating internally.

please suggest......

[christian_wohlfahrt]

I thought your process is first condition creation and then contract creation with price determination. In which way do you create a (correct) document manually?

I don't think it's possible to create a contract (with IDOC) and afterwards a document condition with a second IDOC. You just have to miss the document link, even when you have the contract number in the key fields.

Please describe how you create a contract manually -> in general in the same way you can create a contract via IDOC (but sometimes IDOCS don't support the same amount of functions as the corresponding transaction).

[Former Member]

Hi

In manual process we need to create contract first then condition document.

If we go for reverse order then we do not have any link field between contract and condition records, as contract number is going to be created internally.

again there is chance that one contract may have multiple picing conditions with different validity periods.

Please suggest any other solution ...urgent.

[christian_wohlfahrt]

OK, sorry - I thought the process is the other way around.

I have the feeling, the condition creation isn't correct. To check the correct filling of the IDOC, do the following steps:

- define an outbound cond_a02 message

- search a correct contract condition, display this in MEK3 (or VK13?). Take the condition info button right on the entry screen, select your example in the following screen, execute

- mark and send one (or more) line(s) with the text-button 'send conditions' (SHIFT+F'2)

- now you (should) have an IDOC with the correct field filling - compare this (in WE19) with your inbound IDOCs.

- you can also take the outbound IDOC and use this in WE19 for a new condition creation (exchange the contract or the material) - this should work for sure (otherwise SAP would not be able to receive it's own IDOCs in a remote system)

Some fields of the outbound IDOC are not necessary for condition creation - they would be filled automatically (e.g. based on customizing). Still adjust your condition IDOC as long as the condition is not created correct in the system.