Re: [sap-log-sd] Back update of document status
Posted by
Admin at
|
Share this post:
|
0 Comments
| | Posted by hovering_yogi (SAP SD Consultant, Sony) on Apr 26 at 10:25 AM | |
No worries Jay,
There doesn't seem to be any user-exits available from that form or the
calling program in 4.6 - however I wouldn't be sure how to trigger the
update of all the documents even if we had some stuff in an exit at that
point.
I think it might be useful to see whats going on in there though when
contemplating what the custom report will need to do so thanks anyway for
passing on the details.
Steve.
On 26 April 2010 15:07, Jason Barton via sap-log-sd <
sap-log-sd@groups.ittoolbox.com> wrote:
>
> Posted by Jason Barton (Billing
> Functional Consultant - Team Lead)
> on Apr 26 at 10:09 AM
> I see reference to 'V4.6' now at the bottom of your note, so I think my
> suggestion might be worthless. Sorry, I missed the reference the first time
> I read the note.
>
> Regards,
>
> Jay
>
> ---------------Original Message---------------
> From: hovering_yogi
> Sent: Thursday, April 22, 2010 11:23 AM
> Subject: Back update of document status
>
> > A quotation document has been identified as having incorrect copy control
> such that orders created with reference from it do not adjust the referenced
> qty and therefore the quotation never shows as complete.
> >
> > The config has been corrected but there are a very large number of
> documents that have effectively been fully referenced but still show as
> open.
> >
> > In development I created a similar example and then tried SDVBUK00 but
> this didn't correct the status so I guess doesn't look at correcting the
> referenced qty amounts and therefore the overall document status.
> >
> > Anyone know of a standard report or do we need to look at (an admittedly
> not too complicated) correction program?
> >
> > V4.6c
__.____._ There doesn't seem to be any user-exits available from that form or the
calling program in 4.6 - however I wouldn't be sure how to trigger the
update of all the documents even if we had some stuff in an exit at that
point.
I think it might be useful to see whats going on in there though when
contemplating what the custom report will need to do so thanks anyway for
passing on the details.
Steve.
On 26 April 2010 15:07, Jason Barton via sap-log-sd <
sap-log-sd@groups.ittoolbox.com> wrote:
>
> Posted by Jason Barton (Billing
> Functional Consultant - Team Lead)
> on Apr 26 at 10:09 AM
> I see reference to 'V4.6' now at the bottom of your note, so I think my
> suggestion might be worthless. Sorry, I missed the reference the first time
> I read the note.
>
> Regards,
>
> Jay
>
> ---------------Original Message---------------
> From: hovering_yogi
> Sent: Thursday, April 22, 2010 11:23 AM
> Subject: Back update of document status
>
> > A quotation document has been identified as having incorrect copy control
> such that orders created with reference from it do not adjust the referenced
> qty and therefore the quotation never shows as complete.
> >
> > The config has been corrected but there are a very large number of
> documents that have effectively been fully referenced but still show as
> open.
> >
> > In development I created a similar example and then tried SDVBUK00 but
> this didn't correct the status so I guess doesn't look at correcting the
> referenced qty amounts and therefore the overall document status.
> >
> > Anyone know of a standard report or do we need to look at (an admittedly
> not too complicated) correction program?
> >
> > V4.6c
Copyright © 2010 Toolbox.com and message author.
Toolbox.com 4343 N. Scottsdale Road Suite 280, Scottsdale, AZ 85251
Toolbox.com 4343 N. Scottsdale Road Suite 280, Scottsdale, AZ 85251
SAP Logistics Sales and Distribution Enthusiast
Contributed 100 posts in a group to earn a Bronze Achievement
In the Spotlight
Your SAP Security is at Risk...Learn How to Stay Protected. Read the free white paper from SenSage
View this thread online
Manage group e-mails
Create an FAQ on this topic
Tell us what you think
Unsubscribe from discussion
Manage group e-mails
Create an FAQ on this topic
Tell us what you think
Unsubscribe from discussion