Professional Documents
Culture Documents
SAP SD Sample Certification Questions in Sales Order Processing
SAP SD Sample Certification Questions in Sales Order Processing
Processing
To take the SAP SD certification, contact your local or regional SAP Education
training center at this url :
http://www.sap.com/services/education/index.epx
Caution: more than one answer may be correct.
Please mark ALL correct answers.
Question:
Which statements concerning goods issue are true?
A
B
C
D
E
Question:
Which of the following statements about billing are correct?
A. Invoice dates for creating invoices at certain times are maintained in the calendar.
B. You cannot carry out pricing again during billing.
C. A transaction-specific requirement, such as "deliveries must be combined in a
collective invoice" can be set to control
billing.
D. If there are several payers for one delivery, only one billing document is created for
each player.
Question:
How is the schedule line determined?
A.
B.
C.
D.
Question:
When processing a billing due list, you have the following options:
A. The invoicing run can be started as a simulation run.
B. For performance reasons, the invoicing run via billing due list processing can only be
carried out in batch.
C. The invoice run can be carried out for delivery-related and order-related billing
documents simultaneously.
D. Order-related billing documents and delivery-related billing documents must always
be created separately.
Question:
How does the SAP system enable you to check the reason for documents not being
combined in a billing document?
A. Using the Spilt analysis function in the environment menu of the billing document.
B. Control of the document flow.
C. Control of the billing log.
Question:
How is the schedule line determined?
A.
B.
C.
D.
Topic Areas
General Questions (+)
Sales (++)
Times in R/3 to calculate Delivery Dates
Processing Inquiries and Quotations
Sales Order Processing
Outline Agreements
Incompletion
Controlling Sales Documents
Copy Control
Special Business Transactions (Cash Sales, Rush deliveries, Consignment, Delivery
free of Charge)
Pricing (++)
Taxes
Rebates
Shipping (++)
Transportation (+)
Billing (++)
Organizational Units
Credit Control Area
Maintaining Credit Data
Controlling Credit Automatically
How Credit Blocks Affect Subsequent Functions
Components of Risk Management
Output
Text Determination
Text Processing
Lists
Interface Modification (Account groups, Customer Master field selection, Material
Master field selection, Table Control, Transaction variants)
Material Determination
Special Business Transactions (+)
Shortage
Availability check
Partial Deliveries
Backorders
Third-Party Orders
Stock Transfer
Stock Transfer with SD
Cross-company Stock Transfer
Stock Transfer
Cross-Company Business Transactions
Processing of Complaints
Special Order Types
Basis in Integration (Project Experience or Participation in Case Study)
- Requirement class
Source
OR - Standard Sales Order
ZOR - Your Sales Order
2.
3.
4.
5.
6.
7.
8.
The connection between the project and the sales document item is made
in the individual
schedule lines of the item. Each schedule item can be assigned to a
network in a project.
To display the project-related data for a schedule line, proceed as
follows:
In one of the overview screens of the sales document, select
1.
2.
Item
Turbine
100,000
Billing Plan
Billing date Description
Billing Status
01-10-94
Contract
01-03-95
Assembly
01-04-95
Maintenance
01-05-95
Acceptance
01-06-95
Final invoice
Value
10
30
30
30
..
10,000
30,000
30,000
30,000
..
Billing Block
x
x
x
x
Milestone
x
x
x
x
Network/Activities
Milestone
Assembly
Maintenance
Acceptance
Estimate
01-03-95
01-04-95
01-05-95
Actual
01-03-95
For each billing date in a milestone billing plan, you can specify
whether the billing
date is:
1. fixed
2. always updated with the actual date of the milestone
3. updated with the actual date of the milestone, if the date is
earlier than the
planned billing date for the date
0
1
Tax Exempt
Liable for Taxes
MWST
Customer Taxes
0
0
1
1
Material Taxes
0
1
0
1
Rate Taxes
0%
0%
0%
9%
In this example, if both the Customer Master and Material Master Tax code is 1, Tax will
be included when you create the Sales Order.
For example, if you are selling a goods which are free for tax to any customer, put the
Tax Indicator (at MMR as '0'). If your
material is tax liable pur the Tax Indicator (at MMR as 1). If your customer is not liable
for tax at all (like the case of Indian
Defence organisations) put the Tax Indicator (at CMR as 0) or 1 in case fully tax liable.
3) Now, at VK11 you need to mainatain your pricning conditions with all the
combinations like:
10
11
01
00
4) While maintaining your Material Master Records or Cusotmer Master Records, you
must identify, which are tax liable and which are tax exempeted.
5) In anycase, as a SAP standard Best Practises, while processing a sales order, you must
retrieve a Tax condition record from SAP database only and not entered Manually.
Accordingly, at V/06, the MWST condition Defintions, the field for 'Manual Entries', it
would be marked as - D (Not possible to process Manually).
Due to this setting, normally, you cannot maintain Condition tax code during sales order
processing. And in Cusotmer Master, you can only maintain Tax Indicator and not Tax
Code.
6) In case your client insists for Manual entry of Tax code during Sales Order processing,
you can change the field at point 5) above to C-Manual entry is priority instead of D.
Assign the procedure to the pricing schema, and maintain copy control so that pricing is
not copied from Sales Order.
To achieve this, copy the standard pricing to a ZXXXX Pricing.
Define new document pricing procedure in SM30 - V_TVKV for billing.
Assign new document pricing procedures to billing types in SM30 - V_TVFK_PR
Define the Condition Exclusion Groups in OV31.
Assign the Condition type for the Condition Exclusion Groups in OV32.
Assign the Billing Pricing Procedure in VOK8 for the Condition Exclusion Groups.
When billing document is being created just enter manually your new price and the
pricing program logic will include only the higher price one, excluding the rest that are
lower price.
The pricing date is proposed based on the setting you make in the Sales document
configuration. ( T code : VOV8)
You have a field" Prop.f.pricing date " in the Requested delivery date / pricing date /
purchase order date segment.
Then you can choose the follwoing options:
Blank - Indicates the current date as the pricing date
A - Indicates the date based on the requested delivery date
B - Indicates the date based on the order validity start from date
And the pricing in the billing document is copied from thte sales order / Delivery
document..
It again depends on the setting u have in the copy control from order - billng or delivery billing.
In the copy control, in the item settings you have two fields relavant for this.
One is pricing source and the other is pricing type.
The pricing sources are generally the order. But if you want you can change it to other
values mentioned in the drop down,
but this values have no effect if the pricing type is B.
Any other value other than B in the pricing type will take the reference document price
mentioned in the pricing source field.
but for the pricing type B. The new price is determined in the billing order.
How can I make the system auto create all the Sales Order date during creation?
Each Sales Order can have different date proposal settings.
Follows this step to set the default Sales Order Type proposal date:
- Goto VOV8, double click on sales order type.
- Look and tick the fields Propose delivery date and Propose PO date.
After making the necessary IMG changes, you need to input the Delivery Plant field for
each Materials that you want the system to propose the default date.
To change the Materials field Delivery Plant:
Goto MM02, Select the View Sales: Sales Org. Data 1 and fill in the Delivery Plant.
Testing:
Now, try creating a new sales order for the material and SAP will auto proposed all the
dates in the sales order.
When using transaction VF04 or Billing (background), the date of the billing document
(e.g. the current date) must be entered (In VF04 : settings, default data.)
In VF06 or background: variant with parametrization) to avoid an unwanted split due to
the billing date.
This OSS notes is very helpful :11162 - Invoice split criteria in billing document
36832 - Invoice split in fields from the sales order
RV64A901
FORM FRM_KONDI_WERT_600.
XKWERT = KOMP-WAVWR.
ENDFORM.
The pricing procedure than looks like that:
Step 1 VPRS statistical, subtotal B, reqt 4
Step 2 PR00 Altcty 600
Whilst the availabilty check at the requirement class level via global and mandatory
configuration the schedule line catgry availability check deals with the order.
It is mandatory that the reqmnt class is flagged off for avlblty check and the schdelu line
cat need not be.
The following are the mandatory for Availability check to happen-1. Must be swithced on at the requirment class level and at the schedule line level.
2. Reqmnt type must exist by which a requiremnt class can be found
3. There must exist a plant and is defined
4.Checking group must be defined in Material Master records(it controls whthr the
system is to create individual or collective reqmnt)
A combination of checking gropup and checking rule will determine the scope of
availbaility check.