Sap SD
Sap SD
Sap SD
Q Sales order stock 5598965 000010 does not exist when doing PGI we get
this error.
Ans manitain 561-E in mb1c ( 561 E is the movement type for stock against
sales order
zzost
Q Billing issue
Ans https://wiki.scn.sap.com/wiki/display/SD/FAQ+in+SD-BIL-IV+-
+Processing+of+billing+documents
Q Factory calender
SCAL
Q Table NAST
Q Proforma invoices
Ans Proforma Invoice:
1. You can create a Proforma invoice with reference to the sales order.
Create a sales order (VA01). Create the Proforma invoice with reference to the
sales order. Select the billing document type F5.
2. You can create a Proforma Invoice with reference to a Delivery
document. Create a delivery document (VL01N). Create a Proforma invoice with
reference e to the delivery document. Select the billing document type F8.
Proforma invoice is a document that is used for the documentation
purposes.
This is a mirror image of the original Invoice that would be created in
future date.
When creating Proforma invoice the accounting document will not be
created.
We can create u2018nu2019 number of proforma invoices by referring a
same document (Sales order or delivery).
Proforma invoices are used in Export businesses for documentation
purposes before goods movement. But the original invoices will be created during
goods movement.
Some government agencies will require proforma invoices rather than
quotations since the proforma invoices are mirror images of the invoices that will
be received while doing actual transaction.
Q Delivey split
Kindly check the following:
Delievery split can occur because of following reasons:
1. Different delivery dates for line items.
2. Different ship to parties for line items.
3. Different routes for line items.
Check whether the above data are same for all your line items.
The following data may cause to split as two deliveries:
- Check the shipping points of the two items it may be different.
- Check the item level partner functions in the Sales order is there
different ship to parties available for the two items.
- Check the Delivering plant of the items.
- Check the shipping conditions are different for the two items.
- Check the loading group of the two items
Q item cat KN ZGPR can not be invoiced with billing type ZFSD or item cat
ZOR ZPGR cannot invoice with billing type ZF2
Ans check copy control VTFA
Q Confirm quantity goes to zero after saving the order in 3rd party.
2) Recheck the ATP for both the line item and check confirm quantity before saving
the order( it should not be zero).
2. if you check the statistics option in your pricing procedure and if you
maintain accrual key ,then system will post to accrual account
3. In VKOA if you maintain account key in your pricing and no statistics then you
have to maintain only one GL account . then system will post the value to
respective GL accounts .
4. if you maintain Accrual key in pricing procedure then here you have to maintain
GL account and provision account , to knock of the values from customer account .
5.if you not maintain statistics check in your pricing then you have to check the
accrual in your condition type so that value will post to your FI accounts.(for
ACCURL key)
note -- if statistics check is there in your pricing procedure then you cant able
to pass the values to normal account key . this is standard behavior ."
Account key enables amount to post to certain revenue accounts, for example freight
charges. When you add freight related condition types, it will be added to separate
G/L accounts, means this will not be added to material price.
With the aid of the account key, the system can post amounts to certain types of
accruals accounts. For example, rebate accruals which are calculated from pricing
conditions can be posted to the corresponding account for rebate accruals."
at the output we will get billing for particular output type and
billing type
Q what is alt condition type and condition base value in SAP pricing
procedure
Ans "Pricing � Alternate Calculation type, Alt Condition base value and
Requirements
2 Replies
The alternate condition base value (Alt CBV) is used as the calculation basis only,
while the alternate calculation is used to modify the final value.
For example, imagine you have a condition type ZPR1, with a condition record
maintained (master data) for $10. Now, condition ZPR2 also exists lower in the
schema, but with a rate of 10%. The standard calculation would result in a final
value of $11.
The alternate base value could say, �don�t use $10 as the basis � use the original
price PR00 only, which was $9.� Then, the final value would be $10 + (10% of $9) =
$10.9.
The alternate calculation routine says, �ignore the 10% altogether. Instead, use an
externally calculated 20%.� Then, you end up with a final value of $10 + (20% of
$10) = $12.
Put them both together, and you could end up with $10 + (20% of $9) = $11.8.
Normally if you want to calculate a value you have to use a calculation type for
determining the value. This calculation type is either addition, subtraction or
multiplication. Similarly SAP also has got a default calculation type in the
control data of the condition type. There you have the options of either Qty
based , Fixed Amount Based or Percentage based.
Here suppose if you define your condition type that calculates the base price of a
material on Qty based. Then the calculation will be done based on the quantity of
the material. If the customer orders 10 Nos and you have maintained a unit price of
$10,- for each material then the value determined is $100,-. Similarly if the
discount condition type , you maintain the calculation type as %. This means if you
maintain the value of 10% in the condition record. Then this percentage is taken as
the calculation type and the condition value is determined.
In some cases you have to forego the default calculation types and use the customer
specific method for calculating a value. For ex if you are calculating the Freight
charges for a Material . it depends on so many criteria like, the weight, volume
and also the minimum amount etc etc, in those cases, you forego the default value
and then use the alternative calculation type in calculating the condition value
against the particular condition.
If you have to calculate any value then you have to have a base value for it. For
ex if you want to calculate the discount of 10 % for a material then you have to
have a base value on which this 10% is calculated. Normally you take the condition
value of the base price of the material to calculate the value.
Now you don�t want to take the base value and take other values as base value which
are derived on some formula. So you create a routine which will do the mathematical
operations in the routine and derive you a value which is now used as the base
value for calculating the condition value for a particular condition type.
Requirement:
A factor in the condition technique that restricts access to a condition table. The
system only accesses a condition table to determine the price if the requirement
specified has been met."
It is quite possible that you may have more than one condition type in your pricing
procedureoffering a discount to a customer. Should the discounts be automatically
determined, there is the risk that the customer will receive all the relevant
discounts and thus purchase the product lower than heshould. By using condition
exclusion groups, you can ensure the customer does not receive all discounts, but
instead only receives, for example (the best of the four discount condition types).
Menu Path
The path here is IMG, Sales and distribution, Basic functions, Pricing, Pricing
control, Condition
Transaction Code
There are four possible methods of using the condition exclusion groups:
Selection of the most (or least) favorable condition type within a condition
exclusion group
Selection of the most (or least) favorable condition record of a condition type, if
more valid condition records exist (such as selection from different condition
records of the condition type PR00)
Selection of the most (or least) favorable of the two condition exclusion groups
(in this case, all condition types of the two groups are cumulated and the totals
are compared)
We will use the example of the most (or least) favorable condition type within a
condition exclusion group as an example, using the two discount condition types
K005 and our created Z007.
One now proceeds to assign the condition types to the exclusion group.
Transaction Code
The code here is [OV32]. , assign the relevant condition types to the condition
exclusion group.
Menu Path
After completing the assignment of the condition types to the exclusion group,
proceed with
assigning the condition exclusion group to the pricing procedure as follows: IMG,
Sales and
Transaction Code
The code here is [VOK8]. After selecting the pricing procedure for which you want
the condition
NOTE: Do not forget the condition types that you want the system to
compare must exist in the pricing procedure and have valid condition
records created for them.If you now create a sales order using the same pricing
procedure that the exclusion group is
assigned to, you will find that the condition offering the most favorable discount
to the customer is
represented in the pricing procedure that the condition type Z007 has offered a
discount of 10 percent off
the sale price or a real value of 30 DEM, while condition type K005 has offered a
real value discount
of 10 DEM. The system then takes the best discount for the customer between the
two, which is
Z007, and makes the other discount, K005, inactive. This can be seen by double-
clicking on K005.
exclusion item.”
the product has a lower sales price of, say, 90 DEM per item. The result would be
that condition type
Z007 offers a 10 percent discount, which is a real value of DEM, while K005 still
offers a discount
of 10 DEM. In this case, Z007 would be inactive and the system would use K005.
e.g. like after a sales order is created, it has many discounts, taxes,surcharges.
But during delivery also there are additional charges, like octroi, freight,etc
charges.
These cannot be tolerated into company profits, hence they are calculated at
delivery level to capture their exact value.
Also these cannot be pre-defined and be operated at any location, hence they are
alloted at delivery level.
2. Suppose an old customer wants some material from us. But due to some conditions
the PO cannot be sent by the customer. In this case we will create the delivery
without reference to an order."
Delivery Type LO and tcode is VL01NO
........... no pricing
x..........pricing standerd
In above scenario the Selling Company need to ensure that the Empty Containers are
returned by Customer within a specified period of time. If the Customer does not
returns the Containers they will will either raise a additional Invoice for
Containers or raise a Debit Memo.
These is where the indicator A - Pricing for empties in Item Category (VOV&) comes
into picture. Which means that at time of creating Sales Order for Chemicals the
Containers will be included in Sales Order & Invoice but will not be Priced for
i.e. Customer is not charged for the same. But if Customer does returns them then
we will charge them in future."
Use:
You can define price list types according to the needs of your own organization.
Price list types can be grouped according to:
You can use price list types to apply conditions during pricing or to generate
statistics.
Also,
In the customer master record, enter one of the values predefined for your system.
The system proposes the value automatically during sales order processing. You can
change the value manually in the sales document header."
"2) Price GROUP-Generally the usage of customer group is to group the
customers into One group so that whenever you want to give some additional discount
to that customer group then you can give
Example :
Say you have 2 customers and 2 customers have 2 pricing groups. Customer A belongs
to Wholesale Pricing grp and Customer B belongs to Retail Pricing grp. Maintain a
condition record With the help of the Customer / Pricing grp key combination. Now
for wholesale you give extra discount and for retail you give less discount. Now
when you create the sales order with Customer A then he will be getting extra
discount But if you create the sales order with Customer B then he will be getting
normal discount
"
3) MATERIAL GROUP
Q we can change the adress of partners in sales document, but this will
cause billling split
Ans "In you case Invoice is split due to different Bill to party address,
I face almost same issue in my last project in which one user change the Bill to
party address after few minutes another user just change the Bill to party address
by copy paste from customer master record. when I was checking the Billing split
criteria I checked bill to party address and it was same. finally went through
Split analysis and came to know Address code is different. when I went further
analysis and came to know address was changed once.
BUT when we change the address in our sales document it generates new address code.
every time it generate new code no matter Address is same or different.
If you want to avoid Billing address from your split criteria you have to update
the Data VBRK/VBRP and copying requirement in copy control."
You can use either ""Daily scheduling"" or ""Precise scheduling"" for your Shipping
Point.
If you ""Precise scheduling"" , then the above Lead Times are calculated in hours
and minute and if you are using ""Daily scheduling"" then the above Lead Times are
also calculated in hours and minutes but ultimately resulting in days (calculated
in days).
Daily scheduling uses the Factory calender for calculating the above lead times and
ultimately gives in days.
Precise scheduling uses the working time of the shipping point and calculates the
above lead times down to hours and minutes.
If you have specified a ""Working time"" for the Shipping Point, that indicates
that you are using Precise scheduling for your Shipping point.
I think, you have not specified the working time for the Shipping point by which
system considers as Daily scheduling, therefore system is taking the lead time in
days."
"You must create material master records for the different shipping
materials. You can use material
type VERP for these materials in the standard system. You define special data such
as packing
weight and volume permitted for each shipping material in the material master.
You can activate these fields for each material type."
Q SD and QM integration
Ans "In two stages, Quality will integrate with SD.
1) Before dispatching the final goods to customer, there will be a final inspection
randomly.
2) Once goods dispatched to end customer and in that if there is any quality issues
and customer returns the material, at this juncture also, quality inspection will
be carried out on the issue raised by customer. For this SD will raise a necessary
quality notification thru which, the message will be passed on to quality.
For both the above stages, in material master under Quality view, we would assign
inspection type (one for pre despatch and another one for post despatch).
In material master --> go to quality management view --> select inspection set up
--> select inspection type --> In inspection give 06 and 10 and click on active -->
save it."
"When the outbound delivery is created in SD, QM automatically creates
an inspection lot for the
delivery items that are relevant for inspection. The inspection lot tells the
quality assurance
department that the goods need to be inspected."
"You initiate printing of a certificate of quality from output control
of the outbound delivery at item
level. This function is primarily used for materials that are handled in batches."
Q Billin type F1
Ans F1- Order related Billing, Ex-If you want to invoice a customer for
services rendered, you would normally create an invoice with reference to the sales
order, because deliveries are not usually created for services.
F2- Delivery related billing
Quantity difference
(damaged or sub-standard goods.)
Price Difference
incorrect pricing of goods
The basic reason is return order item category REN is billing relence is Order
releted billing hence it doesnot refer to return delivery"
Q How to change the billing quantity at the time of billing for delivery
related billing?
Ans you can only change the item quantities for item categories that have
billing relevance K.
Go to VTFA select for your order type and billing type and then go to item category
and its details in the data VBRK/VBRP fields ensure that 001 is maintained if it is
for orders."
Field VBRK-ZUKRI is used in the billing header to store these
additional split criteria.
It is possible to include both order-related and delivery-related items
in the same billing document.
Before I show you some hints on the CFOP configuration on SAP, let me introduce
first a little bit about the CFOP concept.
The Brazilian Tax System is formed by several codes that are used to organize and
facilitate the companies� statements. CFOP is one of them.
The CFOP is a code defined by the Brazilian authorities that describes the type of
business transaction.
A CFOP code contains information on the good�s origin as well as the type of
operation, such as sales, returns, stock transfers, or services"
https://blogs.sap.com/2015/11/18/cfop-fiscal-code-of-operations-and-services/
Q how to set individual billing document should get created for each
sales document
Ans select data transfer routine 3 in Customizing for copying control
2. Run MRP for the Header Material, so the procurement proposals will generate for
the BOM items.
4. Once all the component stock is in place, convert the Header Material Planned
order to Production order through MD04/CO08.
For MTO the cycle will start from Customer order / Sale order and end with the
same.
In Master data you should mention the strategy Group in MRP3 and set in MRP 4
Indiv/coll as ""1""."
In MM01, basic data tab, Gen.Item category field 0001= MTO , 0002 for configurable
material
3) Create an order VA01 there you will see item category as TAK, schedule line as
CP, and requirement type as KE
4) MB1C to initialize the stock with special stock indicator E (means 561E)
creation of the customer Sales Order entering manually the advance-payment price
condition AR03 beside the normal price condition;
creation of the Downpayment request Sales Order (with reference to the previuos
Sales Order): in this case the price of the Downpayment Sales Order should be equal
to condition AR03 entered on the original Sales Order;
Creation of the downpayment invoice from the Downpayment request;
When the ""real"" Sales Order will be invoiced, the AR03 condition entered will be
deducted from the invoiced amount;"
https://help.sap.com/saphelp_erp60_sp/helpdata/en/32/71b6535fe6b74ce10000000a174cb4
/content.htm
https://help.sap.com/saphelp_erp60_sp/helpdata/en/c4/ecd353ca9f4408e10000000a174cb4
/content.htm
Q IDOC
Ans https://blogs.sap.com/2012/12/31/idoc-basics-for-functional-
consultants/
When an order was entered, the system used the January price list to
determine a price of $9.00 per piece based on the rate for 20 pieces. At billing,
the system uses the same price list, but uses the rate for 10 pieces (delivery
quantity) to determine a price of $9.50 per piece
If a company (say Walmart) has thousands of products, you have to identify that
these belong to Electronics division or clothing division � only then you will be
able to do any operational or analytical operations as shown above. So, a material
group is a means of classifying or tagging a material for operational or analytical
reasons."
In third-party order processing, your company does not deliver the items requested
by a customer. Instead, you pass the order along to a third-party vendor who then
ships the goods directly to the customer and bills you. The standard sales order
automatically creates a purchase requisition for the materials to be delivered by
the third-party vendor.
The incoming invoice from the vendor updates the billing quantity, so that the
customer-billing document can only be created after entering the invoice from the
vendor.
Process flow: Third party Sales Order --> Convert purchase requisitions to purchase
order --> Approval of purchase orders --> Invoice verification --> Billing
For this process, the vendor sends a shipping notification. The incoming invoice
from the vendor updates the billing quantity, so that the customer-billing document
is only possible after entering the invoice from the vendor.
The vendor then sends a shipping notification. After that a statistical goods
receipt is posted. The incoming invoice from the vendor updates the billing
quantity, so that the customer-billing document can only be created after entering
the invoice from the vendor.
Process flow: Third Party Sales Order --> Convert Purchase Requisitions to Purchase
Order --> Approval of Purchase Orders --> Post Statistical Goods Receipt -->
Invoice verification --> Billing" "Connfiguration- Connfiguration for wether GR
will be required or not is done in item category of PO which is defined from
schedile line category
Schedule line category CS is assigned to Item cat = 5 .This 5 get linked to Goods
receipt with reference to a purchase order through
https://wiki.scn.sap.com/wiki/display/ERPFI/Valuated+Sales+Order+Stock+Configuratio
n
https://wiki.scn.sap.com/wiki/pages/viewpage.action?pageId=235670754
Q SD Interview question
Ans https://blogs.sap.com/2015/09/16/sap-sd-questionnaire-for-scoping-and-
better-understanding-of-business-scenario/
Q Chunking
Ans https://blogs.sap.com/2015/04/03/success-in-sap-sd-part-1-chunking/
Q IDOC
Ns https://blogs.sap.com/2014/09/18/approach-for-system-and-business-
process-integration-with-edi-business-partner-in-sap/
Q Fixing the Date after the Availability Check in the Sales Order� or
maybe not?
Ans https://blogs.sap.com/2013/01/02/fixing-the-date-after-the-
availability-check-in-the-sales-order-or-maybe-not/