Application Development Discussions
Join the discussions or start your own on all things application development, including tools and APIs, programming models, and keeping your skills sharp.
cancel
Showing results for 
Search instead for 
Did you mean: 

Program RBDMANI2 giving error RV45A-VBAP_SELKZ(2) is not an input field

Bharath84
Participant
0 Kudos
338

Hi All,


We have an issue where our IDOC gets posted in the production system with status 51. We schedule a job twice a day in the background using program RBDMANI2 which is used to manually reprocess IDOCS in error. Every time the IDOCS with this error are still getting failed with the same error.

But, when the same error idocs are executed using BD87 in foreground or background, the idocs are successfully and the sales orders are created.

Please help me why this issue is happening and if there is any sap note for this error.


Thanks,

BK

1 ACCEPTED SOLUTION

DominikTylczyn
Active Contributor
0 Kudos
230

Hello vidya.p

See the note 166542 - EDI ORDCHG: Field RV45A-VBAP_SELKZ allows no entry

Best regards

Dominik Tylczynski

8 REPLIES 8

raymond_giuseppi
Active Contributor
0 Kudos
230

Did you already search OSS for available notes for your system version?

abo
Active Contributor
0 Kudos
230

to me, that smells of a batch input error, possibly some Z code not checking for background mode

DominikTylczyn
Active Contributor
0 Kudos
231

Hello vidya.p

See the note 166542 - EDI ORDCHG: Field RV45A-VBAP_SELKZ allows no entry

Best regards

Dominik Tylczynski

230

Good lord, I hope they aren't on that old of a version!

230

ryan.crosby2 That is the only relevant note I could find. If that is not the ancient version, then it must be some custom enhancement that screws up the batch input.

DominikTylczyn
Active Contributor
230

c5e08e0478aa4727abc4482f5be390b2 SAP standard processes sales order IDocs i.e. ORDERS and ORDCHG with batch input calls to VA01 and VA02 respectively.

Sandra_Rossi
Active Contributor
0 Kudos
230

It's not about the program RBDMANI2 which is used to reprocess the failed IDocs (several different programs and transaction codes do the same, e.g. BD87 as you said, and others), it's about the IDoc processing itself, so you'd better describe the IDoc itself and tell us what you tried.

Is it ORDCHG? Did you check the SAP notes? The other same questions and answers? What SAP software version do you use?

Bharath84
Participant
0 Kudos
230

hi Sandra,

The message type is ORDERS05.

We tried deciding RDBMANI2 and we found that in the Sales orders VA02 screen, by default 6 line items are visible and in our IDOC there area more than 6 line items. When we are scrolling down at line item level at that warning message is coming and the same is coming as error in IDOC.


Thanks,

Bharath