VA01 Create Sales Order error message

pts.
Tags:
Basis
Development
SAP
A customer is sending ORDERS IDocs via RFC and they are failing with "Field VBKD-INCO2 is not an input field", message 00 347 error status 51. When I reprocess the IDoc using WE19 or BD87, there is no problem. I suspect something is happening because of the RFC, logical system, method. The SAP diagnosis is "A transaction is processed using batch input." Procedure is "Correct the batch input data. According to the processing scenario, this may concern the following objects: Batch input session, CATT procedure, or application program." I realize this is a limited explanation, but has anyone encountered this while using RFC IDocs? Dave Gustafson

Answer Wiki

Thanks. We'll let you know when a new response is added.

When unwanted screens are called, the easiest way is to change the online behaviour is in the call transaction sentence.

Example:
data opt1 type CTU_PARAMS.
opt1-disMODE = MODE.
opt1-UPDmode = UPDATE.
opt1-nobinpt = ‘X’. ” online mode

CALL TRANSACTION ‘XXXX’ USING BDCDATA
options from opt1
MESSAGES INTO MESSTAB.

Then, you do not have to change the screen sequence.

Discuss This Question: 1  Reply

 
There was an error processing your information. Please try again later.
Thanks. We'll let you know when a new response is added.
Send me notifications when members answer or reply to this question.

REGISTER or login:

Forgot Password?
By submitting you agree to receive email from TechTarget and its partners. If you reside outside of the United States, you consent to having your personal data transferred to and processed in the United States. Privacy
  • Cfilandro
    Simply put, your problem is that the VBKD-INCO2 field is gray when your transaction is trying to update it. Think of it as a VA03---the fields are all gray....if you tried to change fields using a call transaction VA03 it won't work. You need to figure out why that field is gray during your background process. Make sure you execute in background for your WE19. If you are running the same transaction in the WE19 as the RFC, then you should get the same results. Make sure your partner profile is pointing both tests to the same function module. Also, there could be userexit code in the transaction which is causing this behavior, so check out the ABAP.
    180 pointsBadges:
    report

Forgot Password

No problem! Submit your e-mail address below. We'll send you an e-mail containing your password.

Your password has been sent to:

To follow this tag...

There was an error processing your information. Please try again later.

REGISTER or login:

Forgot Password?
By submitting you agree to receive email from TechTarget and its partners. If you reside outside of the United States, you consent to having your personal data transferred to and processed in the United States. Privacy

Thanks! We'll email you when relevant content is added and updated.

Following