Picking request date format populated wrongly

[Former Member]

Hi All,

In the Outbound Delivery document flow, date on a Picking request is showing in wrong format. Please find the example below.

Instead of showing the date as 07/28/2014. System showing the date as 20/14/2807.

Kindly suggest me on this issue.

This issue mainly for STO orders.

For example, in a Purchase order, we have 1 line and created multiple deliveries. But this issue occurs only on some Outbound Deliveries.

Please help.

Regards,

Raja Durai

[former_member223981 · Accepted solution]

Hi Raja,

Is the system date correct on your system? I checked this on my internal system and the picking request gets filled here:

SAPFV50P / FORM PICKMENGE_BEARBEITEN

****************************************************

vbfa-mandt = likp-mandt.

vbfa-vbelv = likp-vbeln.

vbfa-posnv = lips-posnr.

vbfa-vbeln = sy-datum.   <<<<<<<<<<<<<<<<<<<<<<<<<

vbfa-posnn = sy-uzeit.

vbfa-vbtyp_v = likp-vbtyp.

****************************************************

Here, the system date (SY-DATUM) is being passed to the document flow (VBFA).

[Former Member · Accepted solution]

Hi Connolly,

Thanks for the reply.

There is no issue in the System date.

Inside the Delivery, picking date displayed correctly.

In LIKP, picking date format is correct.

But only in the document flow, it is in wrong format.

So obviously in VBFA also, it is wrong.

Regards,

Raja Durai

[Former Member · Accepted solution]

Hi All,

Any suggestions on this issue?

Regards,

Raja Durai

[former_member223981 · Accepted solution]

Is this happening every time? Or has it just happened sporadically?

If it happens every time, set a breakpoint at the code above, check what is being passed to VBFA. If it is the correct format at this point, set a watchpoint on VBFA-VBELN and check where it changes.

[Former Member · Accepted solution]

Thanks for your suggestion Noel.

But it happens rarely.

We are trying to find out the issue through debugging only.

Will update if we found the cause.

Regards,

Raja Durai

[former_member223981 · Accepted solution]

Go to include MV50AFZ1, do a find on VBFA and check if any of your custom code is changing this value. I cannot envisage that standard code would be causing this as it would be a bug that would be caught straight away.