Call Transaction using VL01N

[Former Member]

Hi,

I am doing a call transaction using VL01N and getting a subrc of 1001. When I tried creating delivery manually I was able to create it successfully. Also once I created the delivery and again ran the BDC it is not giving errors still giving success with subrc of 1001. Can anyone help me on this its really urgent and not able to figure out whats going wrong?

Thanks,

David.

[Former Member]

The following is my call in the program

CALL TRANSACTION 'VL01N' USING i_bdcdata

MODE 'N' UPDATE 'S' MESSAGES INTO i_messtab.

[Former Member]

Hi David,

Check these links,

Ali

[former_member194669]

Hi,

Use any one of the below after call transaction

1.  WAIT UP TO 3 Seconds.

aRs

[Former Member]

I don't have any commit work

[former_member194669]

Hi,

or use any one of the below after call transaction

2. call function 'ENQUE_SLEEP'

exporting

seconds = 3.

3. CALL FUNCTION 'FMCT_WAIT_FOR_UPDATE'

EXPORTING

I_SEC = 3.

aRs

[Former Member]

thanks ARS let me try this and I will let you know if it helps.

[Former Member]

Hello David,

Do not use VL01N Transaction ,it is enjoy transaction

You can use VL01 Transaction instead of VL01N Transaction

Call transaction 'VL01' using bdcdata

mode 'N'

update 'S' " This will work like commit work

messages into bdcmsgcoll.

Otherway use RV_DELIVERY_CREATE or GN_DELIVERY_CREATE Function module.

Thanks

Seshu

[former_member194669]

David,

Seshu is right, I have not noticed the transaction type VL01N please use VL01 instead.

aRs

[Former Member]

Hi Seshu,

I have been asked to use VL01N and not VL01 as it is outdated. And the technical requirements says to do BDC, any ideas to get this working?

Thanks,

David

[Former Member]

I know VL01 is outdated ,if you use VL01N ,definitly you get sy-subrc is 1001.

I hate BDC Program but sometimes it is required since some of them does not have FM or BAPI.

but in your case you have FM ,you can use FM or BDC for VL01 ..

VL01 is outdated but still you can use ,there is no harm if you use VL01 .

if VL01N works in Dev ,if you move production defintelty somewhere you get problem.

Try to convience your client otherwise you will be in trouble

Good luck

Thanks

Seshu

[Former Member]

Hi Seshu,

Can you tell me the advantage of using VL01N over VL01? Are they both same or there is an added advantage with VL01N.

Thanks,

David.

[Former Member]

David,

Both are same except GUI ,both are having same functionality...

VL01N is Enjoy Transaction ( GUI )

VL01 is not an enjoy transaction..

You can achieve same functionality if you use VL01 ...

Just record using SHDB and see the results,if you need any help about recording or even if you need Function module coding just let me know.

I am sure that you will not get any issues if you use VL01 BDC..

Thanks

Seshu

[former_member194669]

Hi,

Please find related SAP Note 491875.

Symptom

For Release 4.6A, new, more user-friendly transactions have been made provided for delivery processing:

• Transactions VL01N, VL01NO, VL02N and VL03N for processing outbound deliveries,

• Transactions VL31N, VL32N and VL33N for processing inbound deliveries.

In the release notes for Release 4.6A, SAP informed you that the previous transactions for delivery processing are only provided in Release 4.6 and that you must adapt your processes to the new transactions when you upgrade to a higher release.

Other terms

SAPMV50A, upgrade, batch input, texts

Reason and Prerequisites

This problem is caused by an error in the documentation.

Solution

This information is incorrect. SAP has corrected the release notes correspondingly.

Due to the use of controls, you cannot execute the new delivery transactions for batch input without restrictions (see Note 457925). Since a BAPI for processing deliveries that fully includes the features of a batch input is currently not yet available, you can also use the previous Delivery Transactions VL01, VL02, VL03, VL31, VL32 and VL33 in releases higher than Release 4.6 and they are fully maintained.

Note that the earlier delivery transaction features were frozen at Release 4.6 level and that new functions are only provided in the new dialog transactions.

<b>and check note 504936</b>

With release 4.6B, SAP has delivered new enjoy transactions. Examples

are transactions MIGO, MEPO, VL01N, VL02N. These transactions are not

supported for batch input processing. For details please read notes

304122,381630 457925 and 491875.

May this will help you

aRs

[Former Member]

hi seshu..

i have to do bdc for vl01n... my doubt is how can we pass the storage locations one by one.. means if in the 1ts storage location, stock is not available fully than i should pass second storage location and so on ..

or how can it will select next storage location automatically with pick quantity..

this is requirement i hope u understood.. kindly send me

thanks