on 04-02-2015 4:58 PM
After completing a few SPM installations and projects there are some standard extractor updates that should be made available to the SPM community (These changes should be made after creating a copy of the standard SPM extractors):
Standard Price Extractor:
The field XSASTPRTC should be updated in the special coding area to divide by the price unit by default. This will ensure all of the PPV calculations are compared against the proper base unit amount.
Add the following code to the special coding area
Result = WA_MBEW-STPRS / WA_MBEW-PEINH.
Contract:
The field XSACONST (Contract line Value) should be updated from EKPO-BRTWR (Gross Value) to EKPO-ZWERT(OA Target Value).
This will ensure the correct contract line value is passed to the Minimum Contract Amount field in SPM regardless of contracts with materials vs contracts without materials. Scheduling Agreements require a material number and can be left unchanged (EKPO-BRTWR).
IVBSIK(Non Cleared Invoices) and IVBSAK (Cleared Invoices):
There are a number of changes in this area, please evaluate them based on your customer requirements
Update Exchange Rate Translation Date:
XSATRANDAT - From BKPF-BUDAT(Posting Date) to BKPF-WWERT (Exchange Rate Translation Date)
Generally the posting date and the translation date are the same, but there are occasions where it can be different.
Update the Quantity and Unit of Measure from the base unit to the transactional unit:
XSAINVQT - From BSEG-MENGE(Base Unit Quantity) to BSEG-ERFMG(Quantity in Unit of Entry/Transactional Quantity)
XSAINVPT - From BSEG-MEINS(Base Unit of Measure) to BSEG-ERFME(Unit of Measure in Unit of Entry/Transactional Unit of Measure)
XSATUNIT - From BSEG-MEINS(Base Unit of Measure) to BSEG-ERFME(Unit of Measure in Unit of Entry/Transactional Unit of Measure)
Depending on your system and requirements BSEG-BPMNG and BSEG-BPRME can be used instead
Payment:
In the standard installation the you may be missing the key field ASAPYMTID. Add it to the extractor with the following source field BSAK-BUZEI.
Also ensure that the payment datasource object is added to the OPMDM_Types and OPMDM_TypesT tables in BI/BW:
Upload_Type: Payment
Target_Type: DSO
Target_Name: 0ASA_17
Upload_Group: Tran
Chain_ID: 0ASA_P04
IS_SYS_Dependent: X
Application: XSA
Datasources ECC and BW:
Ensure the ECC Datasource changes/updates are moved first and validated in RSA2 before moving the BW Datasource changes.
Future SPM updates requested:
Correct Calculation (non blended Invoice Unit Price amount)
INV PO qty IPV unit IPV% Ipv amount
2 2 10 0 0 0
4 4 21 0 0 0
3 3 3 0 0 0
5 5 2 0 0 0
6 6 7 0 0 0
Current Calculation (blended Invoice Unit Price)
INV PO qty IPV unit IPV% Ipv amount
4 2 10 2 100 20
4 4 21 0 0 0
4 3 3 1 33.33333333 3
4 5 2 -1 -20 -2
4 6 7 -2 -33.33333333 -14
Hi Otulaja,
Thank you for this contribution!
To have your “Future SPM updates requested” considered please place them
in the Idea Place. Instructions are here:
http://service.sap.com/~form/handler?_APP=01100107900000000342&_EVENT=REDIR&_NNUM=1515837 -
How To: Enhancement Request Process - "Idea Place"
Kind Regards,
John Harris
Senior Support Engineer
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
User | Count |
---|---|
6 | |
5 | |
2 | |
1 | |
1 | |
1 | |
1 | |
1 | |
1 | |
1 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.