Post goods issue VL02N

[pedro_nunes6]

Hello all,

I have a situation that i dont understand.

Imagine that i have an outbound delivery with an item wich material should contain serials. This delivery is to be transferred to another center.

If i make the PGI - post goods issue - using the normal way, transaction VL02N, it will generate a material document with the serials inside the document. that's right and what we want.

But, if i code a BDC or create an LSMW the serials did not appear in the material document.

Did someone face the same issue?

Kind regards,

Pedro Nunes.

[Former Member]

Hi Pedro,

A BDC session will get executed as a background task which is asynchronous in nature (a separate task).

I suspect a possibility of not having a serial by the time a material document is created whereas when the transaction is executed in foreground, the work process will perform the update in the same task(current task).

I am not sure about LSMW.

Thanks

Mohit

[pedro_nunes6]

Hi Mohit,

I understand your explanation about the BDC, but i already tried the following BAPI BAPI_OUTB_DELIVERY_CONFIRM_DEC just to test the PGI and the serials are not carried to the material document.

The functional team already told me that the LSMW has the same issue as well as VL06F.

I found the following function WS_DELIVERY_UPDATE but in some posts says not to use...

I think that this could be a bug...

Is there another BAPI for PGI?

[former_member215542]

BAPI_OUTB_DELIVERY_CONFIRM_DEC could be used for decentralized system. I am not sure about this, but it seems that the serialization does not work when you confirm from a decentralized system

Perhaps, you might want to check this

http://help.sap.com/saphelp_470/helpdata/en/34/a9eb3c1875bd48e10000000a114084/content.htm

So what I would suggest is to check with some functional consultant if SAP can generate the serial number by tweaking some settings.

Another option would be to get the serial number generated, using some BAPI / RFC like DPWTY_SERIAL_NUMBER_EQUI_GET/ BAPI_EQMT_DETAIL, for the line items and then populate them in parameter ITEM_SERIAL_NO of BAPI BAPI_INB_DELIVERY_CONFIRM_DEC

[pedro_nunes6]

i already tried that....

Could it be a configuration?

[former_member215542]

Hey Pedro,

Well, it is a bit difficult to tell from the information that you have provided since it is not clear whether yours is a Decentralised WMS scenario or not.

If yours is not a decentralized scenario and you just want to perform a goods issue for an OBD, you could try running VL21 in background which would perform the GI and you can then read the serial numbers and transfer it.

If the storage location is decentralized, then you could refer to the last section on the link that I provided earlier, "No Serial Number Management in the Decentralized WMS". This part is a bit tricky and you might need help from functional consultants to check if something can be done via configuration. Ideally, in decentralized scenario, the serial numbers are sent by the warehouse to ECC

Regards,

Pulkit

[pedro_nunes6]

Sorry Pulkit,

My scenario is not a decentralized.

The scenario is a simple outbound delivery and when i do PGI from VL02N the serials are carried to the document. I went to MIGO and confirmed that.

If i code a batch input for VL02N the behavior is different. I went to MIGO with the material document and the serial number is not there.

My client wants to automat the process, so in my program i write a BDC but is not working and i dont know if it is a program error or a configuration situation...

[former_member215542]

Did you try performing the GI via transaction VL21/ VL23? How does that behave?

[pedro_nunes6]

Hello Pulkit,

I tried via VL21 and has the same issue.

Via VL23 it works.

[former_member215542]

So you could automate the GI process via VL23. Is there any other issue?

regards,

Pulkit

[pedro_nunes6]

For our process this is not a good idea because i need to throw a popup message to user confirming that PGI was ok or not and fill custom tables with the result.

As the result will appear on the list of a background job it is not a good way to solve the issue.

[former_member215542]

Try FM WS_LM_GOODS_MOVEMENT in that case

[pedro_nunes6]

That FM did not work...

[former_member215542]

If VL23 works fine, the FM call should work as well. I would recommend you to perform more debugging and see what you are missing from the standard approach.

Unless there are some enhancements based on some specific t-codes that you might have put in

[pedro_nunes6]

I don't know if there is an enhancement based on tcode because i'm not the only developer. I already asked the functional team about that but they also don't know.

At all this time i was testing on quality system where the issue was detected. But the functional guys said to me that on development system it is ok. We can post goods issue and the serial are being transported to the material document.

This seems very strange. We already added a note on OSS, but no response.

I have implemented a temporary solution that is an online call transaction to VL02N and the user will press the button to post goods issue.

I really appreciate all yours efforts helping me.

[pedro_nunes6]

Hello,

I had another information about this issue.

It only happens after a system copy from production to quality and happens on quality system. The other two systems, development and production does not have this problem.

Anyone knows what could be the problem?

[Former Member]

Hi,

I would suggest try with the FM: this function module will work delivery update as well as serial number update( Batch split ).

Look at the code inside FM under the include:  FV50XF0B_BELEG_SICHERN

perform serialnumber_automatically.

perform serialnumber_update.

I would suggest check the FM, it will work in your instance!