on 04-04-2013 11:22 AM
Hi,
While we are doing the PGI in the system, our users maintain Actual GI date and expect the invoicing should happen on that night in the background job.
Suppose on
1) 1st April we have received the Order
2) 2nd April created delivery and by maintaining the Actual GI Date of 7th April - PGI button pressed.
3) User expects the the background job should pick the invoicing for this particular order only on 7th night.
but the system is picking all the PGI'd deliveries on the same night to create invoice whether they have maintained 7th or 2nd.
What we can do, so that the system should pick only on that particular day which is maintained in Actual GI Date
Looking for your suggestions.
Regards,
Venkat.
by maintaining the Actual GI Date of 7th April
Not sure to which industry, you are working but to my knowledge, system will not allow to do PGI at future date. Please let me know whether currently it is allowing in your case based on which suitable suggestion can be given.
G. Lakshmipathi
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Lakshmipathi,
Please find the screen shots here carried in test system.
Delivery
In delivery you can see the actual GI date is 19-04-2013 is maintained and able to do the PGI
and subsequently could also do the billing.
Billing
Why the system is allowing me to do the billing although it is not 19-04-2013 ?
The same problem is in background invoicing as well. As soon as the delivery is created with the posted dated GI, still the system is picking it for invoicing.
Regards,
Venkat.
FYI: I am working for the worlds largest food processing company in Switzerland.
Hi Venkat,
Personally, its a very good scenario. As far as I know, we can't do with standard SAP. We have to go for enhancement to check billing date and see if the billing date is future date then system should stop creating Invoice. May be I am missing some fundamentals here, let see what others say on this.
Regards, Sai Krishna.
Hi ,
i think you are confused with Billing date and Creation date
Billing date is something which will be determined from Actual GI date of delivery document and it can be future date as well
Creation date is the date on which the Billing document is generated
you can compare these two fields in VBRK
FKDAT for Billing date
ERDAT for Creation date
Billing date is further carried to Posting date in the accounting document
hope you are clear now
let me know if still have any question
regards,
santosh
Hi Santosh,
All my thoughts are on one thing.
How to achieve background billing for the deliveries which should be on actual GI date night.
Now I am very clear about creation date and posting dates.
for example, in a sales order suppose the schedule line is one perticular date, and if you want to create deliveries before to schedule line you will recieve an error.
I want something in the same way for billing as well.
However I repeat again, my background process should not pick the future dated GI's. and thats it.
Thanks Lakshmipathi,
In my system although the variant was created with VF04 for the programe SDBILLDL and made few changes as suggested and with the various testing and permitation and combinations, successfully achieved what users wanted. However Lakshmipathi's valuable input were immense to drive me in right direction.
Kind Regards,
Venkat.
Hi Venkat,
See if the below one helps you.
http://scn.sap.com/thread/1979442
http://scn.sap.com/thread/1456388
Regards, Sai Krishna.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Venkat,
In addition to above you may check below one as well.
"In order to have both Billing and Service render date as same, as far as i know, you don't have standard solution, but, you can try using USEREXIT_MOVE_FIELD_TO_VBAK".
or
User exit in program RV60AFZC.
FORM userexit_fill_vbrk_vbrp.
Let see what experts say on this.
Regards, Sai Krishna.
User | Count |
---|---|
100 | |
11 | |
11 | |
6 | |
6 | |
5 | |
4 | |
3 | |
3 | |
3 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.