SAP SD – FAQ Notes
The SAP OSS FAQ notes are full of information, they are recommended reading, login to OSS on the left (under links) and search for these:
Number Range Buffering
Basic Introduction to NRIV
The document number is assigned in chronologically ascending order based on the table NRIV. For this, the table NRIV is locked until the application (LUW) is terminated by either a COMMIT WORK or ROLLBACK (OSS Note 639754). Another application cannot take a document number during this time. Read more 
Change a customer account group
What happens to the customer number when I change an customer account group? Read more
ATP – Storage Location Check
Can I deactivate the storage location check for checking rule ‘A’ (sales order) but leave checking rule ‘B’ (delivery) activated when I customize the scope of check, so that sales orders are not checked at storage location level? Read more
Where does the system determine the Accounting Doc Type?
The Accounting document type is determined in various ways, according to type of transaction, for example the default can be configured in SAP Customizing Implementation Guide–>Financial Accounting–>Accounts Receivable and Accounts Payable–>Business Transactions–>Outgoing Invoices/Credit Memos–>Carry Out and Check Document Settings–>Define Default Values
However in the case where you have a sales billing document and you would like to default a specific accounting document type you should Read more
Function Modules for SD Reports and Smartforms
These function modules are great to get the information used to populate Smartforms and reports in SD.
Remember you can access the data with transaction SE37 and use the test/execute icon [F8].
IDoc numbers related to Sales Documents
Purchase Order Transactions
MASS MAINTENANCE
- MEMASSPO : Mass maintenance of POs
- MEMASSRQ : Mass maintenance of PRs
- MEMASSCONTRACT : Mass Maintenance of Contracts
- MEMASSSA : Mass Maintenance of Scheduling Agreements
- MEMASSIN : Mass Maintenance of info records
- XK99 : Mass Maintenance of vendors Read more
Transaction Codes – FI
F-01 Enter Sample Document
F-02 Enter G/L Account Posting
F-03 Clear G/L Account
F-04 Post with Clearing
F-05 Post Foreign Currency Valuation
F-06 Post Incoming Payments Read more
SAP Tips – VPRS condition Type currency in Billing
SAP Tips – VBAP-CEPOK – EDI Price/Value
Not all customer expected prices are causing the documents to be incomplete for with EDI. This will help:
SAP Tips – View Table Change Logs
If the IMG change log has been activated you are able to analyse the changes with the following programs: Read more
SAP Tips – Information Structure Updates
If you wish to see which information structures have been updated from Sales or Transportation you can use the following transaction codes:
SAP Tips – Content of database relevant to configuration of objects
Should you wish to see the tables and information extracted from them for a configured item in a sales document you can use the transaction code:
CUTABLEINFO.
Revenue Recognition
1. Is it possible to use a customized document type for the revenue recognition in FI?
2. Why is a revenue recognition not possible, and why is an entry made in the incompleteness log of the order or contract?
3. How can I use the revenue distribution, and what is the purpose of the revenue distribution?
4. When is an update of the revenue recognition data required, and how do I execute this update?
5. When are the sales costs transferred to CO-PA during the revenue recognition process?
6. Why are not all fields filled in the CO document for the revenue recognition documents that are also filled during the billing document transfer?
7. Why is the account for non-billed receivables, and not the account for deferred revenues, posted in the case of revenue recognition-relevant items in the credit memo?
8. Why is monitoring of the revenue recognition data required, and how do I monitor the data? Read more
Revenue Recognition Cancellation
Why does transaction VF46 (Revenue Recognition: Cancellation) not cancel the revenue recognition posting?
The revenue recognition cancellation (transaction VF46) is not a real cancellation in the sense of a reverse posting, but a posting to a prior period. This is based on the balances in the accounts when the cancellation is created.
How To Pricing – Condition Basis
This is a series of steps to create a pricing procedure covering Condition Basis, From and To Step Numbers and the condition basis formula.
SAP Tips – Manual conditions in the pricing procedure
SAP Tips – How is the cost determined in pricing?
In the order, the cost is generally taken from the valuation segmentof the material master.
In the billing document, however, it may have other sources. Depending on the business transaction, the costs can be taken from the goods issue of the billed delivery or, in the case of a third-party order processing or individual purchase order, from the respective purchase order, the goods receipt or the invoiceverification in purchasing. Read more
SAP Tips – In Billing how was condition VPRS determined?
Go to the detail display of the VPRS condition type.
- If the condition control (KSTEU) is set to ‘H’, the cost was taken from the goods issue.
- If it set to ‘A’, it was redetermined from the valuation segment of the material master, in case of ‘D’ or ‘E’ it was copied from the preceding document.
SAP Tips – ‘Y’ – “Inactive because of subsequent price”
Use of KINAK ‘Y’ (‘last price’ logic) to exclude conditions:
In addition to the condition exclusions, which you can influence in Customizing and in the condition master data, R/3 pricing still has a condition exclusion that was programmedusing a hard-coded logic: the ‘last price’ logic. Read more
SAP Tips – Using field PSTYV in a Pricing condition table
For technical reasons, the field PSTYV was included in the structure KOMP, but not in the structure KOMG (Allowed Fields for Condition Structures).
To solve the problem, proceed as follows:
1. Call the ABAP Dictionary (transaction SE11) and create the data type ZZPSTYV. Select PSTYV as the domain. As the short description, you can use ‘ZZ – Sales Document Item Category’ (for example) and as the field labels, you can use the field labels of the data type PSTYV. Save, check and activate your entries.
2. In the ABAP Dictionary (transaction SE11), enter the structure KOMPAZ, switch to change mode and make the following entries:
Component Component type
ZZPSTYV ZZPSTYV
Save, check and activate the change.
3. Note: Due to the changes in the structure KOMPAZ, the field ZZPSTYV is now known in the structures KOMG and KOMP because the structure KOMPAZ is included in both structures.
4. Call transaction SPRO. Go to ‘Sales and Distribution > Basic Functions > Pricing > Pricing Control’ and execute ‘Define Condition Tables’. Select ‘Conditions: Allowed fields’ and enter ZZPSTYV as a new entry.
5. Note: When you create the condition table Axxx, you can now use the field ZZPSTYV as a key field.
6. Populate the new field you defined by including the following source code line in the user exit USEREXIT_PRICING_PREPARE_TKOMP: MOVE xxxx-PSTYV TO TKOMP-ZZPSTYV.
In order processing, the user exit is available in the include MV45AFZZ, and in billing document processing, it is available in the include RV60AFZZ
Remember too that you can use this technique for other user defined fields. For header fields, use the structure KOMKAZ instead of the structure KOMPAZ, and use the user exit USEREXIT_PRICING_PREPARE_TKOMK instead of the user exit USEREXIT_PRICING_PREPARE_TKOMP.
More information is available in transaction SPRO when you go to ‘Sales and Distribution > System Modifications > Create New Fields (Using Condition Technique) > New Fields for Pricing’, and in OSS Note 21040
SAP Tips – Determination of price unit and unit of measure:
In the SD pricing procedure sometimes you may be confused how the system determines the Net Price:
Determination of price unit and unit of measure: Read more
SAP Tips – Billing document cancellations have hard coded copy routines
Very valuable tip on Billing document cancellations.
Routine LV60A006 is hardcoded by SAP for billing item cancellation.
Routine LV60A005 is hardcoded by SAP for billing header cancellation. Read more
Text Determination – Reference Duplicate Copy
In SAP sales and distribution processing, there are two options for copying a text to documents:
- a) Duplicating text
b) Referencing text
Whether you want to duplicate or reference a text, use text Customizing in transaction VOTX or VOTXN (as of Release 4.70) for each desired text type in the different text determination procedures.
In Release 4.6C or lower, the “Reference/duplicate” (TTXER-REDUP) indicator is called “Copy”. As of Release 4.70 it is called “Reference/duplicate” (TTXERN-REDUP). Read more
Smartforms – upload/download
Scenario - you have a smartform in a system and need to move it to another system and for some reason cannot get there with a transport path. Do you know that you can download a Smartform as an XML file to your desktop and then re-upload the smartform in your new system. This will copy the entire form, all logic as well as the global settings and pages and windows. This is especially useful for copying smartforms from ERP to CRM or visa versa. (obviously you will need to adapt a lot of extensive logic when delaing with CRM and ERP (due to different source tables/fields/variables etc. but you may save some time).
To do this use Read more
Variant Configuration Tips
The SAP easy access Menu for most variant configuration parameters can be executed with transaction CU00.
Configuration simulation can be run with CU50.
To check characteristics and values of a configured material use CU80.
Transaction PMEVC can be used to analyse the configuration model for a product. (You can simulate a configuration from here too.) Read more
Great Rebate OSS notes
Stumbled across this rebate OSS notes which is very good if you are a SAP consultant and want more information on SAP rebate processing:
Note 75778 – Consulting/troubleshooting for rebate processing
Plants Abroad – Great OSS notes
Here are the OSS notes you need to know of when implementing Plants abroad in SAP: Read more
