Billing Date picking future date

[Former Member]

Dear All,

We have a issue when the billing document is created it is picking one day ahead of the current date, ex. current dt is 11.10.2010 it is taking 12.10.2010 our client is using SAP system time as CET and OS level time is IST.

VTFL - Copy Control routine is - 011(Bill. date= Today) and pricing type is - C

Please suggest if you have encounter such issue.

Regards,

Ashish S.

[Former Member]

Dear All,

After applying note 1124661 the system reaction is corrected to use the user time zone instead of the system time zone.

All you need to do is Set in T.Code - SU01 user time zone to local time zone of user who is creating the billing document.

and then apply the Note - 1124661 which force the system to pick the all business transaction date/time of user and not of central system data/time.

Regards,

Ashish s.

[Former Member]

Hello Ashish,

The document creation date and time VBRK-ERDAT, VBRK-ERZET are always saved in system time to have a chronological order (e.g. to avoid that a document will get a number in a time, and later the subsequent number is

assigned in an earlier time, if users from different time zones working at the same document).

Regards,

Raghavendra

[Former Member]

Dear Experts,

I will answer for your quires one by one:

1. SO item level billing date is ok.

2. Actual PGI Date is ok system date but when we create billing doc it is picking future date.

In VTFL at item level we have Pricing Type - C does this anyways effect the billing date.

Plese suggest ..!

Regards,

Ashish s.

[Former Member]

Hi,

Pricing will be taken care through Copying control maintained at Item level for respective Delivery type & Billing Doc. Type where as Billing Date is determined at Header level.

Kindly check the actual PGI Date from the refrenced Outbound delivery?

Thank You,

RB.

[Former Member]

Hi,

Check your billing date inside your SO for each item to confirm whether billing date inside line item is align with the billing date of the header.

Thanks.