Scribd
Upload
65 views4 pages

SAP Automatic Price Update For Service Contract&Service Plans

1) A nightly job will retrieve condition records from the VR-APP pricing procedure where the valid to date is equal to the job run date. The valid to date is automatically updated to be one day before the new valid from date when a condition record is changed. 2) Customer numbers corresponding to the retrieved condition records will be collected in an internal table. 3) The corresponding service contracts and plans for those customers will then be collected by passing the customer numbers to the VBAK table.

Uploaded by

umesh.soni
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
65 views4 pages

SAP Automatic Price Update For Service Contract&Service Plans

1) A nightly job will retrieve condition records from the VR-APP pricing procedure where the valid to date is equal to the job run date. The valid to date is automatically updated to be one day before the new valid from date when a condition record is changed. 2) Customer numbers corresponding to the retrieved condition records will be collected in an internal table. 3) The corresponding service contracts and plans for those customers will then be collected by passing the customer numbers to the VBAK table.

Uploaded by

umesh.soni
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
You are on page 1/ 4

1)Every midnight a job will trigger a program to find the list of condition records with valid

to date" is equal to job run date/system date for list of condition types in VR-APP
pricing procedure.

Please notice the valid to date as soon as condition record value is changed with
future validity start date or even if it is changed on same date the system automatically
updates the old (valid to date field= new valid from date-1).

2) For list of condition records with "valid to date" = job run or system date,
corresponding customer numbers will be collected into internal table. (Job run date will
be passed to valid to date in condition table as below:

The below was run on 23rd March

The below was run on 24rd March

3) For list of Customer numbers corresponding Service contracts and Service plans will
be collected into internal table by passing customer number into VBAK.

4) The list of service contracts and service plans received will be passed to VBKD table
with pricing date same as job run date.

5) Another alternative is if the sold to party and ship to party is always same for service
contract and service plans then data can be passed in VBKD for field ZZKUNWE as
below:

5) The Pricing date will be changed for above service contracts and service plan with +1
date or for the above found service contract and service plans.

You might also like