Call transaction returning 1001 message

Former Member · ‎07-04-2005

Dear Abapers,

I am updating batch information (not at the item level but at component level) in PO through ME22.

CALL TRANSACTION 'ME22' USING BDCDATA

MODE 'N'

UPDATE 'S'

MESSAGES INTO GT_ME22_MESSTAB.

When i execute in all screen mode it is updating the batch information in item components (Subrc is 0). But when i execute in No screen mode program is not updating the information and subrc value is 1001.

In the help it says : for mode N

Processing without display of screens. If a breakpoint is reached in one of the called transactions, processing is terminated with sy-subrc same as 1001. The field sy-msgty contains "S", sy-msgid contains "00", sy-msgno contains "344", sy-msgv1 contains "SAPMSSY3", and sy-msgv2 contains "0131".

There are no break points set any where....

Thanks in advance.

Sanjay.

andreas_mann3 · ‎07-04-2005

Hi,

you can view the content of your message 00(class)

- no. 344

with TA SE91:

No batch input data for screen SAPMSSY3 0131

regards Andreas

RichHeilman · ‎07-04-2005

What this means is that the system is throwing a screen which is not being handled by the BDC. In this case, screen 0131 of program SAPMSSYS3. You need to find out what screen this is, why it is coming, and handle it correctly in your BDC code.

Regards,

Rich Heilman

Former Member · ‎08-10-2005

Sanjay

Any updates on this problem?

I'm struggling with the exact same problem.

But I'm trying to call the 'VL02N' transaction, also with 'N' and 'S'. I get the same return table as you do.

christian_wohlfahrt · ‎08-10-2005

Hi Tim,

enjoy-transactions (modern style, ending with 'N') aren't batch enabled.

Try instead BAPI_OUTB_DELIVERY_CHANGE.

Regards,

Christian

Former Member · ‎08-10-2005

Christian

Thanks for replying so quickly.

Is it possible we don't have this BAPI yet?

We're using 4.6C, but we don't use support packages 😕

Former Member · ‎08-10-2005

before you do the 'CALL TRANSACTION' make sur you have not break-point. Just delete all your break-points.

the screen your talking about it's seems to be the debugger. make sur their is not <b>BREAK-POINT</b> statement too (maybe in user-exits).

joseph

Former Member · ‎08-10-2005

Hi,

Program name : SAPMSSY3 & screen # : 0131 are for Debug mode screen. So there are some break points in your program. So control is stopping at the break point in the No Screens mode and throwing the error message. Remove all the break points and execute it again.

Best Regards,

Vijay

Former Member · ‎08-10-2005

Well this is just as Sanjay's already stated:

>In the help it says : for mode N

>Processing without display of screens. If a breakpoint >is reached in one of the called transactions, processing >is terminated with sy-subrc same as 1001. The field sy->msgty contains "S", sy-msgid contains "00", sy-msgno >contains "344", sy-msgv1 contains "SAPMSSY3", and sy->msgv2 contains "0131".

There aren't any break-points in the code, no manual ones and no red stop icons either.

What I don't know is why I'm getting this reference to the debug-screen.

I'm willing to use the BAPI instead, but I can't find it using SE37

Edit:

I found out the suggested BAPI isn't in our system.

According to this thread I've got some functions to work with:

Message was edited by: Tim Schraepen

Former Member · ‎08-10-2005

screen SAPMSSY3 0131 is the screen of the debbug editor (goto se51 and see the screen).

Why don't you run the <b>call transaction in mode 'A'</b> (display) and you will see where you put the break-point statement.

try bapi BAPI_PO_CREATE1

christian_wohlfahrt · ‎08-10-2005

Hi Tim,

you triggered two additional comments to the original post

But yes, this BAPI was released in 620, sorry (time for upgrade?).

Two other alternatives:

- take an IDOC (e.g. DELVRY01? I hope, they are not just creating docs)

- use an 'old style' transaction (VL02) - but be careful, some functionality is different, e.g. order of determinations.

Regards,

Christian

Former Member · ‎08-10-2005

Thanks again for replying Christian.

I thought about using the 'old style', but when I suggested it, they told me this transaction has been locked, and it's locked for a reason.

Using an iDoc is probably another solution, but I think it would take too long to adapt all our programming (ABAP and Java) to using the iDoc solution, then to just use the Function Module WS_DELIVERY_UPDATE and adapting our programming (ABAP only) to this solution.

Time for upgrade: in my opinion definitely, too bad I'm probably the only one that has that opinion at our company 😕