cancel
Showing results for 
Search instead for 
Did you mean: 

Idocs not populating the fields

Former Member
0 Kudos

Hi

We are using Extended Classic Scenario. After the shopping cart is approved, the PO is generated in the backend R/3. The PO is generated in the backend and the idoc is triggered which is sent to supplier.

The problem we are facing is as below:

There are some fields in the idocs which are not getting populated. We are using badi implementation BBP_PO_INBOUND_BADI in the backend. We have used both the methods BBP_MAP_BEFORE_BAPI

BBP_MAP_AFTER_BAPI

The table EKPO is getting updated but the idoc does not have the fields.

Also when we are second time retriggering the output the idoc is having the required fields.

Kindly advice.

Thanks and Regards

Manoj

Accepted Solutions (0)

Answers (1)

Answers (1)

yann_bouillut
Active Contributor
0 Kudos

Hi Manoj,

Which fields are not populated ?

Kind regards,

Yann

Former Member
0 Kudos

Hi Yann,

The fields MFRPN(Manufacturer Part Number) and EMNFR(External Manufacturer Code Number). These fields are flowing correctly from SRM to R/3. Also the table EKPO is getting updated correctly with thiese fileds.

Thanks and Regards

Manoj

pvanhoove
Product and Topic Expert
Product and Topic Expert
0 Kudos

Hello Manoj,

How are you generating the idoc the first time ?

Rgds,

Pierre

Former Member
0 Kudos

Hi First time when the PO is generated in the backend, idoc is trigerred and sent to vendors through EDI.

Next time I am manually retrigerring the out message which is trigerring the idoc.

Our doubt is table EKPO is getting updated after the idoc is trigerred during first time. Since next time when retrigerring the idoc, values are already there in EKPO table hence they are getting populating in the idoc too.

Thanks and Regards

Manoj

pvanhoove
Product and Topic Expert
Product and Topic Expert
0 Kudos

Hello,

It looks the first generation occurs to early in the process.

Can you should check the processing time you defined in condition records ?

3 is too early, 4 should work because a commit work is done before. And at worst set it to 1 (selection report) and schedule a job to process the message.

Rgds,

Pierre

Former Member
0 Kudos

Hi,

We have not defined any processing time for our output time.

One more thing we have bot Classic Scenario and Extended Classic Scenario. It works correctly for the companies with Classic Scenario but with the companies with Extended Classic Scenario it does not work correctly.

Thanks and Regards

Manoj

Former Member
0 Kudos

Hi Manoj,

If in me23 you are getting all the populated fields from the Badi, then the Idoc also should have these.First of all check the Idoc Documentation in We60 and check for these fields over there along with their occurance.

Regards

Amitabh

yann_bouillut
Active Contributor
0 Kudos

Hi Manoj

With ECS, the PO is designed to be sent through SRM and not through ECC or R/3 where it is blocked in standard.

You have to change the behaviour.

Kind regards,

Yann