Ans: Receiving plant will raise PO then supplying plant will do delivery then intercompany invoice and lastly when goods reaches to receiving plant then do MIGO.

Ans: When receiving find any damage goods then he will raise return PO to supplying plant then supplying plant do return delivery with PGR and then return invoice and last receiving plant do MIGO when goods reaches to their.

Ans: When end customer gives order and stock is not available then customer send same requirement to other company code plant.

Ans: NLC

Ans: NLCC

Ans: When end customer gives order to company but stock will not available in ordering company plant then we change the plant to delivering plant and send the requirement to delivering company code plant and delivering company will deliver the goods to end customer and raise the intercompany invoice then ordering company will raise the invoice to end customer.

Ans: When we create intercompany sales order with normal customer then in condition tab we will find PI01 condition type which shows the intercompany value.

Ans: => Define order Types for Intercompany Billing. => Assign organizational Units By Plant. => Define Internal Customer Number By Sales Organization.

Ans: No, we cannot create a intercompany invoice without rising invoice to customer.

Ans: Delivery document.

Ans: Requirement is [22] and it checks that the ordering company and delivering company should be different.

Ans: Connecting IV01 condition type to reference condition type IP01.

Ans: Open your sales order VA02 select line item go to condition details then click pricing analysis and find that your pricing procedure is coming or not, then click on the condition PR01 and find due to which reason the value is not coming in the sales order. Maintain the prices condition record in VK11 for the validity of the sales order and then redetermine the prices. For all the future order you will get to see the price, be sure to check the material or sales org for the record.

Ek01 is Cost Condition, PR00 is item condition and PB00 is Header condition means cannot process automatically have to enter manually that will applicable to all items.

It’s not compulsory to determine free goods for a sales order. Free goods are determined for a sales order only if they are offered along with another product. For eg; if in my free goods settings, I’ve defined that for purchase 10 items of Product M1, i’l give 1 Free good of M2 then free goods need to be entered. Similarly in Inclusive Free Goods also free goods need to be entered in the sales order. Else for a basic sales order it’s not compulsory.

Transaction Code: OBD2 We can determine output determination by using Account group also in ‘OBD2’ we are having an option for same.

A customer can also be a vendor and a vendor a customer. Vendor tab in customer master data is used to make this link, it is used for intercompany flows, for returns processing.

OMIH – Checking rule for updating back orders OPJL – Define new checking rule OPJJ – Define scope of check marked against sales documents/deliveries. For e.g. you receive an order from a very important customer for material “A” but the entire quantity of A is committed to another customer “B” via earlier sales orders and this is where Backorder processing helps you to change the commitment and shift stock due for B to A. This is the benefit of this functionality. OMIH – Checking rule for updating backorders OPJL – Define new checking rule OPJJ – Define scope of check V_RA – Backorder Processing Data selection:-

Sold-to-party Customer code Mandatory

Sales Organization –  Mandatory

Distribution Channel – Mandatory

Division – Mandatory

Configure it in Status Profile -> BS02 Define & Assign Authorization Code to User IDs -> BS52 Pass the Codes & IDs to BASIS consultant to give the Authorization.

Customer account groups are used to classify customers into business partner functions that fit best the nature of the business transaction. It determines the role of a customer and customer master data. When a customer account is created, it is assigned to a certain account group.

Static and Dynamic Credit Check both take the following into consideration while performing a credit check. 1) Open Orders 2) Open Deliveries 3) Open Invoices 4) Open Items

Simple Credit Check:* Tr.Code – FD32 It Considers the Doc.Value + Open Items. Doc.Value: Sales Order has been saved but not delivered. Open Item: Sales Order has been saved, Delivered, Billed &Transferred to FI, but not received the payment from the customer. Static Credit Check it checks all these doc value & check with the credit limit 1) Open Doc.Value / Sales Order Value: Which is save but not delivered 2) Open Delivery Doc.Value: Which is delivered but not billed 3) Open Billing Doc.Value: Which is billed but not posted to FI 4) Open Item: Which is transferred to FI but not received from the customer. Dynamic Credit Check 1) Open Doc 2) Open Delivery 3) Open Billing 4) Open Items 5) Horizon Period = Eg.3Months Here the System will not consider the above 1, 2, 3 & 4 values for the last 3 months.

Tcode: FD32, check the menu function “Edit->Change Credit account” on “Status” View. After that, your current account will share the credit on your specified Credit account. Create as a partner and you can assign the credit limit to them in single transaction.

It’s nothing but an adjustment. Let’s say you have creates a bill of 10 bucks and latter you realize it’s not correct and the billing amount should be 8 bucks. To change the billing amount you have to create a negative bill worth -2 bucks. It’s a negative bill or in other words it’s an adjustment of credit type. Similarly debit type adjustments are also there.

1.Plant to shipping point Assignment ans: this is done in ovl2,: shipping condition, loading group, plant 2. Storage location determination for outbound delivery (Ex:FG01) ans: you will check for OVLsssssssssssssssssssssK tcode here you can assign the storage rule ,mala.mare,reta: mala : shipping point, storage condition ,plant mare:mala, then reta(back up procedure reta: plant, situation, storage condition Based on this you determine the storage location 3. Storage condition of material in MMR (Ex:06) ans: you can check the mm02, mm03 , storage location view , 4. Storage location in SO (we not maintaining stor.location @ SO level)

If we not maintaining the pricing date in the condition type the system automatically triggers the current date as a pricing date, so we need to maintain the pricing date for deliveries.

Instruction to move the material from source storage bin to destination storage bin with in the warehouse complex. It contains Material No, Material Quantity, source and Destination storage bin.

if u want to reversal u can use VL09 and then cancelled delivery to use transaction VLO2N.

It is imp to maintain the substitution reason by using the t.codeovrq, which explains the rule for determination.

strategy is an approach to migrating data from a legacy system to a new system — in this case an system. … Open transactions are those business transactions that are still under process when the company switches from the legacy system to the system

The main purpose of the customer views are for each department to determine the roles effectively in customer general data deals with all the details regardign the customer COMPANY CODE DATA DEALS WITH FINACIAL ASPECTSsales area data deals with sales ; billing ; shipping detaias along with the partner determination.

The billing document can be an invoice, per-forma invoice, cash sales invoice, credit memo and a debit memo. Whereas an invoice is a type of billing doc used to bill the customer for services or goods delivered.

General Item category Group is an extension item category group. Example: if one select item category group as NORM, but under item category group, NORM can further be classified as Service item, packaging item or Normal. Item category group determines how a material is processed in the sales order. When processing sales and distributiondocuments, the system uses the item category group to determine the item category and proposes it in the respective document. Item category group is defined in the Sales Org View 2 of Material Master Record. Example, in the standard SAP System, the item category group NORM is defined for materials kept in stock and the group DIEN for services and non-stock material.

General item category group is used by MM if u made any changes in that it will not effect is SD u can test this now. Item category group is used for SD to configure the item category if u make anything here it will effect in your sales document process.

Creating condition type as a discount u need to enter Condition Class as A and in plus/minus field u have to enter – (minus) . We specify whether a condition type is discount or surcharge in Details screen of the condition type. Where u have a field Plus/minus. If u take (-)ve it becomes discount and if u take (+)ve it becomes surcharge.

Returnable packaging process is where the customer will return the material used at the end of the complete usage, and that material valuation done as it is owned by the company itself only.

Ex: Gas cylinders, Cease fire, which are been able to refill.

It is the time taken to produce or bring material from out side.it is based on planned delivery time and in-house production time.

1. Chart of accounts 2. Sales organization 3. Customer account assignment group 4. Material account assignment group 5. Acct key

Storage loc determination depends on the storage loc rule that you assign to the delivery doc type. MALA: Shipping point / plant / storage conditions RETA: Shipping point / plant / situation MARE: 1st MALA if not possible, then RETA. Or any other custom logic. Whatever may be the case you do the determination in OVL3. The same storage location will be proposed in the delivery. Please note that the storage location determination happens automatically only in delivery. If you want to have it done in order, then a customized code should be written in user exit in MV45AFZZ.

Returnable packaging explains the case where customer returns the packaging material, and the same is not charged to the customer.

Factory calendar is maintained in four areas: Plant, Shipping point, Route, Customer and Sales Organization.

If the material determination procedure is assigned to the sales document type and condition record is maintained for material determination, then material determination triggered.

A handling unit is a physical unit consisting of packaging materials (load carriers/packing material) and the goods contained on/in it. A handling unit is always a combination of products and packaging materials.

Performa Invoice is generally used for Export Sales and have no relevance of postings into accounting. Its only serve as what will be the cost for the seller/purchaser. Billing Type F5 =Order related F8= Delivery related F5 is used by sales dept. for approvals from higher authority within his sales organization. F8 is used generally for custom purpose.

We can use output determination procedure to automate output processing. This is based on Condition technique. We have to assign the output determination procedure to the combination of 1. Output type 2. Partner function 3. Transmission medium time 4. Language

Those deliveries you want to create a single billing document should have the same criteria like, 1. Payer 2. Payment Terms 3. Incoterms 4. Destination country 5. Billing date 6. Actual Goods issue date 7. Foreign trade data 8. Billing doc type 9. Shipping conditions 10 Account assignment group of customer/material 11. Exchange rate 12. Billing relevance field in the item category Will be combined into one Billing document automatically and this is controlled by the copy control. GotoT.Code VTFL choose your delivery type and you’re billing type, goto header and in that at item level for the field VBRK/VBRP maintain the values as 001/007. In VF01 you have to input those deliveries and execute then those will be combined into a single billing document. Or you can do that in VF04 also.

A lump sum is a single payment of money, as opposed to a series of payments made over time (such as an annuity). … Prudential was of the view that for many retirees, a lump sum at the time of retirement was the most tax efficient option.

A rebate can mean the same as a discount when it refers to a reduction of the price during a sale but it also means refund. That is money given back after payment has been made. Rebates may be given on tax, rent and utility bills as well as on goods purchased.

When thereis not enough stock system will give the next delivery date by checking the availability of that quantity of material. In addition to above answers system checks if the same material is available with some other plant. if it is available in other plant we can do the delivery from other other plant. When they’re not enough stock system will give the next delivery date by checking the availability of that quantity of material.

– Revenue account – Customer receivables account – profit center account – Special purchase ledger account – Profitability Analysis Account

This is a very common requirement in many implementations depending on the scenario Sales order with one pricing procedure the same sales order when goes for billing Billing document with another pricing procedure Settings needed Order type VOV8 has a document pricing procedure Say A Billing type VOFA has a document pricing procedure Say B Sales area 1000, 10, 00 and CPP is 1 OVKK settings is like this 1000, 10, 00 DPP A, CPP1 Pricing procedure is RVAA01 1000, 10, 00 DPP B, CPP1 Pricing procedure is RVAA02 The control data in both RVAA01 and RVAA02 is different In VTFL between your del type to billing type under the header that item level The pricing type should be B (carry out new pricing) if delivery related billing In VTFA between your order type to billing type under the header that item level The pricing type should be B (carry out new pricing) if order related billing Now the same sales order will carry PP RVAA01at order level and RVAA02 at the billing document There can be some business scenarios you want to add some extra discount at the time of billing That time you have a discount type added in the billing PP so that it is reflected in the billing This is scenario dependent Hence SAP has given the option of DPP in VOFA so that by billing document wise we can differentiate To achieve this Copy control settings and DPP should be different both in VOV8 and VOFA.

As far as account key concern both are the same to find the right G/L Account through condition technique.SD account key will be from pricing procedure. On the other hand, FI account key will be from tax procedure. Acct keys are defined in FI only, sd people only use them, say in pricing. But ultimately they r used for posting the amounts to relevant GL accounts only .

It is NOT possible to create a Delivery without a Shipping point. Shipping point is normally a physical place at a fixed location, exactly from where goods goes out/ leaves for the customer (Ship-to-party). Without shipping point, Route also cannot be determined as the Transportation zone used in Route determination comes from the Shipping point. So no delivery creation is possible. Loading time and Pick/Pack time used in delivery & transportation scheduling, comes from the Shipping point. Transportation planning time and Transit time used in scheduling comes from the Route. So, if there is no Shipping point, no Route can be determined and delivery& transportation scheduling cannot be performed without the above lead times. As a result, system cannot confirm any delivery date etc. Therefore, you cannot deliver without a Shipping point. Note: We can do out bound delivery without shipping point only in Third party where delivery is done by vendor.

In SAP you will always get integration with other modules. SD will interact with FI, MM will interact with SD:- 1a. Looking at MM and SD interaction first, take the scenario of a third party order process. This process uses a purchase order (which is sent to your vendor). Also invoice verification is used further along the process to check that the invoice you send to your customer is the same material and quantity as that which the vendor sends to you (but obviously shipped directly to your customer). 1b. Billing is an SD function. But SAP needs to know, when processing a customer’s payment, to which GL account the payment has to be processed. For instance payment of a UK based material would be placed in a different GL account to that of a non-UK based material. Furthermore, a UK based customer may have a different GL account to that of an Export customer. This is configured in Account Determination. 2. ABAPers are there to essential do some bespoke development. Your integration, or interaction, with them would be when specifying the tables, fields, input fields, a simple process explanation, data mapping (if doing an interface from one system to another) etc. The link between SD and MM :- 1. When you create sales order in SD, all the details of the items are copied from Material master of MM. 2. MRP and availibility check related data is also taken from MM although you control this data in SD also. 3. While you create inbound/outbound delivery with reference to a sales order,the shipping point determination takes place with the help of the loading group, plant data, shipping conditions etc. This also refers to Material Master. 4. The material which you are entering in a sales order must be extended to the sales area of your sales order/customer otherwise you cannot transact with this material. There are many such links between SD and MM. Now the link between SD and FI :- 1. Whenever you create a delivery with reference to a sales order, goods movement takes place in the bacgground. eg. In case of standard sales order, you create an outbound goods delivery to the customer. Here movement 601 takes place. This movement is configured in MM. Also, this movement hits some G/L account in FI. Every such movement of good s hits some G/L account. 2. The accounts posting in FI is done with reference to the billing documents (invoice, debit note, credit note etc) created in SD. Thus this is a link between SD and FI 3. Tax determination: In case of a tax determination also, there is a direct link between SD and MM SD Integration points with other modules SD module is highly integrated with the other modules in SAP. Sales Order – Integration Points Module •Availability Check – MM •Credit Check – FI •Costing – CO/ MM •Tax Determination – FI •Transfer of Requirements – PP/ MM Delivery & Goods Issue – Integration Points Module •Availability Check – MM •Credit Check – FI •Reduces stock – MM •Reduces Inventory $ – FI/ CO •Requirement Eliminated – PP/ MM Billing – Integration Points Module •Debit A/R – FI/ CO •Credit Revenue – FI/ CO •Updates G/ L – FI/ CO (Tax, discounts, surcharges, etc.) •Milestone Billing – PS Return Delivery & Credit Memo – Integration Points Module •Increases Inventory – MM •Updates G/ L – FI •Credit Memo – FI •Adjustment to A/R – FI •Reduces Revenue – FI SD Transaction Code Flow: Inquiry / Document type IN Tcode for creation VA11, VA12, VA13. Tables VBAK, VBAP Quotation / QT Tcode for creation VA21,VA22,VA23. tables VBAK,VBAP Purchase Order PO Tcode for creation ME21,ME22,ME23. tables EKKO,EKPO. Sales Order OR Tcode for creation VA01,VA02,VA03. tables VBAK,VBAP Delivery LF Tcode for creation VL01,VL02,VL03. tables LIKP,LIPS Billing MN Tcode for creation VF01,VF02,VF03. tables VBRK,VBRP To create a sales order we need purchase order number and custmer number. Before that, to create a purchase order we need to have material no, vendor no. To create vendor tcode is xk01(create), xk02(change) , xk03(display) Tables are lfa1. To create custmertcode is xd01, xd02, xd03. Table is kna1.

Toggle Content