Movt 647 - Stock transport order serialized in 1 step

[Former Member]

Hi,

Is there a workaround on using serial number management for movement 647?

Our issue is when we have STO (charge to Cost Center) and we have used movement type 647 in SD delivery. We also have a process where we can use a material with serial number profile and during delivery (VL02N) / post goods issuance, a serial number is required based on delivery quantity. Unfortunately we are encountering this error message "Movement type 647 does not currently support serial number management".

I have found OSS Note 213861 - Stock transport order serialized in 1 step for this, but I would like to know if you have other workaround.

Thanks,

Ria

[former_member234835 · Accepted solution]

This message was moderated.

[former_member234835 · Accepted solution]

This message was moderated.

[rafael_zaragatzky]

Hi Ria,

We always faced the same issue and went for a two-step STO with a follow-on autom. transaction after PGI. The transaction was called by the output processing of the outbound delivery (medium 8, special processing). The called program had of course to wait a bit to let the PGI be stored in the database.

BR

Raf

[JL23]

Beside of customizing there is quite a lot hard coded in the program that posts movements.

If there is an error message that this scenario is not supported and the same is said in a SAP Note, then you just have to go with the alternative of the one-step transfer that was given as work around.

Movement types cannot be created from scratch, they can only be copied, hence the general functionality cannot be influenced by you. You can only influence what SAP designed for this.

If it was so easy by just using a different movement type name then SAP had certainly mentioned it or even given you a different movement type for this.

[Former Member]

Hi Jurgen,

I see your point, creating a new movement type doesn't solve my issue for 647 if I will just copy it exactly from 647. We don't have this issue in 641 (for direct charge), but we cant reuse the same movement 641 type since our process wants to segregate direct charge from cost center charge (with automatic goods receipt), thus we have used 647.

We dont have issue on using 647 for non-serialized materials as well, thus our issue is not something incorrect for the entire process.

Anyway, I'll check on this on business process prospective.

Thanks,

Ria

[ankurch]

Hi Ria,

Try to create new movement type by copying the existing 647 & 648 Movement & replaced with Z## through the transaction code "OMJJ".

In field selection add the serial number field and try to post your transactions!!