Third party few questions

FAQ, VA02, third-party, individual purchase order, sales order stock, individual purchase order, change quantity, change in
quantity, delivery address, ship-to party, item category, TAS, TAB

1. Question: Can I subsequently change the quantity for a third-party item or individual purchase order item?

Answer: Yes, you can subsequently change the quantity of a third-party item or individual purchase order item. If that item has
not been ordered yet, the change does not cause any problems because the quantity in the purchase requisition is updated as
well. If a purchase order item already exists, it is absolutely necessary that you consider several issues that are covered in the
following FAQs. For this reason, please continue reading.

2. Question: I want to decrease the quantity for a third-party item or individual purchase order item that has already been
ordered. What do I have to consider in this case?

Answer: If you decrease the quantity in the sales order, the system issues a warning message that this item was already
ordered, but the system does not prevent the change. However, you should remember that the original quantity has already
been ordered and that you must therefore maintain the purchase order in a system-conform manner. There is no automatic
function here except for the ALE scenario because the maintenance is connected to an activity. This is the case because you
generally have to inform your vendor about this change in quantity. This topic is also explained in SAP Note 210942.

3. Question: If I decrease the quantity for a third-party item or individual purchase order item that has already been ordered, the
system confirms the original, higher quantity. Why does this happen?

Answer: The system confirms the original quantity if the respective purchase order item has been confirmed. If it has not been
confirmed, the system confirms the new quantity in the order item (also refer to FAQ 549583 regarding the question: 'When is a
purchase order item confirmed?'). In both cases, you must maintain the purchase order item manually as described in the
previous answer.

4. Question: How can I increase the quantity for a third-party item or individual purchase order item that has already been
ordered and do this in a system-conform manner?

Answer: You should not increase the quantity directly in the item overview but rather create a new request schedule line in the
scheduling screen. Then the system generates a new PReq item from which a new purchase order item can be generated
(within the same purchase order or in a new one). This is the only way if the purchase order item was already confirmed. If the
purchase order item was not confirmed, you can increase the quantity in the order item and in the purchase order item as
explained for the quantity decrease. For more information, see SAP Note 445451.

5. Question: What do I have to consider when I change the quantity for a third-party item or individual purchase order item with
an automatically generated purchase order (ALE scenario)?

Answer: In the ALE scenario, the change in quantity (increase or decrease) is transferred automatically to the respective
purchase order item, and the latter is updated. In the sales order item, the system carries out a rescheduling if the respective
purchase order item was not confirmed. You must be careful if the respective purchase order item was already confirmed; in this
case, the system does not carry out a rescheduling. Instead, it copies the date confirmed by the purchase order, which you may
need to discuss with your vendor. For detailed information, see SAP Note 449592.

6. Question: Can I change a third-party item into an individual purchase order item after saving the sales order?

Answer: Yes, you can change the item category from third-party to individual purchase order (TAS => TAB in the standard
system). However, if a purchase order item already exists, you must delete it beforehand. This topic is also explained in SAP
Note 210989.

7. Question: Can I change an individual purchase order item into a third-party item after saving the sales order?

Answer: No, you cannot change the item category from individual purchase order to third-party (TAB => TAS in the standard
system) because an individual purchase order item generates a CO object in the background that does not allow this change.
Depending on whether a purchase order item was generated, you must delete it first. Then you must reject or delete the
individual purchase order item, and finally you have to create the third-party item again. This topic is also explained in SAP Note
210989.

8. Question: What do I have to consider when I change the ship-to party for the entire sales order or for a third-party item?

Answer: In the third-party scenario, the ship-to party of the third-party item in the sales order is identical with the delivery
address of the respective purchase order item. Up to and including Release 4.5, there is no automatic function for a
synchronous change, so this must be done manually in both documents. As of Release 4.6, the system automatically updates
the delivery addresses from the purchase order items if the ship-to party of the third-party item changes. The change of the
delivery address in the purchase order is therefore no longer possible; thus the tab 'Delivery address' is displayed only in display
mode in the purchase order transaction.

For more information, see SAP Note 204190.

https://www.tutorialspoint.com/sap_scm/sap_scm_interview_questions.htm

https://www.tutorialspoint.com/sap_sd/sap_sd_online_test.htm

Exceptions

SO01 - Mail/inbox

VKM1 - Blocked SD documents

 
Sales and Distribution Documents

VKM2 - Released

VKM4 - All

VKM3 - Sales document

VKM5 - Delivery

V.01 - Incomplete SD Documents

VA14L - Sales and distrib.documents blocked for delivery

VL06 - Deliveries

VF05 - Billing documents

 
Account

FD10N - Display balances

FD11 - Analysis
 

Item

FBL5N - Display/Change

 
Master data

FD32 - Change

F.34 - Mass Change

FD33 - Display

FD24 - Display changes

 
Credit management info system

F.31 - Overview

F.33 - Brief overview

F.32 - Missing data

FCV3 - Early warning list

FDK43 - Master data list

S_ALR_87012215 - Display changes to credit management

S_ALR_87012218 - Credit master sheet

 

Tools

FCV1 - Create A/R summary

FCV2 - Delete A/R summary

For this use T-Code MB1C Movement Type: 561 this is for Good receipts without reference.
Movement Type 501 this is used for receiving goods with Purchase Order
Key components in SAP Sales and Distribution module are −

 Customer and Vendor master data

 Sales Support

 Shipping of material

 Sales Activities

 Billing related

 Transportation of products

 Credit Management

 Contract Handling and Management

 Foreign Trade

 Information System

 VTAA This control is used for copying from sales order to sales order
 VTLA This control is used control for copying from sales order to delivery
 VTFL This control is used control for copying from delivery to billing doc
 VTFF This control is used control for copying from billing doc to billing doc
 VTAF This control is used control for copying from billing doc to sales order
 VTFA This control is used control for copying from sales order to billing doc

Which of the following can be used to avoid Purchase Order duplication?  

Check PO number field

Which of the following is maintained in conditional records about free goods?

Calculation Rule

how to arrive same day two difference prices for same material/customer

This is possible through some careful customization

In your condition table you need to bring the field PRICE LIST

That is customer/ Material/ Price list

That is customer ABCD / Material X / Price list 01---Price is Rs 10

That is customer ABCD / Material X / Price list 02---Price is Rs 20

The condition records to be maintained like this

So same material and same customer with price list 01 price is Rs 10 and with price list 02 price is Rs 20

Now in sales order you will find price list field in item details SALES B tab

Through incompletion log you can make this field as an mandatory field

Now in sales order same material and same customer according to the price lists different price is picked

In img-sd-basic functions-Maintain Price-Relevant Master Data Fields--here you can define different price lists

Regards

GST related question

https://blogs.sap.com/2017/06/08/a-solution-for-indian-gst-implementation-for-simple-procurement-scenario-using-taxinn/

https://www.stechies.com/gst-goods-service-tax/

Goods and Services Tax (GST) is an indirect tax throughout India to replace existing multiple taxes levied by the central and st
ate governments.

Applicable GST rates are determined by the combination Nature of Purchase and Harmonized System of Nomenclature (HSN) 
code assigned to material.

CGST  Central Goods and Service Tax

SGST  State Goods and Service Tax

IGST  Integrated Goods and Service Tax

Configuration Steps:

Steps t-code

 Assign Tax Procedure to Country  OBBG

 Define Tax Access Sequence  OBQ2/OBYZ

 Define Condition Types(Tax)  OBQ1/OBYZ

 Create account keys  OBCN

 Define Tax procedure  OBQ3/OBYZ
 Assign GL to account keys & GL  OB40

 Create Tax code in Country  FTXP

 Maintain Tax Codes for Excise Duties Using Condition Technique  SM30 – J_1ICONDTAX

 Maintain Tax Condition Records  FV11

Intercompany sales processing shall be initiated with the sales organisation creating an order for the delivery plant belonging to
another company code.

The system checks sales organization and distribution plant company codes and conducts intercompany billing processing via
Inter-Company Billing document automatically.

The plant in the company code of delivery delivers the goods to the customer for whom the sales organization has placed the
order.

In this case , two billing documents are created:

 The customer billing document that is sent from the sales organization to the customer who receives the goods.
 •An Inter-Company billing document that is forwarded from the delivery plant to the sales organization

Pre-requisites for intercompany

 The ordering sales organization and the delivery plant must be governed by different company codes.
 The required combination of the Sales Organization and the Delivery Plant must be maintained.
 Sales Area – Sales Organization, Distribution Channel and Division shall be assigned to all plants in which the sales
processing of Intercompany is carried out.
 Intercompany Billing Document type must be assigned to the type of sales document required.
 In order to represent the ordering Sales Organization, an internal customer number must be established in the Sales
Organization representing the delivery plant.
 Materials must be available in all plants participating in the Intercompany Sales process.
 Condition types representing the processing of sales by Intercompany shall be maintained in the pricing procedure.
 Condition records for the required combination of sales organization and plant must be maintained
Intercompany Configurations
Menu Path: IMG- > Sales & Distribution->Billing->Inter Company Billing->Define Intercompany Billing Order Types.

Define Order Types For Inter company Billing:

Assign Organizational Units by Delivering Plant:

The sales organization, Distribution Channel and Division are allocated to plants for which inter-company processing of sales is
possible. Delivery Plant uses these specifications to process intercompany billing.

Menu Path: IMG- > Sales & Distribution->Billing->Inter Company Billing->Assigning Organizational Units by Plant

Define Order Types For Inter company Billing:

Assign Plant to Sales Organization and Distribution Channel:

Sales Organization and Distribution Channel must be assigned to the Delivery Plant to enable the processing of sales.
Menu Path: IMG->Company Structure->Assignment->Sales and Distribution->Assign Plant to Sales Organization and
Distribution Channel.

Assign Plant to Sales Organization and

Distribution Channel

Define Internal Customer Number By Sales Organization:

The Internal Customer Number must be assigned to the Ordering Sales Organization.

Menu Path: IMG- > Sales & Distribution->Billing->Inter Company Accounting->Define Internal Customer Number by
Sales Organization.

Define Internal Customer Number By Sales Organization:

Master Data –Preparation

Create Internal Customer Number By Sales Organization:
The Customer Master Record shall be established in the Sales Organization representing the Delivery Plant. The sales
organisation belonging to the Code of the Ordering Company shall be the internal customer.
Menu Path: Easy Access- > Logistics- > Sales and Distribution- > Master Data- > Customer- > Create.(XD01)

Define Internal Customer Number By Sales Organization:

Master Data – Extend the material in the Delivery Plant

Enter the Delivery Plant in the material master records that will be relevant to the sales transaction will be carried out by the
Ordering Sales Organization. Extend the material master records in the Delivery Plant: Enter the Delivery Plant in the material
records that will be relevant to the sales processes carried out by the Ordering Sales Organization.

Menu Path: Easy Access- > Logistics- > Sales & Distribution- > Master Data- > Products- > Material- > Other Materials-
> Change.

Extend the material in the Delivering

Condition Type Configurations

Creating Intercompany Condition Types: The delivery plant uses one of the following condition types to bill the sales
organization.

 PI01 Intercompany: fixed amount per unit of material

 PI02 Intercompany: percentage of the amount of the net invoice.
 These conditions specify that the price charged by the delivery plant to the sales organization shall be shown as a
statistical value in the order of sale and as an effective charge in the internal invoice.
Menu Path: IMG -> Sales and Distribution ->Basic functions -> Pricing-> Pricing Control -> Define Condition type.(T-
code: V/06)

Condition Type

Master Data – Condition Records

Creating Inter Company Condition Records:

 PI01 Inter company: fixed amount per material unit

 PI02 Inter company: percentage of the net invoice amount.
Menu Path: Easy Access ->Logistics -> Sales and Distribution -> Master Data -> Conditions -> Select using Condition
Type ->Create
All Setup has been done , Now lets create intercompany transaction

Transaction Steps – Order Creation

Menu Path: Easy Access -> Logistics -> Sales & Distribution -> Sales -> Order -> Create
Create Order: The ordering Sales Organization shall prepare the order for sale. The system shall check the company codes and
the authorized combinations of the ordering sales organization and the delivery plant for the implementation of the Inter-
Company Billing process.

Sales order initials creation

Inter company Sales Order Creation

The system automatically performs pricing in accordance with the pricing procedure assigned to the sales organization. The
intercompany charge (PI01 / PI02) appears as a statistical value on the sales order screen conditions-the charge has no effect on
the final value of the customer’s order. The intercompany charge is not printed on the customer’s documents.
Sales Order Item Pricing condition

Transaction Processing – Outbound Delivery

Delivery shall be effected by the Ordering Company from the Shipping Point assigned to the Delivery Plant.

Outbound Delivery

Transaction Processing – Billing Document

Menu Path: Easy Access- > Logistics- > Sales & Distribution- > Billing- > Document Billing- > Create (VF01)
The Ordering Company creates the invoice for the end customer.The Payer and the Company Code are derived from the Order
created by theOrdering Company Code

F2 Invoice

Inter company Billing Document

The Company associated with the Delivery Plant bills the Ordering Company through the Inter-Company Billing Document. The
Payer Code and the Company Code are derived from the Order of the Order of the Company.
IV Inter company Invoice

IV Inter company Invoice

Posting of the Inter Company Invoice

Manual invoice posting is done after Post good issue has been done and systems prints invoice document using the output type
RD00, which is then sent to the end customer. The intercompany accounting transaction is automatically posted via IDOC / EDI
The system uses the output type RD04 included in the output determination procedure V40000, which is assigned to the internal
billing type.

Automatic posting of the intercompany billing

For the system to determine another delivering plant for the material in the customer order item, when entering a sales
document:

 Ensure that the same delivering/supplying plant is maintained in the Customer material info record if any.
 The internal customer master for the delivering sales organization must also contain the same plant.
The delivery company must be set up as a vendor in order to be able to publish the financial document of the ordering
company.

SAP SD - Credit Management - Tutorialspoint

SAP SD - Credit Management - Tutorialspoint

Please find the below the Main Difference between Intra and Inter Company:

P.O Order types and Delivery Types

STO: - Stock Transfer Order – Intra Company

Stock Transfer between Two Plants with One Company code.

The Purchase Order Type is Used in this case is "UB".

And the Delivery Type Used here is "NL".

Goods Movement type: 641

Item Category in delivery is NLN

STPO: - Stock Transfer Purchase Order – Inter Company

Stock Transfer Purchase Orders between Two Plants with Two Different Company Codes.

The Purchase Order Type is Used in this case is "NB".

And the Delivery Type Used here is "NLCC".

Goods Movement type: 643

Item Category in delivery is NLC

Billing Plan

It’s a schedule for individual billing dates for a single billing date
It define in header only further it apply in all line item
Type :
1periodic
2 milestone billing

Periodic billing: used for service product rental or maintenance. service product with time dependence price i.e calculation type
–M,N,O and P .which bill monthly , quarterly , yearly etc.

Milestone billing: used for sales project for big product like real estate or in big govt project.

Notes : on billing plan

Date proposal is used for periodic bill plan and not used fpr milestone
In advance – used to for any deviation support billied end of month but cuatomer wants to bil 2 days before so he can use this
option
Horizon – until which date bill plan is valid
On line order – check this filed if you want to Autom. Date Creation in Billing/Invoicing Plan Maintenance
Days in year/Days in Month :
Billing/Invoice Creation in Advance :- Check (X) this field
Automatic creation of correction dates in Billing Plan :- If this field is checked (X) , system can determines if correction date
has to be proposed .

Config steps:

1.Define Billing Plan,

2.Define date description
3.Define and assign date categories.
4.maintain date proposal for billing plan type
5.assign bill plan to sales doc
6.assign bill plan to item categories.
Related Exits :-

BILLING_SCHEDULE_DELTA

USEREXIT_MOVE_FIELD_TO_FPLT

USEREXIT_MOVE_FIELD_TO_FPLA

USEREXIT_DATE_PROPOSAL

https://blogs.sap.com/2015/08/28/billing-plan-periodic-sap-sd-part1/

https://blogs.sap.com/2017/10/20/sap-delivered-more-than-30-new-improvements-in-the-area-of-sd-sales-billing/

FIORI Interview question.

https://www.tutorialspoint.com/sap_fiori/sap_fiori_interview_questions.htm

Please explain to me the concept of resource related billing and its different between periodic and milestone.  In what kind of
business scenario do we use it? and what are the settings required to use it?

Periodic billing is used when you want to bill the customer at different points of time based on the periodicity or progress of the
work. 

Milestone billing can be used for this type of billing purposes when you want to have billing control from the project.

Resource billing is based on the resource consumption for the particular activities. Dynamic Item Processor (DIP) profile is used
for the resource related billing.

Steps to be followed:

1) Configure DIP Profile (T.code ODP1)

2) Specify the usage - 

(i) Billing & Result Analysis (RRB)
(ii) Request Quotation (Sales Pricing)

3) Specify - 
(i) Sales Document Type (PS2)
(ii) SD Doc Type CMR 

4) In Sales Order Type --> Sales Order Category - "L" (Debit Memo Request)

5) Document Pricing Procedure --> PS (Customer Project)

6) Select the billing usage and click on characteristics. eg--> Activity Type

7) Then define sources. Select "Actual Cost" as we use actual cost for RRB. Define%

8) Sources --> Selection Criteria: This would display all characteristics. Now in Activity Type --> Mention the activity type

9) If more activity type are being used then create set of activity type using T.code GS01

10) Material Determination --> Initially create material with "Material Type = Service"

11) The service material should be mentioned in the material determination

12) Criteria -- In criteria allocate the activity type for the specific material. (We can also use cost element, cost center, which we
have defined in characteristics)

13) Create Project (T.code CJ20N)

14) Create Sales Order (T.code VA01)

15) Book CATS 

16) Execute DP91 to view Sales Pricing

 

E invoicing:

eInvoicing is the system of invoice registration introduced by GSTN, wherein every B2B invoice generated by the supplier must be
submitted to GSTN in real time for the generation of IRN (Invoice Registration Number).

SAP Document Compliance: e-Invoicing for India allows for the registration of invoice and generation of Invoice Registration Number (IRN)
with direct integration to the eInvoicing System via GSP.

The eInvoice solution requires the installation and integration of the following components:
• SAP Enterprise Resource Planning (ERP)
• eDocument Framework in SAP ERP or in SAP S/4HANA
• SAP Cloud Platform Integration (SCPI)
• SAP Certified GSP
• Government tax portal - National Informatics Center (NIC)

https://blogs.sap.com/2020/09/23/gst-india-automated-e-invoicing-solution/
https://launchpad.support.sap.com/#/notes/2872365 - WEBNAIR

https://sap-se.zoom.us/rec/play/tcUsIrj8qG03HIaXtASDBv58W9S7KausgXIW-vFYyx2yBndWNVenY-
FGa7Z3ZQxy10PLTOAm148isGBQ?continueMode=true

https://blogs.sap.com/2020/08/08/insights-into-india-e-invoicing-implementation/

Batch Management;

1. Purchasing View
2. Work scheduling View- FG, SFG
3. Plant Data Storage 1 view

Automatic
Manual – MSC1N, MSC2N,MSC3N

MANUALLY – CREATION/RELEASE
AUTOMATIC

CREASE

CREATE – CHARACTERISTICS – CT01

Create class – CL01 (CONTAINS CHARACTERISTICS )

Storage location not determine – reason check OVL3 determination then if check parameter for shipping locaon plant

Qty control, in sales retun 100 k balde message 229 error message

1. Return order qty should not be increasesd say Billed qty of material X is 20 units
While returning Material X should be a maximum of 20 units
If made 21 it should throw error T code OVAH message class V4 message no 299 convert from warning to error thro
customization
2.Return order should be created only once referencing billing doc
To control that T code SE91 message class V1 message no 499 convert from warning to error thro ABAP help
3 Your issue is same like case 1 but the material X is entered as second line item in the return order with some qty
This case system is not throwing even a warning
Yes correct
This is to be handled with userexit
Discuss the same with ABAPer
Check these threads on return issues which is of different scenario than of yours
Forum post in ERP - Sales and Distribution (SD) General: Order Qty.
order-qty
Forum post in ERP - Sales and Distribution (SD) General: Return order
return-order

MD04 ALLOCATED STOCK FOR SALES ORER

es, you can block a material to discontinue its procurement. So, go to MM02 for this material and select views . In Basic
data 1-> X-plant matl status -> select blocked for procurement.Here you can block the material for all the plant. If you
want to 

FIORI –
MM16 TO DELETE MATRRIAL MASTER

S/4 HANA and its differences with ECC

Most of us are following the innovations & simplifications in S/4 HANA and wondering about the functionalities & business
benefits of implementing S/4 HANA (S4H).Find lot of questions on differences in ECC with S/4 HANA (S4H). Trying to highlight
the major(not a full list) differences in digital core of S4H as planned by SAP w.r.t ECC

Hana database

S4H can only be run on Hana database unlike ECC which can be run on Oracle , IBM DB2 etc.  Back bone of S4H’s design is
with HANA’s in memory capability and below design principles

 In-memory database means that data is read from memory i.e data always reside in main memory RAM (though Write
happens in hard disk) and hence in-memory database reads data much faster w.r.t traditional databases (fetching the
data from hard disk)
 Hana’s column based tables provide faster access (as only affected columns need to be read in a query), better
compression (due to few distinct values compared to rows), parallel processing (different columns can be easily
processed parallel)
 OLTP and OLAP capability in same system with real time reporting and predictive analysis
 There will be no aggregate (total), index and history tables in S4H.  Aggregates are created dynamically based on line
item table instantaneously (on the fly).

Single source of truth

S4H combines the data structures of different components (for FI , AA , CO , CO-PA and ML) into a single line item table
ACDOCA, called as Universal journal . It eliminates several aggregate and index tables. Now, data needs to be inserted only a
single table instead of several tables thus reducing the data foot print drastically.

MATDOC is also a new line item table for inventory management and it eliminates 26+ tables. Material documents will be stored
in MATDOC but not in MKPF or MSEG tables.

Merger of CO and FI

In ECC , FI GL accounts are mapped to CO primary cost elements . In S4H, only one field of universal journal is used to store
both GL account and cost element. Cost elements (both primary and secondary) are now GL accounts and hence created /
maintained (in FS00) with relevant Cost element category. Reconciliation (as in case of CO to FI) is not needed now. Period end
closing also will be faster.
New GL

S4H is technically very similar to new GL of ECC due to its data structure. Customers using classic GL need not use Document
split or parallel ledger. However, new GL’s functionality (Parallel ledger) is a pre-requisite for new Asset accounting .

CO-PA

Account based CO-PA is now the default option with Costing based CO-PA as optional. Both options can be run simultaneously.
Refer URL http://scn.sap.com/docs/DOC-65828 for more details.

Custom code

Read operations in custom code will be redirected to compatibility views (like V_COEP for CO line item table COEP) via a
special setting at database interface level (i.e invisible to source code) so that the custom reports can work without any
disruption.

Business partner

All customer and vendor master need to integrated / migrated as Business partner . Probably, SAP is trying to align the concept
of business partner as in other SCM applications like APO , EWM , TM etc as these SCM applications also will be natively
integrated with core of S4H in future releases. Customer-vendor integration (CVI) is a mandatory step. Refer
URL https://websmp201.sap-ag.de/~sapidp/012002523100007374172016E.pdf for more details.

Extension of Material number field : Material number can now be 40 characters from existing 18. It is a optional feature. Impact
of this extension on custom coding, interfaces, other SAP applications need to be evaluated before switching on 40 characters.
Refer note 2267140 for more details.

Credit management

ECC’s FI-AR-CR is replaced by credit management of FSCM (Financial supply chain management) . FSCM-CR is based on a
distributed architecture which allows interfaces with external credit rating agencies.  Traditional FI-AR-CR credit control setting
requires high degree of manual work. However, FSCM-CR has advanced features like

 Credit rule engine for automatic risk scoring & credit limit calculations
 Automatic update to master data on approval of credit limit etc.
 Work flow for credit events etc

ATP

ECC provides the option of availability check at the individual or summarized requirements (aggregated at daily or weekly
level) , however S4H uses only individual requirements (with no VBBS table) and probably the rationale is that S4H does not
have any aggregate table with its simplified data model.

SAP also has plans to integrate APO’s GATP (Global ATP) functionality in S4 core. Not sure whether all functionalities of GATP
will be integrated in S4 core.  Rule based ATP (For substitution of location (plant) or material), Multi-level ATP check, advanced
check for product allocation with ATP, advanced BOP (Back order processing) etc are some of the unique features of GATP
w.r.t ATP in ECC.

Location substitution allows to check the material availability at plant B (as set in master data or business rule) if the material is
not available at sales order plant A. If material is available in plant B, then a stock transfer order from plant B to A is created
automatically. This rule can be extended to a network of plants also.
SD pricing

There are some changes in data model in pricing and condition techniques like existing table KONV replaced by new table
PRCD_ELEMENTS with extended fields etc. Refer note 2267308 for more details.

MRP

MRP in ECC is run through batch jobs and during off peak hours. However, there is no need of batch job in S4H and MRP can
now be run in real time with HANA.

MRP can be run on plant and MRP area level, but not on storage location level. In ECC , Storage location can either be
excluded from MRP or planned separately . SAP recommends to use MRP area  with MRP type (ND in case of exclusion or VB
for re-order point planning) for those scenarios at storage location level. MRP with subcontracting has also been simplified.

SAP has plans to integrate the functionality of APO’s PPDS in core of S4H in future releases and hence probably aligning the
APO features like BOM to be selected through production version for in-house ,  unified source of supply (no source list , only
info record ) for external procurements with S4H core.

Foreign trade

Foreign trade functionality has been replaced by GTS (Global trade services). Advanced features in GTS w.r.t foreign trade are
SPL (Sanctioned party list) screening, automated embargo check (Manual in ECC), automatic & simplified license check
(manual and complex in ECC) , Automatic import / export declaration etc.

Material ledger

Activation of material ledger (ML) is mandatory. ML valuates inventory in multiple currencies. Traditionally inventory is mainly
valuated with a single currency in SAP ERP. ML allows valuation in two additional currencies. Today’s global organizations
operating in different countries desire to valuate inventory in multiple currencies. Like for example, a company in Norway dealing
with oil needs to maintain their books in Norwegian currency (NOK), they will also like to evaluate their inventory in USD as oil is
traded in international market in USD. This functionality is available in Release 1511 of S/4 HANA.

Refer the blog in URL http://scn.sap.com/community/s4hana/blog/2016/02/22/material-ledger-embedded-in-s4-hana–benefits-

and-challenges for more details on ML and its benefits & challenges.

Revenue recognition

ECC SD revenue recognition is being replaced by SAP Revenue Accounting and Reporting (RAR)  due to  new accounting
standard released jointly by the Financial Accounting Standards Board (FASB) and the International Accounting Standards
Board (IASB). New guide line is also in IFRS 15 issued in 2014.

Existing SD revenue recognition of ECC is based on Generally Accepted Accounting Principles (US-GAAP), International
Accounting Standards (IAS) / Financial Reporting Standards (FRS) and it provides the option of recognizing the revenue based
on an event (like Goods issue, proof of delivery ) or over a period of time (based on specific set of dates)   apart from standard
way of realizing revenue on billing. New standard introduces the 5 step model (Identify the contract, separate performance
obligations, determine transaction price, allocate transaction price and recognize revenue). SAP’s new Revenue Accounting and
Reporting (RAR) solution is in S4H.  for fundamental changes with IFRS 15 and also to meet the requirement of parallel
accounting and cost recognition .

Rebate
Customer rebates through existing SD rebate processing has been replaced by settlement management through Condition
contracts. Some details on condition contracts are in URL Condition Contract – Compensation Management – SAP Library

Output management

ECC message determination through table NAST is replaced by Business rule framework plus (BRF +) and target architecture
is based on Adobe document server and Adobe forms only. Refer OSS note 2228611 for more details.

Warehouse management

Existing WM module will be replaced by SAP’s new application for warehouse management EWM . There will be 2 options

 Native integration i.e inbuilt in S4H

 Side car approach for decentralized deployment

There are several advantages in EWM w.r.t WM like complex warehouse processing through Process oriented storage control
(POSC) , improved (easily customisable) RF functionality , Value added service like kitting , enhanced wave & replenishment
processes, labour management etc.

Native integration of SCM applications

Other SCM applications like  TM etc will be natively integrated with digital core of S4H. Refer
URL https://scn.sap.com/community/s4hana/blog/2015/11/19/sap-s-road-map-for-supply-chain-solution-with-s4-hana-and-its-
expected-benefits for more details.

User interface

Fiori is a new user interface . Refer URL  https://experience.sap.com/files/SAP_Fiori_UX_Overview.pdf for more details.

Activate implementation methodology

There is no concept of Blueprinting in S4H implementation. S4H has introduced new ‘Activate’ methodology. SAP offers pre-
built demo system with SAP’s best practices for specific business processes. Business users can now test in demo system
whether it meets their business requirement or not . Fit-gap analysis can be done after initial trial period . Refer
URL http://www.akili.com/wp-content/uploads/2016/01/SAP-Activate_Customer_v03.pdf for more details.

Where to find the User Exits on Sales and Distribution along with functionality?

To see the detail go to SPRO --- Sales and Distribution ---- System Modifications --- User Exits
There you will find all the details by checking IMG Activity Documentation. You will have User exit for - Sales Document Processing.

How to find out the list of users logged in to sap system for the last 5 days?

Solution:

1. TCode st03n
2. Then check that screen shot path
3. Then put Date, Time period from and to

What is the purpose of RSNAST00?

How is related to NAST entry creation?

When executing my form through rsnast00, it is giving a information message saying that "0 outputs were processed in total (0 success 0
incorrectly)", how to execute my program?

--

RSNAST00 is the program used to retrigger the output types(to make one more printout of the invoice for example). It is not specific to any
application. Hence it can be used for sales order outputs, delivery outputs and invoice outputs.

RSNAST00 can be used only if the output was triggered for the first time in Batch mode (i.e. it is not triggered in immediate mode (4) and
triggered in batch mode (1). Those kind of outputs can be triggered n number of times using RSNAST00

When RSNAST00, is executed, it checks the NAST table which has the data about all the outputs and select the only records which has
NAST-VSZTP is equal to 1. These output lines will be yellow in colour if you see in the document. When RSNAST00 processes these
records, it triggers the output and converts the line from yellow to green during which NAST-VSTAT will change from 0 to 1 for green.
 

You can run process output type from RSNAST00 only when the output type is set in schedule mode, its processing mode should be 1 not 4.

Check the settings from tcode NACE -> Condition records -> output type ->
The time should be set as 1. Now re-trigger output type from document and process it from RSNAST00, it will be processed without the
error you have mentioned.
 

An example for Billing output:

An example for Billing output:

Goto tcode VV32 - Fill in your own Output Type

At the Date/Time column, press F1, you will see these explanation. 

Fill in Time 1 or 2 if you wish to used the program RSNAST00.  It's work the same for all other modules.

Describe how the system chooses KOFI or KOFK when both are maintained in VKOA. In other words, I have the entry set up for both
conditions, however sometimes it chooses KOFI and sometimes KOFK depending on the billing type, but I don't see the setting on the billing
type that controls this.

Account determination procedure for all is KOFI00 but within this it somehow determines whether to use kofi or kofk - how?

Explanation:

In the standard SAP, SAP provided 2 condition types for SD module.

1. KOFI - If the using company code is not activated for Product Costing, this condition type will be used for revenue account determination.

2. KOFK - If the using company code is activated for Product Costing, PA, then this condition type will be used for revenue account
determination in the financial accounting as well as controlling.

Add a field to a new condition table in Pricing (Condition Technique):-

I will explain you the process with below example...Please follow steps in below sequence-

Try to add the filed from the field catalog.  In case the required combination field is not there, you can add the field through the following
process to filed catalog and create the condition table.   It is most common that one or other time we need to use this function while
configuring multi tasking & complex Pricing Architecture.

Here I'm giving a simple guide to add fields to the Pricing Field Catalogues:

For example you want to use field PSTYV ('Sales document item category') that is included in structure KOMP ('Pricing Communication
Item') as a key for a condition table.

When you create a condition table (Transaction V/03), however, the system does not propose the field in the field catalog.

Condition access, field catalog, allowed fields, KOMG, KOMK, KOMP, KOMPAZ, KOMKAZ, PSTYV are the other terms which we need
to know about, to add Fields.

Reason and Prerequisites: 

For technical reasons, field PSTYV was included in structure KOMP, however, not in structure KOMG ('Allowed Fields for Condition
Structures').

Proceed as follows:
1. Call up the ABAP Dictionary (Transaction SE11) and create data type ZZPSTYV. Choose PSTYV as a domain.As a short text, you can
use, for example, 'ZZ - sales document item category' and as a field label, you can use the field labels of PSTYV.Save, check and activate
your entries.

2. Call up structure KOMPAZ in the ABAP Dictionary (Transaction SE11) in the change mode and make the following entry:
Component Component type:
ZZPSTYV ZZPSTYV
Save, check and activate the change you made.

3. Note:Because of the change in structure KOMPAZ, field ZZPSTYV is now known in structures KOMG and KOMP because structure
KOMPAZ is included in both structures.

4. Call up Transaction SPRO. Navigate to 'Sales and Distribution -> Basic Functions -> Pricing -> Pricing Control' and execute 'Define
Condition Tables'.
Choose 'Conditions: Allowed fields' and include ZZPSTYV as a new entry.

5. Note:Now you can use field ZZPSTYV as a key field when you create a condition table Axxx.

6. Supply the new field you defined by including the following source code line in USEREXIT_PRICING_PREPARE_TKOMP:
MOVE xxxx-PSTYV TO TKOMP-ZZPSTYV.
In order processing you find the user exit in Include MV45AFZZ, and in billing document processing you find it in Include RV60AFZZ.

Consider that you can also use this note as a help if you want to use other customer-specific fields as key fields in a condition table.

For header fields, use structure KOMKAZ instead of structure KOMPAZ and
 USEREXIT_PRICING_PREPARE_TKOMK instead of
 USEREXIT_PRICING_PREPARE_TKOMP.

You can create and use condition indices. You can use these indices to display, change and create condition records with
reference. This transaction can include condition records with several condition types and tables. For example, you can use a
condition index if you want to see all condition records that apply to a particular product regardless of whether the records are
prices or discounts. In this case, you can use one of the standard condition indexes. Or you may want to see a list of condition
records that contain a particular sales deal and a material from a user-specified list of products. To display this information, you
can create your own condition index.
 Higher level item category depend upon the material type and itam category of the other item ( header item i.e tan for free of
goods ).
higher level item category is the item category of the high level item. It controls the item category of the item along with sales
document type, item category group, usage.
basically higher level item makes the functionality of how the item should behave along with material type.

SAP Smart Forms is used to create and maintain forms for mass printing in SAP Systems.As output medium SAP Smart Forms
support a printer, a fax, e-mail, or the Internet (by using the generated XML output).
https://www.guru99.com/smart-forms.html
ERP SD Invoice Lists
Skip to end of metadata

 Created by Christian Rosa, last modified on Aug 13, 2014

Go to start of metadata

Purpose

This article covers a simple example of Invoice List in SD-BIL area.

Overview

Invoice lists are mostly used to provide some benefits for payer when possible. Some benefits are the following:
 To be able to consolidate/print several invoices into one.
 Having billing date of invoices changed once it is consolidated. Customer may required submission of consolidated
invoices by date.

 Factory discount is applicable.

It is also beneficial to the seller while organizing the billing documents a invoices are grouped into one invoice list. It simplifies
the control once there is only one payment which means that accounting document of invoice list takes place of all its invoices'
account documents.

Depending on the payer's country the payer may pay tax for the discount provided. The condition type for factory discount is
RL00 while its tax is MW15 (optional).

Settings

There are some settings before creating Invoice List, here they are:
1. In Billing Document Types make sure that Invoice List Type (LR) is assigned to the invoice to group (E.g: F2).
2. Make sure that copy control make use of requirement 016 from F2 to LR ( VTFF transaction ).

3. Set a calendar for Invoicing List Dates ( XD00 transaction ) to the related customer/payer.

 
  

       4.      Set RL00 (statistical) in the pricing procedure, for example:

       5.       Set condition record for RL00 ( VK11 transaction ).

You may want to set also in pricing procedure the tax MW15 (optional) and also to determine LR00 (invoice list header) to create
printing papers output automatically.

 
 Invoice List Creation Steps

It is simple flow of SD transactions before creating Invoice List (transaction VF21), like VA01, VL01N and VF01.
1. Create more than one sales order for a same payer.
2. Creates respective delivery orders.

3. Create respectives invoices.

4. Now you create the invoice list (VF21).

       5.    Hit Execute button and check discount as per defined in condition records:

After hit save buttong notice that when you release the invoice list to account then accounting document has the final data.

 
           6.       Setting Output Type:

Standard program for LR00 will print the invoice list with each invoice data per page.

ERP SD Revenue Recognition

Description

Many companies require that revenues are posted according to a time period. This means that the revenues must be realized in
the posting period in which the service was carried out, and not in the posting period in which the billing document was set up.

For this purpose, create a message under the component SD-BIL-RR containing the following information:

Documentation

The latest version of the Revenue Recognition Best Practices document is attached to SAP-note 1172799.

Available methods
 Revenue recognition at the point of billing (standard method)
 Time-related revenue recognition (the revenues are realized between specific set dates)

 Service-related revenue recognition (the revenues are realized on the basis of a specific event, e.g. the goods issue for a
delivery)

 Credit/Debit memo request with reference to preceding document

 Service based revenue recognition, billing related (only for IS-M solution)

Customizing

For the setup of revenue recognition processes you have to customize:

 FI accounts and their settings
 SD item categories and their settings

 Revenue recognition category on item category level

 Account determination

The following accounts are needed for the representation of the revenue recognition process:
 Revenue account (recognized revenues)
 Receivables account (customer account)

 Revenues to be deferred (deferred revenue account or D/R account)

 Unbilled receivables (unbilled receivables account or U/R account)

Revenue recognition category on item category level

Transaction: OVEP

Set Revenue Recognition category for Item Categories:

Possible entries for the field “Rev. recognition” are:

Account determination

Transaction: VKOA

Assign G/L accounts for revenues and deferred revenues:

 
 G/L account no. (SAKN1): revenue account
 Provision acc. (SAKN2): D/R account

Transaction: OVUR
 Account for unbilled receivables (U/R account) has to be maintained depending on the reconciliation account and the associated
chart of accounts:
 NonBldRec.: U /R account

Description of Core Businesss Processes

Process 1: Standard Revenue Recognition at time of billing

Process 2: Time based with VF44 as first

Process 3: Time based with invoice as first

Process 4: Service based with VF44 as first

Process 8: Time based & billing related (‘D’)

Process 9 – time based / service based with VF44 as first 

Process 10 – time based / service based with VF44 as first

SAP-note 1172799. 
 Handling of revenue recognition data

Revenue realization processes

 Revenue recognition run (transaction VF44). With transaction VF44 the revenues are posted and financial accounting
documents are created.
 The posted revenues can be cancelled by using transaction VF46, e.g. if revenues have been realized in error.

 In certain cases - for example, when you change condition values - revenue lines of the related sales document have to
be updated. Transaction VF42 can be used to update revenue recognition data.

 Transaction VF45 shows deferred revenues, unbilled receivables, billed and realized amounts on the level of a sales
document item.

 The report of VF47 shows inconsistencies between the revenue recognition tables VBREVK, VBREVE and VBREVR and
the appropriate sales documents. Only development support may run it in update mode.

Se38 to edit the sap std program.

Exit type –

1-function exit –functional module exit – search- in CALL CUSTOMER.FUNCTION TO FIND FM –

OR TO FIND FOR TO STAUS – GET PACKAGE AND CHECK THIS IN SMOD

2-menu exit –

3-filed exit

4- screen exit

BOM – TABLE 1. MAST – FOR ATERIAL AND BOM NUMBER (TECHNICAL REPRSAENTATION OF THE TECHNICAL

2) STKO- BOM PLANT AND USAGES

3) STOP- BOM NUMBER AND COMPONENT

CUSTOMER MASTER TABLE .

GENRAL – KNA1, SALES – KNVV, PATNER –KNVP, TAX- KNVI, FINANCE – KNB1, VREDIT – KNKA,HIRARCHY –KNKH

DOC FLOW-VBFA

A billing document has to be archived, therefore you execute the check program S3VBRKPTS. This program checks billing
documents to see if they can be archived. The check program should be executed before the write program to ensure the
quality of the billing documents that are to be archived.

https://blogs.sap.com/2014/05/30/document-not-archivable-due-to-badi-add-on-archiving-check/

Third-party process overview

FollowRSS feedLike
71 Likes 113,279 Views 36 Comments 

In third-party process the delivery of the goods required by the customer is not done by sales organization where customer
orders. Instead, the request of the goods is forwarded to an external vendor who sends the material directly to the customer.

Here is what happens in third-party process:

1. Customer orders goods and a sales order is created in a sales organization

 2. Purchase requisition is created automatically when sales order is saved.
3. Purchase order is created at the vendor in the MM purchasing application (manually or automatically)
4. If the vendor does the outbound delivery to the customer, the goods receipt can be posted in the system
5. Invoice receipt is created (invoice from vendor)
6. Invoice to customer is created (order based invoice)

SALES ORDER

Third-party process is triggered when the sales order with third-party item is created. Depending on settings done in
customization third-party item categories can be automatically determined by the system (automatic third-party processing) or
they can be changed from standard item to third-party item category in sales order (manual third-party processing).

Sales order type used for third-party – OR (standard order)

Item category for third-party – TAS

Schedule line category for third-party – CS

Let’s look deeper into the settings in the system done for automatic and standard third-party process:

ITEM CATEGORY TAS:

Create PO Automatic indicator is not marked in TAS. ALES is an item category for third-party processing where this indicator is
marked.

ITEM CATEGORY DETERMINATION

Item category TAS will be determined automatically for standard order (OR) and item category group BANS (third-party item).
Item category group can be found in material master, Sales: Sales org.2 view.

SCHEDULE LINE CATEGORY CS

Data: Order type = NB, Item Category = 5 and Acct.AssgntCat  = X is the data for Purchase requisition. If it is filled like above
the purchasing requisition will be created automatically as standard purchasing requisition (NB), with item category S and
acc.assign cat X. The mapping of item category (from 5 to S) can be found in IMG:  MM->Purchasing->Define External
Representation of item categories. The definition of account assignment category can be found in IMG: MM->Purchasing-
>Account assignment->Maintain acc.***. Categories

settings for schedule line category CS -for third party sales, in the field Account Assignment category we assign X-all auxiliary
account assignment.
what is the purpose and reason for using account assignment category in third party and at what point of time this comes into
picture in third party sales process

Procurement against customer requirement will be booked against cost or expense account. So when creating PO, this account
assignment category is determination factor for respective G/L accounts in MM.
- Account assignment category will have general modification assigned. in MM account determinatoin OBYC settings-
Valuation group code(this needs to be confirmed) + General Modification + valuation class determines G/L account.
This is how G/L account will be displayed in PO - item level - account assignment tab.
To see the settings in account assignment category - check the help of the field & choose customization & observe in details.

SCHEDULE LINE CATEGORY DETERMINATION  

THIRD-PARTY PURCHASE REQUISITION

After saving sales order with item category TAS the purchase requisition is automatically created. In order to see the document,
go to: Environment -> Status overview and expand data for item, then expand data for purchase requisition as well:
Double click on the requisition number and you will be taken to the purchase requisition document. The other way is to go to
schedule line where you can find the purchase requisition number.

If third-party item has more than one schedule line with confirmed quantity > 0, then purchase requisition is created for each
schedule line.

It is wise to have the vendor determined in source of supply at this stage of the process (i.e. source list)

MANUAL PURCHASE ORDER

The purchase requisition needs to be converted into purchase order in MM (t-code me21n). The purchase order document type
is NB (standard order), item category S, that must be assigned to account. Thus account assignment category needs to be
given. In this example it is X (automatically taken during conversion from purchase requisition, as it was defined in item category
CS).

The definition of acct assignment category can be found in IMG: MM->Purchasing->Account assignment->Maintain acc.***.
categories:

Note: There is also a third-party account assignment category created in the system and its definition looks as follows:

The mapping of item categories: IMG:  MM->Purchasing->Define External Representation of item categories:

AUTOMATIC PURCHASE ORDER

As it was written before – the purchase requisition is created automatically when sales order is saved. It is possible to
automatize the next step, the creation of purchase order, as well. The ALE function is used for that purpose.  The indicator for
the automatic creation of purchase order is not set for TAS item category. However, there is a special item category – ALES
which can be used instead in third-party process. The indicator for the automatic creation of purchase order is marked in ALES
by default.

Prerequisites for the automatic creation of purchase order are as follows:

 The indicator automatic purchase order needs to be marked in item category definition (item category ALES has it by
default)
 Unique source of supply needs to exist for third-party item
 At least the document type for the purchase order must be assigned for Sales organization in customizing
under Enterprise structure->Definition->SD->Define, copy, delete, check sales organization

If all above prerequisites are set up correctly, purchase order will be created when sales order is saved. Then, it can be found in
document flow in sales order.

GOODS RECEIPT

Since during third-party processing goods are moved directly from the vendor to the customer, inventory management is not
affected by this event. However, if sales department would like to document and enter delivery to the customer in the system it
is possible depending on settings in customization. If account assignment category 1 is used in item category definition, goods
receipt is not possible, as the goods receipt indicator is not set for this account assignment cat. If account assignment category
X is used, goods receipt is possible.
The goods receipt posting (t-code migo) would have the following effects:

 The warehouse stock is not updated

 The goods receipt is posted directly to consumption and the consumption quantity is updated
 The order value is posted to a GR/IR clearing account for invoice verification purposes
 The goods receipt can be traced in the purchase order history

The goods receipt posting should happen when the vendor reports that outbound delivery was executed or customer confirms
that delivery arrives.

Since no flow of goods occurs in the enterprise, the goods receipt posting results in updates on value basis.

INVOICE RECEIPT

The invoice verification with reference to purchase order needs to be created when invoice from vendor arrives to enterprise (t-
code miro). The value and, if goods receipt was done earlier, the quantity are proposed by the system. When the incoming
invoice is posted following are updated:

 Purchase order history

 G/L  accounts
 The vendor account in sub ledger accounting, as well as the liabilities account (general ledger)

CUSTOMER BILLING DOCUMENT

Once invoice receipt has been entered, the customer can be billed as well (t-code vf01). Since an outbound delivery doesn’t
exist for the third-party the invoicing will be order based. In the item category TAS definition, the billing relevance indicator is set
to F by default. That means: relevant for order-related billing document: status according to invoice receipt quantity. That is, the
system allows invoicing the order only when vendor’s invoice has been processed in invoice verification.

The customer invoice is created for the quantity specified in the vendor invoice. The setting in the copy control for the third-party
item category from sales document to billing document specifies that the quantity from the invoice receipt is transferred to the
billing document instead of the order quantity (billing quantity indicator in copy control is F)

How to resolve "Document not relevant for billing" error message?

Check the detailed error log in VF01 screen. We may get more information on error.

Then, check have you completed the PGI for the delivery document or not.

Next, go to that Item Category functionality VOV7 and find if it is order or delivery related billing.

And after that go and check in the particular Sales order document type whether billing document types are maintained in the sales document
or not.

If every thing is correct go and find with copy controls

If it order related, go VTFA 

If it Delivery related, go VTFL and check in your document type combination is maintained or not, if they are maintained item category is
available or not.

After delivery while creating billing document system showing error that no billing document is generated for material no 395.  So
how I can solve this issue.

Check if Item Category is checked for Billing or not.

How to schedule billing to be run automatically?

You can create individual Billing documents in VF04, with out any saving of each and every billing document.
Select all the deliveries which you want to create billing documents, using Cntr Button, and click on individual billing. Then all the deliveries
will go for billing individually in a single run. And you can also see all the billing documents numbers, which are created. No need to select
single delivery each time.

If you want to do a batch job for billing, proceed for the following process

1. goto VF04, in the selection screen Delivery document range, for which you want to create billing documents e.g., in SD Document field,
give delivery 1 to 10.

2.Now Click on GOTO -> Variant -> Save as Variant, then it will take you to another screen, give the variant name, e.g., test, and save it.

3. goto SM36, this is used to do batch job, if you dont know any thing also, you can do the entire process, using JOB WIZARD, click on Job
Wizard which is on the screen.

4. It will take you to different steps, just you need to give your variant name, (in job name field) (in the first screen) the continue for further
steps, In the ABAP Progamme Name give SDBILLDL, (this is the programme used to create billing documents) continue to give the
specified time which you want to run this batch job, like immediate, after an hour, or a specific day like so.

Second Scenario

If accounting documents gets generated and you use VF11 to Cancel the invoice, then automatically the posting document gets reversed and
separate number will be assigned for those documents. This you can see in the document flow. Check with FI Consultant.

Please Check this :

SPRO--->Sales and Distribution-->Billing Documents-->Define Billing Types

Select Billing type S1.

Then check Posting Block, it should be unchecked.

Check whether for the S1 billing document type Posting block has been checked or not. If it has been checked then uncheck it and secondly
also check in the F2 billing document type whether S1 cancellation billing document type has been assigned or not. 

Finally check whether the billing document which you were cancelling that billing document generated accounting document or not.  If it has
not generated the accounting document then check the settings in OBA7 k

In SAP billing process; I am facing the problem with the exchange rate. As the rates picked in the sales order as default exchange rates
maintained for the day; if the sales order is MTO and goods will dispatched after 2 months and within these 2 month the exchange rate got
floated by a large amount and during the billing with VF01 t-code; the exchange rate will be something else; and I can’t change it at that
instance also. 

The billing document will be posted to the accounting after getting the money from the customer and the exchange rate will become
something else at this moment also; and make a large difference of amount at this instance. Is there is any provision in sap system so that I
can change the exchange rate in the billing document and with this same exchange rate I can post the entries in accounting also. It will solve
the problem as it will give me the billing amount in exact LC amount also.

Solution: 

You can have the same exchange rate (OB08) in sales order to be in billing document:

In Copy control VTFL at item category level -> PricingExchRate type to 'A'Copy from sales order

Now, if you want that same exchange rate to be in Accounting document in Sales Order GOTO -> HEADER -> ACCOUNTING there one
field is there 'Exch.rate-acct.' enter the exchange rate there manually, which will post to accounting.

  
Proforma invoice is exactly the same as to Invoice.  The difference is Proforma invoice is need not to be paid and system does not
transfer data to FI(Financial accounting).  No statistical data is created on the basis of Proforma invoice.  
  
F8 is delivery related proforma invoice and you can create proforma invoice for same delivery you as many as you like. Goods issue is not
require to create Proforma invoice.  
  
In case of sample orders - (delivery free of charge- order type FD) - invoice is not generated.  In VOV8 - billing is not proposed.  Hence
system does not generate invoice.  In Sample order/delivery account receivable does not increase but cost of sample order is added to
sales promotion account or client suggested accounts.  
  
- Another requirement to have proforma while Stock Transport Order.  
    
  

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

Gap means small cracks. In SAP world or in Information Technology world, gap analysis is the study of the differences between two
different information systems or applications (ex; existing system or legacy system with Client and new is SAP), often for the purpose of
determining how to get from one state to a new state. A gap is sometimes spoken of as "the space between where we are and where we
want to be."
 
Gap Analysis is undertaken as a means of bridging that space. Actual Gap Analysis is time consuming and it plays vital role in Business
Blueprint [AS IS Process] stage.
 
A through Gap Analysis will identify the gaps between how the business operates and its needs against what the package can can't do. For
each gap there will be one of three outcomes which must be recorded and auctioned,
 
1. GAP must be closed and customized software can be developed
2. GAP must be closed but software cannot be written therefore a workaround is required
3. GAP does not need to be closed.
 
Actual gap analysis is time consuming and it plays vital role in blue print stage.
 
Cut Over Plans
Detailed plans need to be developed for cutting over from the old system(s) to the new. Parallel runs of what will happen over the
conversion period using test data, convert and watch for a period after wards to ensure nothing unexpected happens.
 
Train Users
Well trained users will support and defend the system on site. Unsupportive users will continually undermine the system and eventually it
will be replaced. Therefore the more effort you put into helping the users master the system early the better. Fit gap means, before
implementing the SAP all the business data is in the form of documents, we cannot keep this data as is in the SAP. There should be a gap.
So by filling this gap, we make configuration with the help of these documents. This is called as fit gap analysis.
Cut over activities are mainly in final preparation before go live
 
i). Legacy system shutdown and
ii). All finished goods uploaded from legacy system to sap
iii). And linking old number ranges to new number ranges
iv). Uploading all transport requests
v). End user training
CUT OVER STRATEGY:
Cutover strategy depends upon how the organizations design their data load strategies. Normally, you decide the sequence of Data loads
for Configuration settings, Master data, Transaction data which follows whom and then you make a copy of the system as a Production
system a day before and after checking the successful data loads, you go-live 100% or partial again depending upon organizational setup
and policies.
 
Cutover planning is highly site specific. There's no thumb rule. The stock data as on the date of going live should be correctly entered. But
stock being a highly dynamic quantity, the strategy for loading should be crystal clear. Then you have to load all the back dated transaction
on the stock. Some stock comes into your plant/storage location as return and some stock is actually delivered to your customer through
sales orders of various kinds.
 
As example, in simple words for MDM (master data maintenance) it means that after cutover - all data will be used of MDM and not legacy
systems. For central master data scenario; Data before cutover date will be maintained in all systems and after cutover date, it will be
maintained in MDM only.
 
Data can be uploaded using BDC programs, LSMW for master data and CATT is also being used.
 
Hope this will helps you and Please Reward If Really Helpful,
  

 
1. VA01 - Sales Order or earlier - No Entries
 
2. VL01N - Create Delivery - No Entry
 
3. VL02N - PGI - COGS Dr and Stock Cr
 
4. Invoice
 
Customer Dr
Discount Dr
  Sales Revenue cr
  VAT Cr
  Excise Cr (If applicable)
Goods Delivery to Customer - PGI (VL01N) 
(Outbound Delivery)                                                      
                                       
                      Dr. Cost of Goods Sold A/c     
                     Cr. Inventory A/c    
            
            
Raising of Sales Invoices (VF01)  
       Dr. Customer A/c (Accounts Receivable)    
       Cr. Sales A/c    
       Cr. CENVAT Output Clearing A/c     
       Cr. VAT Payable A/c     
       Cr. Pro Fright O/w Claim A/c                  If any. Collecting from Customer   
       Cr. Pro Export Exp A/c                           If any. Not Collecting from Customer.    
       Dr. Freight Outward-XP A/c                   Freight Outward - XP A/c is Expense A/c    
       Cr. Pro Export Exp A/c                          If any. Not Collecting from Customer.   
       Dr. Commissn On XP Sales A/c           Commissn On XP Sales A/c is Expense A/c   
            
            
Raising of Excise Invoices (J1IIN)  
      Dr. CENVAT Output Clearing A/c     
      Cr. Excise BED Payable A/c    
      Cr. Excise ECS Payable A/c    
      Cr. Excise SHE Payable A/c    
            
            
Accounting Entry in case of Sale of Scrap (VF01)  
       Dr. Customer A/c (Accounts Receivable)    
      Cr. Income From Scrap Sale A/c     
      Cr. CENVAT Output Clearing A/c     
      Cr. VAT Payable A/c     
      Cr. TCS - Scrap Sales     
            
            
Raising of Excise Invoices for Scrap (J1IIN)
       Dr. CENVAT Output Clearing A/c     
      Cr. Excise BED Payable A/c    
      Cr. Excise ECS Payable A/c    
      Cr. Excise SHE Payable A/c    
            
            
Receipt of Amount from Customer(F-28)  
       Dr. Bank Account A/c     
      Cr. Customer A/c (Accounts Receivable)    
            
            
Receipt of Amount from Foreign Customer (F-28)  
       Dr. Bank Account A/c     
      Cr. Customer A/c (Accounts Receivable)     
      Dr/Cr Exchange Fluctuation A/c    
Here is the list of all determination rules in SD for quick reference.

Sl.no Determination Object Rules for determination

1 Sales document Sales Area 

+ Document Type

2 Item category determination for Sales document Document type 

+ Item category Group 
+ Usage 
+ High level Item Category 
Sl.no Determination Object Rules for determination

3 Schedule line category determination Item category of the corresponding item 

+ MRP type of the Material 

4 Delivery document determination Delivery document default type attached to  Sales document type

5 Item category determination for Delivery Copy form Sales document 

document or 
Delivery Document type 
+ Item category Group 
+ Usage 
+ High level Item Category

6 Shipping Determination Delivery Plant 

+ Shipping condition (Customer Master - Sold-to Party) 
+ Loading group(Matrial Master)

7 Route determination Departure zone of the shipping pt(Customizing) 

+ shipping condition(SP) 
+ Transport group(MM) 
+ Transportation zone of the Ship to party(General Data)

8 Storage location determination Shipping point 

+ Delivery plant 
+ storage condition

9 Picking determination On bases of MALA rule  

Delivery Plant 
+ Loading Group 
+ Storage condition(MM) 
(storage rule also assignment to Delivery type)

10 Packing determination Package usage

11 POD This object use for confirmation of delivery, based on which billing
document can create

12 Billing document determination Sales document type is maintained as default type 

For Billing plan, Billing Type maintain under Billing Plan Type of
Maintain Date Category for Billing Plan Type

13 Account determination Chart of Accounts 

+ Sales Org 
+ Customer Account grp (Customer Master - Payer) 
+ Material Account grp (Material Master) 
+ Account key

14 Business area determination Plant/Valutaion Area 

OR 
Sales area 
OR 
Item division + Plant 

15 Company code determination Sales organization uniquely attached to Company code

16 Partner determination At -Account group level, sales document header level, item level, sales
document delivery level, Shipment level, Billing document level and item
level

17 Delivery Plant determination The system will determine Plant details at following in given sequence 
Customer - Material info record 
From customer master Ship-to Party 
From Material Master

18 Output determination Output determination at Sales document level, Delivery level, Billing
Sl.no Determination Object Rules for determination

level

19 Price determination Pricing procedure 

Sales Area
+ Document Pricing Procedure indicator from Sale/Billing Document
type 
+ Pricing Pricing Procedure indicator from Customer Master (Sold-to
Party)

20 Text determination 1)Customer Material Information Record 

2) Customer Master (General text, Accounting text, Sales text) 
3) Material master text (Sales text or PO text) 

21 Warehouse determination Ware house number 

+ Plant 
+ Storage location

22 Lean Warehouse determination Lean ware house activate, 

Plant 
+ Storage Location 
+ Ware house number

23 Tax determination Destination Country of Ship-to Party 

+ Departure Country of Shipping Point 
+ Tax Classification for Customer from Customer Master 
+ Tax Classification for Material Master

24 Routing determination Shipping point 

+ Delivery plant 
+ Loading condition 
+ Shipping condition

25 Material determination Create condition record 

Maintain Customer Material record

26 Product substitute Create condition record

27 Product Exclusion Create condition record(Not to sale any particular product)

28 Product listing Create condition record (Sale of one particular product)

29 Credit check Credit check at Sales document level OR at Delivery OR at Good issue
Risk group at Sales document level and Risk category from Customer
Master, Item category credit check should be activate

30 Incomplete log Incomplete log assign to Status group, which is assign to Sales document,
Item category or Schedule line level

31 Rebate condition setup customer master billing info checked, Sales organization activate, Billing
document activate

How system determines as special stock to normal stock in

special business processes
Special stock is determined from Item category. For e.g. In Consignment process, while we issuing the stock to customer, it
consider special stock as 'W' which determines from item category KEN. 

What is Delivery group and what is its purpose in sap sd

If you want to combine a number of items in a sales document so that they are delivered together, you can create a delivery
group.
If an item has more than one schedule line with confirmed quantities (for example, after an availability check) the system copies
the date of the latest schedule line for this item and displays it on the delivery group overview screen.
When forming delivery groups, the system deletes the earlier schedule lines and copies their confirmed quantities into the latest
schedule line.
If a complete delivery has not been requested, as soon as all the items for the bill of material are available, the system
generates a correlated schedule line. This allows you to make a partial delivery on the first date on which all the items in the bill
of material become available.
In other words, the first day on which all items in the bill of material are available, the system issues a confirmed quantity.
Prerequisites
 
For correlated schedule lines in bills of material (BOMs) in delivery groups, there are certain prerequisites for the delivery group.
 
These are as follows:
 
The delivery group may only contain one bill of material
It cannot contain any fixed quantities
It cannot contain any items that have partial delivery indicator C (one-time delivery)
It cannot contain any partially-delivered items
It can only contain items that can be at least partially delivered
It can only contain items that have a maximum of one requested schedule line
 
In Customizing for item categories, you can control that the system should generate correlated schedule lines for the delivery
group. You can do this by selecting A in the Generate delivery group field for the item category in the bill of material main item.

postings do not happen when:

a. we have not assigned the correct GL accounts

b. we have not assigned the Account keys properly
c. we have automatic account assignments happening.

We need to check and correct them... 

Make to Order VS make to Stock

Process in a Made to Order  Made to Stock

Sequence

     

Definition When you specially produce and deliver a product for a When you produce according to a periodic forecasted
customer's order, it is called "Made to order" Production. demand and sell the product to any incoming customer
For example Production of Designer Jewelry, Production who wants to buy them, it is called "Made to Stock"
of Areoplanes, production of Special type of steel, High Production. Example Mass Steel Production,  
end instruments and vechiles etc., 

Demand Form Customer Places a Sales order. A Sales order for the When you produce against a Periodic forecasted demand
demand is created in SAP.  it is called Made to stock production.  

Sales order in some cases is referenced from a previous You can enter this forecasted demand in a tool in SAP
enquiry or quotation of sales created.  called Planned independent requirements in the system. 

Planned independent requrirements can also be

derived/copied from Sales & Operation Planning system
which contains demand from previous periodic Sales
figures from the sales areas or Sales organizations or
sales area or sales offices or plants or various
combination of this (as per your requriements). These
previous period figure for a product or a product group
can be extrapolated to create the demand for the future
periods.    
 

SAP Production Every Material that is ordered should have a strategy that Every Material that is Produced with a forecasted
Strategy is - Made to order Strategy = 20, set in the Material demand should have a strategy that is - Made to stock
Master  MRP 3 View, Strategy Group Field.  Strategy = 10, set in the Material Master MRP 3 View,
Strategy Group Field. 
Strategy 20 is used for Made to order scenario, in which
case the production is tagged with the customer order.  Strategy 10 is used for Made to stock scenario, in which
case the production is not tagged with the customer
You should also set the Individual and collective order. 
Indicator in MRP 4 to = "1" - Individual requriement
which specifies that this is an individual requirement not You should also set the Individual and collective
 to be clubbed and produced individually for a given Indicator in MRP 4 to = "2" - Collective requriement or
customer order.  an field value which "Blank" - Individual and collective. 

     

Transfer of Demand is Pushed to SAP MRP Tool  Periodic demand is pushed to SAP MRP Tool
Demand to MRP

     

MRP Net MRP For its planning calculates the Net requirement MRP Evaluates the Planned Periodic Demand for the
Requirement planning  Material and while doing this it checks for availability
Planning for the of the Materials in stock and computes the shortage
header Materials MRP analyses and evaluates the Customer Demand for quantities.
the Ordered Material and while doing this it does
not check for availability of the Materials in stock and MRP creates a Planned order for the shortage quantities
considers it as not available at the time of creating of this periodic demand. 
procurement proposals in MRP.
To get the Shortage Quantities - The system thereby
MRP Creates a Planned order for the total quantity of the compares available warehouse stock or the scheduled
customer order.  receipts from Purchasing and Production with planned
independent requirements, material reservations and
incoming sales orders. In the case of a material shortage,
that is, if the available stock (including firmed receipts)
is smaller than the quantity required, the system creates
procurement proposals. 

MRP Net After creating planned orders for the header material, if a After creating planned orders for the header material, if a
Requirement certain dependent requirement or component has a certain dependent requirement or component has a
Planning for the procurement type - "In-House", then:  procurement type - "In-House", then: 
Dependent
Requirements MRP then explodes the Bill of materials for the header MRP then explodes the Bill of materials for the header
Material and plans the dependent requirements by Material and plans the dependent requirements by
evaluating the shortage quantities (Requirement qty - evaluating the shortage quantities (Requirement qty -
Available qty) and dates of the components required in Available qty) and dates of the components required in
production as per the BOM. production as per the BOM.

While creating the Procurement Proposals for the While creating the Procurement Proposals for the
components, it takes in to considerations the Lot sizing components, it takes in to considerations the Lot sizing
procedures, special procurements, Quota arrangements.  procedures, special procurements, Quota arrangements.

MRP Planned After creating planned orders for the header material, if a After creating planned orders for the header material, if a
order for certain dependent requirement or component has a certain dependent requirement or component has a
Externally procurement type - "Externally Procured", then: procurement type - "Externally Procured", then:
procured demands
MRP Creates Planned orders or purchase requisitions for MRP Creates Planned orders or purchase requisitions for
the externally procured dependent requirement, only for the externally procured dependent requirement, only for
the shortage quantities (Requirement qty - Available the shortage quantities (Requirement qty - Available
qty).  qty). 

While creating the Procurement Proposals for the While creating the Procurement Proposals for the
components, it takes in to considerations the Lot sizing components, it takes in to considerations the Lot sizing
procedures, special procurements, Quota arrangements.  procedures, special procurements, Quota arrangements.

The procurement proposal is also scheduled which The procurement proposal is also scheduled which
means that, for materials procured externally, the means that, for materials procured externally, the
delivery and release dates are determined, and for delivery and release dates are determined, and for
materials produced in-house, the production dates are materials produced in-house, the production dates are
calculated.  calculated. 

MRP Explosion of After Calculating the Proposal quantities for Inhouse After Calculating the Proposal quantities for Inhouse
Routing or Procuded Materials, the System explodes the Routing Procuded Materials, the System explodes the Routing
Receipes or Recipes (if MRP is set at Lead time scheduling) which or Recipes (if MRP is set at Lead time scheduling) which
helps in correctly evaluating the basic order start date helps in correctly evaluating the basic order start date
and basic order end date. MRP system calculates the and basic order end date. MRP system calculates the
operation execution dates and inturn the order execution operation execution dates and inturn the order execution
time from a forward start date or from a backward end time from a forward start date or from a backward end
date provided (normally set at backward scheduling in date provided (normally set at backward scheduling in
Scheculing Parameters customizing). Material floats and Scheculing Parameters customizing). Material floats and
operation floats (buffers) are taken into account while operation floats (buffers) are taken into account while
deriving the dates.  deriving the dates. 

If MRP is set at Basic Scheduling - Then the basic start If MRP is set at Basic Scheduling - Then the basic start
date and end date is calculated using the flat Material date and end date is calculated using the flat Material
Master Lead times.  Master Lead times. 

Conversion of Once the Planned orders and Purchase requisitions are Once the Planned orders and Purchase requisitions are
Planned orders created, they are converted to Production orders or created, they are converted to Production orders or
Process order/Purchase orders.    Process order/Purchase orders.   

Production Supervisors or Planners convert the Production Supervisors or Planners convert the

planned orders to Production orders or Process orders. planned orders to Production orders or Process orders.

Purchasers would convert the Planned orders or Purchasers would convert the Planned orders or
Purchase requisitions to Purchase orders.  Purchase requisitions to Purchase orders. 

     

Production order Production order adopts the planned order information Production order adopts the planned order information
creation such as Quantities, Basic Start Date, Basic Finish Dates, such as Quantities, Basic Start Date, Basic Finish Dates,
operation dates, component quantities.  operation dates, component quantities. 

Production Orders are created and released on the shop Production Orders are created and released on the shop
floor. Before saving and releasing the order, the floor. Before saving and releasing the order, the
production scheduler or planner can change the production scheduler or planner can change the
quantities, dates and component quantities, operation quantities, dates and component quantities, operation
scheduling information. scheduling information. 

The Production order which is created has a link to the The Production order has no link to any customer atall. 
customer order. 

Purchase order Purchase orders which are created through the Purchase orders which are created through the
creation conversion process are released and sent to the Vendors.  conversion process are released and sent to the Vendors. 

Production order Once the Production orders are Released, they are Once the Production orders are Released, they are
Shop Floor thrown on the shop floor for Production: thrown on the shop floor for Production:
Execution
a) Every Operation confirms the production against each a) Every Operation confirms the production against each
order once they produce the required quantities of that order once they produce the required quantities of that
order.  order. 

b) Once all the operations are confirmed for all the b) Once all the operations are confirmed for all the
quantities, the production order gets the status "CNF" - quantities, the production order gets the status "CNF" -
Completely confirmed. Completely confirmed.
 
 

Goods issue to the At the time of confirmation or Parellel to the At the time of confirmation or Parellel to the
Production order  Confirmation process or after the confirmation process, Confirmation process or after the confirmation process,
the supervisor/respective operator issues the components the supervisor/respective operator issues the components
to the production order.  to the production order. 
 The Operator or Supervisor gets a list of all the The Operator or Supervisor gets a list of all the
components that are required for production through a components that are required for production through a
reservation list created in SAP (a reservation list is reservation list created in SAP (a reservation list is
created for every order at the time of order creation). created for every order at the time of order creation).

Goods Receipt The Products which are fully manufactured against the The Products which are fully manufactured against the
from the order are received to the "Finished Goods Storage order are received to the "Finished Goods Storage
Production order Location" through a SAP Material Movement called Location" through a SAP Material Movement called
"Goods receipt against the Production order - Movement "Goods receipt against the Production order - Movement
type 101". type 101".

The Received Materials in a MTO scenario have a tag of

the customer order and customer against them and they
cannot be issued or delivered to any other customer
order. 

Order Settlement  Orders which are received in to stock are settled by the Orders which are received in to stock are settled by the
finance team.  finance team.

Status Profiles in SAP

You can create Status profiles for documents or transactions and then set up authorizations for certain activities. The result is
we can enable select personnel as authorized to carry out the activities blocked by status profiles.

Create Status Profile

1. Create status profile in general status management as shown below (BS02) or  via IMG --> Sales & Distribution à 
Sales à Sales documents à Define & Assign Status Profile:

 
 
2. Go to Define Status Profiles. Choose New Entries and enter code & description for your status profile:
 
 
3. Choose object types for status profile. Eg: Sales order header or sales order item for which the status profile is to be applied
to.

 
 
4. Enter your status say for price check, specify lowest status number (which will render any statuses lower than the lowest
number specified, inactive) and highest status number (which will decide the upper limit of status numbers which may be
activated if this status is active).
Set initial indicator for your required status, generally system sets initial automatically for the first status.
Specify authorization key in authorization code field. (See below for creation of authorization key).
 
5. Double click on your status (PRC) and choose transaction control. Select the activities which are to be checked with this
status.
For eg: confirmation of order, creation subsequent documents like delivery & billing documents is forbidden.
  Save status profile.

 
6. Assign status profile to document types (VOV8) & item categories (VOV7) as required.
 
 
 
 
Authorization Key
Enter authorization key & description in BS52 and save. Authorization key is assigned to status profile and is used to create
authorization for user role.
 

 
Users and Authorizations
Authorizations to perform a particular action in the R/3 system can be created (and included in required user roles) via
authorizationobjects.  Create authorization for authorization object B_USERSTAT
 
1. Go to IMG à Cross-Application components àDocument Management à Control Data àMaintain Role or use transaction
PFCG and add authorization for status profile to required user role.

 
2. Choose change user role and go to menu tab. Add transaction (say VA02) for which you want to give authorization to change
user status for sales order header or item
  
 
3. Go to Authorization tab and choose ‘change authorization data’.  Maintain status management for authorization object
B_USERSTAT, specify object category as chosen (VBK or VBP), authorization key, and status profile. Generate authorization.
 
4. Go to user tab and enter user ids which are to have role with authorization for status profile and save.

 
Save User Role.
 
 
Test Status Profile
 
1. Create sales order and check status (sales document header à status tab). Status is blocked and user status is PRC
(from status profile).

Click on object status button (Sales document headerà status tab à object status) and both statuses from status profile can be
seen.

 
2. Try to deliver the blocked sales order to get below error:
 
3. A user with authorization (in this case sdconsultant) can change status to 'released' after checking sales order price.
After selecting ZRE, overall blkd status changed to ‘Not blocked’ as under:

 
Now, delivery and subsequent documents can be created for released sales order.
 
FI-SD Integration: The integration is done in T-code VKOA
 
  1. Sales Order Created 
 
        -No Entry-
 
  2. PGI done (Goods issue)
 
      Cost of Goods Sold     Dr (Configured in OBYC GBB T-Key)
           To Inventory Account
 
  3. Billing document released to Accounting
 
        Customer Account Dr.
              To Sales Revenue Account (ERL T-key in Pricing procedure)
 
  Note : The GL account is assigned to this ERL in VKOA
 
  4. Payment Received
 
        Bank Clearing A/c Dr
                       Customer A/c Cr. 
 
ALSO:
 
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
 
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.
 
Incompletion log configuration                                          Author- Dattatreya N R
 
The incompletion log is a important and simple concept related to SAP Sales and distribution.
The incompletion log reminds you when data important for further processing is missing from the sales document
 
We can create incompletion logs for the following:
·         Sales document header data
·         Sales document item data
·         Sales document schedule line data
·         Sales activity data
·         Partner data in sales documents, deliveries & sales activities
·         Delivery header data
·         Delivery item data
 
Configuration steps:
1)      We define status group
2)      Assign this group to different fields maintained in incompletion procedure
3)      Assign this in completion procedure to sales document type
 
 
1)     Defining status groups:
You can define status group for your requirement to define status of incomplete documents and it is to be assigned in
incompleteness procedure
SPRO | IMG | SD | Basic function | Log of incomplete items | Define status group

 
Suppose if we consider status group 03. Check boxes for General, billing doc and goods movement are checked. This means
that when general information such as PO number, document date OR billing related information such as terms of payment OR
goods movement related data such as quantity picked are missing in corresponding sales documents system will give a
message to user saying that document is partially incomplete or incomplete.
Then user has to fill the data to make the document status as complete. We can restrict further processing of incomplete status
either not allowing the user to save the incomplete document or allowing the document to save but further processing will not be
possible.
 
Ex., We can say that if terms of payment is  not mentioned in sales order then user cannot save sales order. Or user can save
the document but delivery cannot be created without payment terms.
2)      Defining incompletion procedures:
SPRO | IMG | SD | Basic functions | Log of incompletion items | Define incompleteness Procedures
 
Here we will check the fields maintained for incompletion procedure 11
 
Note: We have assigned Incompletion procedure 11 to sales order.

 
In the above screen we can see that we have maintained PO number field to be in incompletion procedure and also checked the
Warning checkbox. This means whenever we create a sales order the system will check whether PO number is filled in sales
order or not, else it will display a warning message while saving order.
 
3)      Assigning incompletion procedure:
SPRO | IMG | SD | Basic functions | Log of incompletion items | Assign incompleteness Procedures
We can assign incompletion procedure to following documents
 
We have assigned incompletion procedure number 11 to sales order type OR. So it will check for all the fields maintained in this
procedure (Shown in above screen) while saving a sales order.

what is condition category, where its maintened

CONDITION CATEGORY is the classificaion of CONDITION TYPE such as  FREIGHT, TAX, PRICE, DISCOUNT.

Whether it is a Deemed Exports or Exports under Bond or Domestic sales, the Excise Transaction Type for all these is DLFC.
Excise Transaction type DIEX  for Debit Entries while issuing Credit Note(J1IH Addition Excise)
 
Excsie Transaction type MRDY for Credit entries while issuing Debit Note.(j1ih other adjustment)

OTHR would be for Debit Note and Credit Note.

 For open sales order in sap sd -- VA05/ VA05N; its better to use Report: VL10C
Open PO –vl10b
VL10A
VL10C
 
also check in table VBBE for open quantities

VF04 - Process Billing due list

VL04 - Process Delivery Due ist
VL06F - General Deliveries list - outbound deliveries

Define Common Distribution Channels

You can use this menu item to define distribution channels which have common master data. The allocation is valid within a
sales organization.

Example

You can, for example, create customer master data for distribution channel "01" and define it so that it is valid for distribution
channels "02" and "03".

Note

The master data shared by several distribution channels applies to conditions and customer and material master data.

This helps you minimize the cost of creating and maintaining the master data.

You can also update statistics for each distribution channel and division without creating the master data for the different sub-
areas of the organization.

Activities
Define the distribution channel from which master data is to be copied into other distribution channels.

By pricing group we cab make exise zero for the customer

alv

T-CODE OMJJ-- for total movement types in SAP .

561 - Receipt per initial entry of stock balances into unrestricted use.
601- goods issue : delivery
645 - Inter company replenishment etc.

Item Category Group determines the type of material i.e. 

whether it is a normal item "NORM" or a third party 
item "BANS" 
Gap Analysis :
The client wants to configure in such a way that while
performing material determination he wants to swap the
materials by customers description -given in customer
material information record (cmir), which is not a
functionality of SAP .

For this you will be creating the field in the field catelog
for creating material determination table with the help of
Userexits.(ABAP cosultant).
this is an example ,when u do an implemention project for a
client lot of gaps will come and u have to give solution for
that.
n the present project client wanted to have pricing on the
basis of shipping point.

PRD support issue

Shipping condition not changeable in order

Material description will not changed-exit
Incoterm ship to party –exit
Foc-
I want to give additional discount for those customers who have surplus in their credit limit...If a customer is facing deficit then that
additional discount should not come in to picture. How can I overcome this

FD32-- Payment History.

There you have columns Total (with cash Disc) and Total (w/o cash disc).

This shold take care of your requirement. 

Regarding automatic picking

Check here SPRO > LE > Shipping > Picking > Define Relevant Item Categories

If Customer credit limit exceeds it's blocked for order i don't want send output to that customer how you configured?
In nace
requirement 2 send output for order confirmation
requirement 9 do not send output if credit limit exceeds
requirement 20,21 if order is not confirmed do not send output 

Re: Creating Delivery Without Sales Order

-T code VL01NO
s for creating delivery without any order reference.

Default delivery block

Specifies a delivery block that the system applies automatically during processing.

Use

You can specify a delivery block for any of the following:

 Sales document type

 Schedule line category

 Delivery type
  Shipping activity, such as picking and goods issue

Example

You can specify a delivery block, for example, for all free of charge deliveries. These documents then have to be approved
before further processing can take place.

Copy control
What is the difference between schedule line in sales order and scheduling agreement?
Schedule line in sales order confirms delivery Quantity And deliver dates.
Scheduling agreement is an agreement between company and customer for supplying of goods of particular quantity within a
specific validity period and with predefined delivery dates. 

1.Payer
2.Payment terms
3.Destination country
4.Actual GI date
5.Incoterms
6.Billing date and billing due date
7.Billing doc type
8.Foreign data trade
9. Sold to party
 
If these are different in sales orders or delivery documents the invoice will split
 
These are the controlling factors or creteria for invoice split and you can see in split analysis
 
If all these being the same then in VBRK/VBPP fields if you choose 001 in VTFL the invoices can be combined
that is multiple deliveries into single billing document
 1) - Schedule agreements allow you to have 2 different sets of schedule lines (VBEP-ABART). Standard SAP you should have
two sets of tabs - of schedule lines. One Forecast & the other JIT. Forecast forwards the schedule lines to planning (seen in
MD04) and JIT passes them to shipping (VL10). They can be identical or different. Typically these are used for component
supplier customers (namely Automotive). The customer will provide you 4-10 weekly buckets (usually a
Monday date) of future forecast qtys. Also send you 1-2 weeks of individual FIRM ship dates - which are entered on the JIT. It
comes down to the customer not knowing exactly what they need next week, but they don't want to suprise you with a large
order qty, where your lead times are 5+ days. The forecasted qtys they sent last week should account for this.
 
(2) Cumulative Quantities are tracked and influence how the schedule agreement passes requirements to both forecasting and
shipping. These qtys are sometimes requested by the customer on ASNs. Cumulative qtys reset at year end unless you've got a
customer calendar or you've modified standard SAP userexits to not reset.
 
Schedule agreements are very nice when the customer sends EDI data (830s = forecast or 862s = JITs). Outside of that they
can really cause trouble regarding daily maintenance, missing requirements, *** qty corrections, year end processing, etc.
One alternative would be to use customer independent requirements - entering the weekly, monthly forecasting qtys and
entering standard sales orders (with or without multiple schedule lines) to represent the true firm qtys.
chedule line Agreement :
Use the T.code VA31 (and choose Scheduleline agreement) : This agreement lets you to predetermine scheduling of different
materials with in a given period of time (This is same like the other contracts).
 
First enter the material with quantity say for example Material 1 Qty: 40, go to Edit from the menu >> Item >> Schedule line
 
There select within the time period defined two dates, say for example on 12: 01: 2005 20 quantity and on 13: 01: 2005 another
20 (The qty has to be same as the one in the sales order) .
 
Once this is done you have created a schedule line agreement.
 
Call this agreement in your sales order (with reference) and use them.
 
Note: You will be able to deliver only 20 qty on the 12th and 20 qty on the 13th, even though the sales order is for qty 40

Check copying control for billing.

Say, if you are looking this in order related billing, then use TCode VTFA.
In header of copying control, for your desired docs
source: Sales Order - OR
target: Billing Doc - F1
you can use "Reference number / Assignment Number" field to send info related to E - Current billing document number to
accounting document.
Similarly, you can have this mend for transferring
 Purchase order number 
 Sales order number
 Delivery number
 External delivery number
 External delivery no. if available, otherwise delivery no.
to accounting doc from the transaction.
 
Replenishment lead time (RLT): is the time taken for the material to become available either internally (in house production) or
externally (from a vendor). The most important things to consider during an external procurement are purchasing and MRP 2
(procurement) views of MMR where the processing time for purchasing, planned delivery time and goods receipt processing
time are taken into account. On the other hand internal procurement is based on in house production time (MRP 2 view) goods
receipt processing time or alternatively RLT time, which is found on MRP 3 view.
 
RLT (Replenishment Lead Time) is the time taken for the material to become available. RLT is only used when doing an ATP
check (Available To Promise). The value of RLT for a material is specified on material master record.
 
There are three types of availability checks –
Check on basis of ATP quantities.
Check against product allocation.
Check against planning.
Configuring Availability check through Checking Groups –
1. The checking group + checking rule determine how the availability check is to be performed.
2. The checking group determines whether and how the system checks the stock availability and generates requirements for
material planning. The checking group defines what type of requirements will be passed on i.e. summarized requirements
(daily/weekly) or individual requirements for each sales order.
3. The checking rule applies to how the availability check is to be carried out at the transaction level. Note that you must define
checking rules for each individual application such as for production orders for example. In Sales and Distribution, the checking
rule is specified internally within the system and cannot be changed.
4. The checking rule, in conjunction with the checking group, determines the scope of the availability check for every business
operation; that is, which stocks, receipts and issues are to be included in the availability check and whether the check is to be
carried out with or without the replenishment lead time.
5. Briefly explaining the above – checking group determines which type of requirement to be passed on to MRP whether it be
individual or summarized and checking rule which is at the transaction level and can be configured independently for each
application module, determines which stocks, receipts and issues to be taken into account. For performing an availability check
checking group has to work in conjunction with checking rule.
6. Advantages of individual processing over summarized processing –
Backorder processing is possible.
You can access (MD04) order, line and schedule line individually which gives a greater control on available stock and
requirements placed on stock.
The system automatically uses individual requirements in case of special stock items.
7. Required data for the Availability check to be carried out –
The Availability check must be switched on at the requirement class level.
The Availability check must be set at the schedule line level.
A requirements type must exist by which the requirements class can be found.
A plant must be defined in the sales order for each schedule line item (in other words plant must be defined for every material in
MMR).
A checking group must be defined in the material master record in the MRP3 screen in the availability check field.
8. Configuring Availability check and defining Checking Groups –
Checking groups are introduced into the sales order based on the setting in the material master record.
SAP standard checking groups are 01 – summarized requirements and 02 – individual requirements or you can create your own
by copying the standard ones.
Total sales and total deliveries columns are there to configure a checking rule to sum up requirements to post to MRP either
individually or by day or week.
Block quantity required can be set if you want several users to be able to process the material simultaneously in different
transactions without blocking each other.
The no check indicator is CHECKED when you DO NOT want the system to carry out ATP check.
9. Defining material block for other users – the block check box is an indicator that enables you to block material master records
of a particular material during the availability check and restrict other users from accessing same master record and reserve the
material. If the block is not set, two users can confirm the same material at the same time for two different orders, not knowing if
the stock is available or not. If you select this field, the material is blocked during the availability check and other users cannot:
a) Make changes in the material master record. b) Create purchase orders for the material. C) Create orders for the material.
10. Defining default values for checking groups - Checking groups are introduced into the sales order based on the setting in the
material master record.
However if there is no entry present in the material master record for the checking group, a default value can be set here,
depending on material type and plant.
This default value will be used by the system depending on the material type mentioned in MMR and plant in sales order.
If an entry exists, this default value is over written by MMR.
11. Controlling Availability Check – in this section, you tell the system what stock on hand and what inward and outward
movements of stock it must take into account when performing the availability check in addition to whether or not to consider the
replenishment lead time.
12. These settings are based on the checking group that is assigned to the material master record and the checking rule that is
predefined and assigned to the sales and distribution transaction.
13. These settings carry out control both for sales order and delivery as well. This is due to the fact that you may want to include
specific stock or incoming stock for the sales order, yet at the time of the delivery only include physical stock on hand waiting to
be shipped.
14. It is possible to indicate to the system that you would like the availability check NOT TO CHECK the stock at the storage
location level. This indicator is used to set the scope of the availability check.
15. It is used to switch off the check at storage location level. You create a reservation for a particular storage location.
However, the scope of the availability check is set in such a way as to exclude the storage location. In this case, the system
carries out the check at plant level only and does not take the storage location into account that is specified in the reservation.
16. Should you not want the system to automatically check RLT, you may indicate so here. RLT is the time taken for a material
to become available. It is only used when doing an ATP check and is taken from MMR.
17. Defining the elements in the availability check entirely depends on the business needs, but a few tips are given under –
When controlling the Availability check at the time of the sales order, a purchase requisition does not necessarily indicate by it is
going to come into the plant.
A shipping notification on the other hand - a confirmed purchase order – is a good indicator of receiving stock on a specified
date.
It is always recommended not to select the shipping notifications for the delivery requirements type as you may not actually
receive the stock into plant or warehouse for which you are creating a delivery.
 
REWARD IF U FINDS THIS AS HELPFUL...

current MRP current BP

MRP /BAG Billing Price /BAG

Withholding tax or Tax collected at source:

In India tax has to be collected at source (by the seller) from buyer on specific items like alcoholic liquor, tendu leaves, timber, other forest
produce, on mining/quarrying & scrap. Withholding tax rate or TCS rate is generally 1% - 5% varying from product to product. We will see
below process configuration for TCS on sale of affected products by creating a provision for the same in sales pricing procedure.
 
1. First we will create two condition types say JTCS for charging TCS in sales order & JWTS for posting TCS amount in FI with an
offsetting entry. Here, JWTS will be 100% value of JTCS and will be posted from sales order with accrual key say JTS.

 
 2. Include JTCS & JWTS in pricing procedure after regular taxes:

 
3. Assign withholding tax type in customer master as under:

 
NOTE: Create condition records for JTCS – 1%  with withholding tax code T1 & JWTS – 100%  with tax code T1 for your key combination
in VK11.
Tax collected at source entries in accounting document from sale of scrap will be as under:

 
Please note Extended withholding tax has to be activated for the company code and relevant FI configuration is required before use of
withholding tax in Sales.
FI Configuration is as under:
 
1. Define Withholding Tax Keys

After including country code (IN) in basic settings  - check withholding tax countries, a key for withholding tax has to be created. Enter
official key 206C for withholding tax – Tax collected at source
2. Now, define withholding tax type for invoice posting

 
Double-click and choose configuration for T1. Your choice of base amount & rounding rule here have to be backed up with subsequent
configuration for the same.

 
 
3. Assign condition type JTCS to withholding tax type T1.

 
 
4. Define withholding tax code in FI

 
Assign Withholding tax code for withholding tax type T1.

 
5. Further, assign withholding tax type to company code and define accounts for the same.

 
6.Define accounts for withholding tax to be paid over and accounts for withholding tax offsetting entry

 
 
7. Define processing key for modified net amount

Questions 35. What is the purpose of the moving price or standard price on the Accounting view in the material master?
(Choose two) 
A. To define the value that is used when posting the receivables for a customer ordering this material
B. To determine the value that is used for the accounting document when posting goods issue
C. To display statistical information for the costs in the pricing environment of a sales order
D. To define the sales price that is used when selling this material to a customer
Answer: B,C
Explanation:  

VPRS
 It cost is mainly used to determine whether the material is having the standard price or moving average price.
The condition type VPRS is labeled as a statistical condition in the pricing procedure.
in this, using the condition category G, the condition type VPRS goes into the valuation segment of the material master and
determines from here the standard or average price.
The condition category S always accesses the standard price whereas condition category T always accesses the average price.

EK01

It is used to is used to post actual price. If you use this condition type, the result of unit costing is issued to the first position on
the conditions screen for the item. The value can be used as a basis for price determination. It is mainly used for cost-plus
contracts in which the sales price depends on the expected costs.
It is selected for sales document type TA (standard order). This means that the value from the cost estimate goes directly into
pricing. A surcharge is calculated from this value and the net value for the sales order item is calculated. It will be positioned in
the first step of all the condition types in Pricing procedure and the values are given manually.
EK02
It is used for statistical posting. If you use this condition type, the result of unit costing is simply a statistical value which you can
compare with the price. So, this can be can used instead of VPRS to calculate the profit margin for the assembly item.
Please note the following points:
1) The condition type must have condition category 'Q' (costing).
2) The condition type must agree with the condition type defined for unit costing in the pricing procedure.
So, EK01 & EK02 are the condition type that will display the results of the unit costing for certain type of sales document and
can be used in Make To Order scenario.
Sales order cost estimate can be flow to COPA. Where you have to maintain setting in COPA in Define access to Standard cost
estimate for costing key select sales order cost estimate.
For transfer SD to COPA you have to use Transaction KE4I here enter SD conditions with COPA Value fields.
So, whether EK01 or EK02, these will determine from Requirement class configuration. Requirement class in turn there is
requirement type and requirement type is determined by item category and MRP type when you cost a sales order
(valuated/non valuated sales order) at that time when save the cost estimate then the cost value automatically gets populated in
your condition tab. Hence, if the item is not relevant to sales order costing then the cost comes from VPRS.

Shipping conditions modification in SAP On the basis of Matrial freight group.

Sale Order Qty in PCs and Pricing in Cubic Meter(M3)

Posted by S Jeeva in SAP ERP SD Sales on Mar 24, 2015 3:50:54 PM
inShare
Hi SDN Gurus,

I came across below requirement from the client.

Client is in to business of manufacturing building material, where business requirement is

“Order Quantity” Will be in Pieces (PCs) and “Selling Price” will be in Cubic meter (M3),
  which is nothing but Volume.

The same needs to be mapped in SAP.

While creating sale order, Customer requirement, is to have ONE Column for PCs and
ONE Column for Cubic Meter(M3)  at Item Level.

So that,while creating sale order, if Customer increases Order Quantity (PCs) for a material,
Should automatically update relevant Volume /Cubic Meter (M3) of the respective material.

Note: 
 Business requires, Order Quantity to be in Pieces (PCs) as the same requirement will be transferred to
       Production planning,to manufacture the material in pieces (PCs).
 Sale Order price to be calculated, per Cubic meter(M3) for calculated volume of ordered quantity
        in pieces(PCs) and price not to be calculated on Pieces(PCs)

        Eg: if 20 Piece=25.5 M3, then Sale order Item price, needs to be calculated for 25.5 M3 and
                not for 20 Pieces.

Example of Material Description

Vertical Panel T200 W600 L3000 

Dimension given in above material are in Millimetre (MM),

i.e.. Thickness 200MM / Width 600MM /Length 3000mm

T = Thickness / W =Width / L =Length

Solution to be mapped in SAP

One Column for PCs and One Column for Volume / Cubic Meter (M3),while

creating sale order
so that any change in Quantity ,should parallel y update respective Volume(Cubic
meter(M3) for the
material.

Price for the material to be calculated on “Volume/ Per Cubic Meter(M3)" for
ordered Quantity
which is in Pieces.

Proposed Solution in Standard SAP

(A)  In Standard SAP, While creating material master record “Volume /Cubic Meter M3”
      automatically calculated by giving dimension of the material.

   Create material (T.Code:MM01) "Basic Data 1" Tab , we can see VOLUME field.
 
Standard SAP system automatically calculate “Volume /Cubic meter (M3)”, while entering
product dimension, In “Additional Data” as shown below.

Click Additional Data,Go to Unit of Measure TAB, and scroll to the right, to enter

product dimensions in Millimetre
Enter Product dimension (Length/width/thickness in Millimetre) and Press ENTER.

System will automatically calculate Volume (i.e.) Cubic Meter (M3) of respective dimension of the material.
   
Calculated Volume in Cubic meter (M3) can be seen in “BASIC DATA 1” tab, as shown below

(B) 
Now, Sale order Price to be calculated based on Volume in M3 for the respective material and
     for calculated Volume for ordered quantity in pieces(PCs)
 
     To Calculate, Price based on Volume, do the settings in calculation type for respective
     Price condition type (Eg: ZPR0), as below.

     T.Code : V/06

     
      

 
    Create Sale Order (T.Code :VA01)
    

     

       
  To have volume and Volume Unit, scroll to the right as highlighted above,
 
  drag VOLUME and VOLUME UNIT, and SAVE it as a Variant as shown below.
 

 
  Above screen shot displays, Volume and Volume unit in Cubic meter (M3) for one Piece (PC)
 
  If we increase Order quantity (Piece), system parallel y updates the relevant volume, as shown below.
  
  
   Now,while entering Price for the material, system needs to calculate Price per Cubic meter (M3),
    for calculated volume for the ordered quantity in Pieces (PCs).

    
 
   Entering Price with “ZPR0” Condition type

    
Double clicking condition type “ZPR0” to see calculation details
  
As explained above, user requirement had been mapped in standard.
 
 
Note: This is the first document im posting, looking forward for valuable feedback.
 
 
Regards
 
Jeeva
Deemed Export
Welcome to the SD-CIN-Deemed Export page.
This process is specific to India Localisation Business Scenario.

Overview
This scenario deals with Deemed Export or CT-3 or SEZ sales that refer to sale of goods to customers within India, who are
generally holders of an export license. The materials sold are required to be used in the production of goods meant for ultimate
export. The customers can be an export-oriented unit (EOU) or located in one of the following areas:
 An Export processing zone
 An Electronic hardware technology park

 A Software technology park.

Sales Process
For this Deemed Export sale:
An inquiry can be the first step in the order cycle. The purpose of this activity is to create an inquiry to represent the customer’s
inquiry in the system.
 Then a quotation can be created to determine material, their quantities, prices and payment terms that are valid for a given sold-to
customer during a specified time period. As prerequisites, it can be referred from an existing inquiry and terms of payment need to
be in place.
Then in system we need to capture the Customer’s License Details. This done for
 Deemed Export License is captured in the system to represent customer’s licenses.
 For capturing Customer’s License details like material, quantity, value, expiry date etc.,

 Deliveries will take place against the license quantity / value.

As prerequisites, a copy of the license obtained by the customer from issued by relevant authorities.
Then a Sales Order is created to represent the customer’s requirement in the system. That will calculate the price and check for the
availability of materials. As prerequisites, it can be referred from an existing quotation and should mention material that are
mentioned in customer licence details.
Then with reference to the created sales order, a Pro Forma Invoice can be created in order to inform the customer about the value
of the goods, so that he will make arrangements for the payment to be made, when goods arrive at his place.
With reference to the created sales order, the delivery document is created for shipping point mention in sales order to pick the
goods and post goods issue based on availability of the ordered material.
With reference to post goods issue delivery material, a billing document is created to send a commercial invoice to the customer. It
also updates the corresponding GL Accounts. Further its output can be taken.
With post goods issue completed for the delivery and respective billing document generated, the Excise Invoice created for the excise
authorities. And subsequently print for accompanying materials that are being sent to the csurtomers.
ARE-3/ARE-1document is created with reference to generated outgoing Excise Invoice. This is assigned to a License captured for the
customer. This document is a proof that, goods are treated as Deemed exports and Excise duty does not need to be paid for these
goods, which are mentioned in the ARE-3/ARE-1.
After the responsible official confirms that all the details are correct, we can post the ARE-3/ARE-1 document. The changes are
allowed to the ARE-3/ARE-1 document only if, it is in the process pending posting. Once posted, the ARE-3/ARE-1 cannot be
changed but can only be cancelled.
Going further, we can print the ARE-3/ARE-1 documents for submitting to the customer and the excise authorities. After
ARE-3/ARE-1 Document is created and posted and also when the goods arrive at the Customer’s premises, they will check them
against the excise invoice and the ARE-3/ARE-1. If there are any discrepancies in the quantity of the goods, the customer will record
the actual quantity received on the ARE-3/ARE-1.To record the customer’s confirmation of the quantity delivered, we update the
ARE-3/ARE-1 document.Finally, when the countersigned ARE document arrives back at your premises from the customer, the
ARE-3/ARE-1 is further updated with the date of receipt. This closes the ARE-3/ARE-1.

System Configuration Considerations

   1        Defining Sales Document Type for deemed export
   2        Creating Pro Forma Invoice for deemed export
   3        Creating Billing Type for deemed export.
   4        Assigning Billing Types to Delivery Types
   5        Maintaining Item Categories
   6        Copying Control for
                  a.    Sales Document to Sales Document (Inquiry – Quotation, Quotation – Deemed Export Sal Doc Type)
                  b.    Sales Document to Billing Document (Deemed Export Sal Doc Type – Pro Forma Invoice)
                  c.    Sales Order type to Delivery Type (Deemed Export Sal Doc Type – Delivery Doc)
                  d.    Delivery type to Billing Type (Delivery Doc – Billing Doc)
  7        Configuring Pricing
                    a.    Pricing procedure for pricing
                    b.    New customer pricing procedure (Cust.pric.proc. is maintained at customer master) need to be maintain for deemed
export for differentiating from export pricing while pricing determination.
8        Account determination
9        Maintaining Number Range for Excise Bonding License for object J_1ILIC
10        Creating a new Series Group (maintain new series group
                    a.    Maintaining Number Range for Local Excise Invoice for object J_1IEXCLOC
                    b.    Making Settings for ARE-3/ARE-1 Procedure
                    c.    Maintaining Number Range for ARE-3/ARE-1 for object J_1IARE3/J_1IARE1
                    d.    Defining Processing Modes per Transaction, this will make ARE-3/ARE-1 options active in the ARE-3/ARE-1 screen
                    e.    Defining Reference Documents per Transaction
11        Maintaining an output types for ARE-3/ARE-1 Sales which will be based on plant.
12        The following Master Data will attract attention,
                     a.    Maintaining Customer Master, particularly, Cust.pric.proc. in pricing section of Sales Tab in Sales data.
                     b.    Customer CIN details (J1ID)
                     c.    Maintaining Material Master
                    d.    Material CIN details (J1ID)
                     e.    Maintaining relevant conditions records for:
                            i.      Pricing
                           ii.      Tax

Development activity to be consideration

 Following output type & program we may need to maintain/modified as per requirement:
Object Object Name Object Desc Configuration

Output Type J1ID Excise Bonding ARE New config may be required

Output Type Access Sequence ZJ1D ARE3 Op Acc Seq New config may be required

Program J_1IPRNTARE Print program for ARE Std config available

Form J_1I_ARE3 J_1I_ARE3 Printing Std config available

Further Information:
Following are few of the License Types:
1. CT-1(Value based),
2. CT-2(Quantity based),
3. 108/95 (un-projects),
4. 15/2009(solar projects), etc.
So, when CT-1 one of the license types, for that you need to create ARE3 use TCode J_1IARE3. Then you need to capture license by
using TCode J1ILIC01.
Further, if your scenario is of exporting under bond, then you might need to create ARE1 use TCode J_1IARE1 and also create bond
by using TCode J1IBN01.
1) Automatic PGI from Shipment doc:-
Tcode: 0VTL (Path:- IMG>Logistic Execution> Transportation> Shipment> Define & Assign Activity Profile)
select "Shipment doc type" , click on Maintain
 
then in "Post Goods Issue for deliveries of shipment"
- Carry out goods issue posting during save
 
Then, when you save the Shipment document PGI document will be created automatically.
 
2) Automatic Excise Invoice :-
IMG>Logistics General>Tax on goods Movement>India> Basic setting-->Maintain excise Group  :- here you can select the
check box of Create EI for your Plant. This will create Excise Invoice as soon as you save the Invoice.
How to get Opening & Closing Balance in RG1

when you update(J1I5) and extract register(J2I5) ,it will update the table J_1IGR1 with movement type and classification code.Check with
your abaper whether he included this table in RG1 Report or not.If not then give him logic to add manufacturing qty with movement type
321 andissue qty 601.
 
Logic :-
opening qty + manuf qty - issue qty= closing qty and todays closing qty is next day opening qty.
 
Regards
DevD

Basically the main master data in Sales and Distribution:

Customer Master Data
Material Master Data
Output Master Data
Incompletion Log
Condition Master Data in Pricing
Taxes
 
rganisational master data
Customer and Material master data
Documentary master data
Conditional master data( what ever  we create using basic functions)

give me 5 different ways you can block the material from 

creating a sales order
we can block the materila at palnt level in basic data 1; 
sales level both distribution and divison as sales org 1; 
we can block at sales document level but putting a block 
on delivery; we can block at item category level ; we can 
block through schdule lines ; we can block through listing 
 and exclusion by given exclusion indicatior int hecondtion 
type ; we can block at substituion where you substitite the 
material for some other material

invoice list

https://wiki.scn.sap.com/wiki/display/SD/ERP+SD+Invoice+Lists

This article covers a simple example of Invoice List in SD-BIL area.

Overview
Invoice lists are mostly used to provide some benefits for payer when possible. Some benefits are the following:
 To be able to consolidate/print several invoices into one.
 Having billing date of invoices changed once it is consolidated. Customer may required submission of consolidated
invoices by date.

 Factory discount is applicable.

 
It is also benefitial to the seller while organizing the billing documents a invoices are grouped into one invoice list. It simplifies
the control once there is only one payment which means that accounting document of invoice list takes place of all its invoices'
account documents.
Depending on the payer's country the payer may pay tax for the discount provided. The condition type for factory discount is
RL00 while its tax is MW15 (optional).

Settings
There are some settings before creating Invoice List, here they are:
1. In Billing Document Types make sure that Invoice List Type (LR) is assigned to the invoice to group (E.g: F2).
2. Make sure that copy control make use of requirement 016 from F2 to LR ( VTFF transaction ).

3. Set a calendar for Invoicing List Dates ( XD00 transaction ) to the related customer/payer.

4.      Set RL00 (statistical) in the pricing procedure, for example:

5.       Set condition record for RL00 ( VK11 transaction ).

 You may want to set also in pricing procedure the tax MW15 (optional) and also to determine LR00 (invoice list header)
to create printing papers output automatically.

Invoice List Creation Steps

It is simple flow of SD transactions before creating Invoice List (transaction VF21), like VA01, VL01N and VF01.
1. Create more than one sales order for a same payer.
2. Creates respective delivery orders.

3. Create respectives invoices.

4. Now you create the invoice list (VF21).

5. Hit Execute button and check discount as per defined in condition records:

n 3rd party sales process we have two scenarios.

 
1. With out shipping notification ( this is standard we usually many time follow).Here MIRO is mandatory before creating
customer invoice.
 
Billing relevance is (F) and in copy control in billing qty (F).
 
2. With shipping notification (here MIRO is not mandatory before customer invoice creation.
 
subject to you need to have the changes in below.
 
In VOV7 (For TAS )item category the billing relevance should be (G) and
 
in the copy control VTFA  at item level  for item cat (TAS)maintain the billing qty(E)
 
remaining all settings are same as 3rd party sales with out shipping notifications.
 
Here system will not stop at the time of invoice creation even though MIRO not completed, later as per your requirement you
can create every month end.

he thread was nicely described by Srinu. If I am not wrong, I can give a scenario where we use Billing relevance as "B" in Item
Category TAS. Suppose there is a agreement between Business and Customer that business will invoice in full to the customer
if vendor delivers partially also. Means customer has ordered 100 qty but vendor delivered only 50 quantity but customer will be
billed for whole 100 qty. In this case we use Billing relevance as B.

When you create a purchase order using the purchase request corresponding to the
third-party order line, SAP automatically updates the purchase order number in
the document flow of the sales order. Any changes in the delivery dates or quantity
thereafter in the purchase order automatically updates the confirmed quantity and
confirmation date in the corresponding schedule line on the third-party sales order,
but the reverse way is not allowed. Any changes in the quantity or date in the sales
order does not change the purchase order quantity or delivery dates. It is therefore
always suggested to make changes in the purchase order and not in the sales order.
You can also use report SDMFSTRP to find any quantity differences that exist
between the sales order and the purchase order.
Definition: excise bond type

Logistics - General (LO)

Distinguishes between the following types of excise bond:

 Running bond

 Fixed bond

 Letter of undertaking

Internal Bond Number

Displays the internal excise bond number.

Dependencies

The system numbers bonds using the number range J_1IBOND. You can customize the number range in Customizing for
Logistics - General, by choosing Tax on Goods Movements -> India -> Tools -> Number Ranges.

Transfer of Requirements

By means of the transfer of requirements, the MRP department is informed about the quantities and deadlines by which
incoming orders should be delivered. The system checks the availability of the goods based on the requested delivery date of
the customer and creates MRP records which contain all necessary information for passing on to materials planning. The
transfer of requirements ensures that the goods are available in time for the delivery. Materials planning transfers the reported
requirements and creates production orders or purchase requisitions from them, for example.

The following sections on the transfer of requirements describe how to control the transfer of requirements.

The transfer of requirements is basically dependent upon the following factors:

 requirements type

 requirement class

 check group
  schedule line category

Note

The transfer of requirements is controlled globally using the requirements class which is derived from the requirements type for
all sales document types. For the sales document types, fine tuning is also possible at schedule line level. This fine tuning is
described in the section "Defining the procedure for each schedule line category".

Note that the requirements classes are also used in production so you should coordinate  any changes to the requirements
classes with production. The requirements type and, eventually, requirements class are determined in the strategy group so all
changes made there should also be coordinated with production.

Requirements transferred to planning are further processed in the module MM. You must, therefore, coordinate the transfer of
requirements with the module MM.

Requirements

For controlling transfer of requirements, you have to carry out the following steps:

1. Each requirement type has to be allocated to one requirement class only.

2. The transfer of requirements must be switched on at requirements class level, the sales documents at schedule line
level.

3. You must define a check group. It is possible to have this check group proposed for the initial creation of a material
master record.

4. Note that a plant must exist for transfer of requirements to be carried out at document item level.

Note

Requirements transferred to planning are further processed in the module MM. You must, therefore, coordinate the transfer of
requirements with the module MM.

Availability Check

The following sections describe configurations for the availability check.

For every item of a sales order or delivery, the SAP system checks availability if the appropriate configuration is set in sales
order processing and shipping. The availability check procedure depends on several factors and varies according to the
configuration.

It is possible to control the availability check for sales documents and deliveries separately. You can,for example, control the
scope of the checks or whether the replenishment lead time is taken into account, for example.

The availability check is controlled by means of the same elements as the transfer of requirements:

 Requirements class

 Requirements type

 Checking group

 Checking rule

 Schedule line category

 Strategy group

 Planning strategy

For more information on strategy groups and planning strategy, see the 'Planning strategy' chapter under Production Planning in
the Implementation Guide.
Requirements

Process the following points to control the availability check:

1. For the sales document types you must determine for each schedule line type whether an availability check should be
carried out or not.

2. The availability check should be switched on at requirements class level and at schedule line level for sales
documents.

3. You can define a checking group which can be proposed, depending on the material type, when a new material
master record is created.

4. The requirements types used must each be allocated to a requirements class.

5. Note that a plant must be available if an availability check is to be

Re: Regarding Automatic Picking Setting in Deliveries

Check here SPRO > LE > Shipping > Picking > Define Relevant Item Categories

0vlp

Steps for opening and closing Period – MM FI CO

 
As many of us struggle with changing periods in our DEV and QA environments, here is quick reference for opening and closing
period. In doubt, please consult with your FI/CO expert.
 
There can be upto four transaction involved depending on your situation.
 
•          MMRV - Allow posting to previous period
•          MMPV - Close Periods
•          OB52 - Change view "Posting Periods: Specify Time Intervals": Overview
•          OKP1 - Maintain Period Lock
 
1. MMRV – View current period / Allow posting to previous period

 
This transaction allows you to view current period and change setting for posting to previous period.

 
 
2. MMPV - Close Periods

 
In MMPV you can execute period closing up to the end of the current fiscal year. The period closing program updates the
administration record, thus ensuring that the stock data of the material master are updated.
 
If, for example, you want to close your periods up to 03/2013, you are not allowed to post values in 01/2013. Therefore, if you
still want to make postings in period t, you should execute period closing only for a maximum of t+1 periods.
 
 
 
3. OB52 - Change view "Posting Periods: Specify Time Intervals": Overview

 
In this activity, you close the posting periods for FI-AA and open the new periods for FI-AA.
No more FI-AA postings can be made to the previous period. Postings for the future periods are allowed.

 
4. OKP1 - Maintain Period Lock

 
If needed, unlock period for CO transaction.
 
If I have missed anything here or misinterpreted, let me know and I will correct it or add additional clarification/tips.
 

Billing date for billing index and printout

The date on which the billing is processed and booked for accounting purposes.

Use

You can use the billing date as one of the selection criteria when you process billing documents collectively.

Procedure

If invoice dates are defined for the customer, the system proposes the billing date from the invoice date calendar. If no invoice
dates are agreed, then the actual goods issue date is formed on the basis of delivery related billing. In order related billing, the
billing date of the order forms the basis of the billing date.

If you are billing services, the system proposes the date of services rendered. You can change the date manually in the sales
document.

If you are using a billing plan to bill a project, the system can propose billing dates for the billing plan on the basis of planned or
actual dates in the corresponding milestone.

In a billing plan for a maintenance or rental

Date for pricing and exchange rate

The date that determines date-related pricing elements, such as conditions and foreign exchange rate.

Use

You can use the pricing date as one of the selection criteria when you process billing documents collectively.

Procedure

The system proposes the current date. You can change it manually in the document. If you change the pricing date, the system
recalculates pricing for the entire document. If the date is in the past, you receive a warning before you can continue.
Determining the Proposal

In the order: You can customize the order type to determine a proposal, such as the current date or the requested delivery date
as the pricing date.

In the billing document: The billing date is proposed as the pricing date.

The difference between KOFI and KOFK is

 
KOFI -- Account determination without CO
 
KOFK -- Account determination with CO
 
You can control through Routine, which you can placed in Requirement Colomun of the account determination procedure.
 
Routine 2 - With CO acct.assignt
Routine 3 - With out CO acct.assignt

1)  Exports Under Bond

 
Exporters are classified into two categories. Manufacturer-Exporters who manufacture and export  the goods in his own name without
payment of excise duty and Merchant Exporters who buy the goods without payment of excise duty from a manufacturer and export the
goods in his name.  For getting the goods without payment of duty, the merchant exporter has to necessarily execute a bond (standard forms
are prescribed for various types of bonds, in which the assessee gives an undertaking to export the goods within a stipulated period as per the
law).  The execution of bond is to ensure that in case of non-fulfillment of obligation, the central excise duty amount liable to be paid on the
goods can be realized from him. Normally the bond is executed for an amount equivalent to the duty amount payable on the goods that the
exporter is planning to export.  Whenever  the goods are cleared from the factory without payment of duty for export, the duty amount
 payable on the goods will be debited from the Running Bond Account.  Whenever the goods are actually exported (after the proof of export
is received from the Division/Maritime Commissioner),  the manufacturer will take credit of the duty amount debited earlier by him.  The
manufacturer also has the option to maintain a running bond account by executing a bond with the Central Excise authorities.    Though it is
optional for a manufacturer-exporter to execute a bond for export clearances, it is very much necessary for merchant exporters. 
 
 
2)  Exports under Letter of  Undertaking
 
The manufacturer  exporters have another option for clearing their goods for export without payment of duty.  They have to give a letter of
undertaking which is valid for a year.  This procedure of giving a letter of undertaking  was introduced as a liberalization measure.  The
assessee will not have to follow the difficult legal procedures involved in executing a bond (providing surety/security in the form of Bank
Guarantee etc).  It will be sufficient if he just gives the letter of undertaking in the form prescribed. 
 
 
3)  Exports under Rebate
 
Export  under Rebate is the procedure in which the exporters first pay the central excise duty before clearing the goods from the factory and
subsequently get it back by applying for rebate after the goods are exported.  They have to apply to the Division or to the Maritime
Commissioner (designated exclusively to look after all Export related issues) as the case may be, along with the required documents (usually
the Export Promotion copy of the Shipping Bill and Bill of Lading) to prove that their goods had actually been exported.    Rebate can be
claimed for both the inputs (purchased from indigenous markets and used in the manufacture of exported goods) as well as for the final
products.  Normally, rebate is being widely opted by non-excise assessees (for example garment exporters) who procure raw materials
locally, manufacture their final products and export them.   It is similar to Drawback of Customs duties in respect of Imported raw materials. 
 
With regard to number range for domestic and exports, you have to maintain a seperate number range for each in T.Code SNUM  and the
Objects are
 
-  J_1IEXCEXP:::::for  Export excise invoice number range
-  J_1IEXCLOC:::::for  Local excise invoice number range
 
thanks
G. Lakshmipathi

Regarding
Bond / No Bond / Deemed / LoU buttons for exports  comes automatically
 
we have to make default setting in
IMG > Logistics General > Tax on Goods Movements > India > Business Transaction > Outgoing Excise Invoices > Maintain
Default Excise Groups and Series Groups
 
Here we maintain default settings for Excise group and series group against combination of Sales Org + Distt Channel +
Division + Shipping point + Plant. There is one more TAB 'Export' under which we maintain
Deemed Export
Export Under Bond
Export under Claim for Rebate
Export under Letter of Undertaking
 

A list of major topics covered in this step-by-step SAP material is below;

 Check Scheduling Agreement MD04

 Check Stock Of Material MMBE
 Exploded BOM View CS11
 Reservation Creation: By Manual Creation Through MB21, Reservation Display MB25, Stock Transfer Posting MB26 ,
By Manual Creation Through MB1B
 Check Bill Of Material CS03: Checking Standard BOM, Adding An Alternative BOM
 Check Routing – CA03: Checking Standard Routing, Adding An Alternative Routing
 Production Order Creation – Manual CO01
 Shop Floor Printing – Production Order CO04
 Production Order Confirmation CO11N
 Quality Inspectation QA32
 Production Order Settlement KO88
 Production Order (Technically Complete) CO02
 Check Production Order Reports
 Production Order – Through Demand Management
 MRP – For Planned Order + Purchase Requisition

rRe: How to trigger accounting entry in PGI 

 Hope you have searched the Forum before creating this new thread
  
 A Movement type is attached to every Schedule LIne in Sales Order (Generally 601 for Goods Issue Delivery).
  
 Now go to T-Code OMJJ & open movement Type 601. Then select Account Grouping Folder from laft hand side.
  
 Here you can see Transaction key assigned to this Movement Type (GBB in this case).
  
 Now go to T-Code OBYC & select yuor Chart of Accounts & double click on GBB.
  
 In tthe subsequest screen you can see the Debit & Credit side GL Account assigned for GBB.
  

F: Order-related billing doc. - status according to invoice quantity

Relevant for order-related billing documents based on the invoice receipt quantity (third-party business transaction). The system
transfers the order into the billing due list only after the vendor invoice has been received and processed in the purchasing
department. After the receipt of each invoice, a  customer invoice is created for the quantity that appears on the vendor invoice.
The order has status "Billed" until the next vendor invoice is received.

Item category TAS (Third party item) is set up with billing relevance "F" in the standard system.

This process can also be related to the quantity of goods receipt.

You can make the control setting as to whether the invoice receipt quantity or the goods receipt quantity should be relevant for
billing in the copy control for billing on the item level in the billing quantity field. (In Customizing, choose Sales and Distribution -
> Billing -> Billing documents -> Maintain Copying Control for Billing Documents -> Copying Control: Delivery to Billing
Document -> Item, then select an item category.)

1) There are two types of Third Party Processes: -

 
a) Third Party Process without Shipping Notification
b) Third Party Process with Shipping Notification.
 
 
Third Party Process without Shipping Notification
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
 
 
Third Party Process with Shipping Notification
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
 
 
So, technically the 3rd Party Sales w/o SN is commonly used - whereby no GR is required. GI and GR process is between the
vendor and the customer in the Sales Order. Once customer confirmed received, only then there will be incoming invoice from
the Vendor, which then MIRO and Billing follows..
 
 
 
2. Standard SAP practice.. it is recommended to perform MIRO before Billing, as the vendor has to advice us that our customer
has received the goods of the quantity ordered, which only then we can bill the customer according to the quantity received by
the customer.
 
Thanks.
Reply to Query 1
After creation of the inbound delivery, a statistical goods receipt is posted automatically. This goods receipt does not trigger any
inventory management goods movements. It is only required so that it can be posted (statistical goods receipt), since this allows
invoice verification with reference to the purchase order. Since a third-party order involves a movement from the vendor direct to
the customer, Inventory Management is not in any way affected. If you wish to document the movement in the system, however,
you can create a goods receipt for the third-party order.
TAS Third party Item category is linked with Schedule line Category CS in SPRO .
Schedule line category CS is assigned to Item cat = 5 .This 5 get linked to Goods receipt with reference to a purchase order
through
 
MM>Purchasin>Statistic-->assign update groups to item category
 
 
 
Reply to Query 2
As per the SAP best practice it is recommended to perform MIRO before billing for the same only Item category TAS (Third
party item) is set up with billing relevance "F" in the standard system.
(F: Order-related billing doc. - status according to invoice quantity)
This is relevant for order-related billing documents based on the invoice receipt quantity (third-party business transaction). The
system transfers the order into the billing due list only after the vendor invoice has been received and processed in the
purchasing department. After the receipt of each invoice, a  customer invoice is created for the quantity that appears on the
vendor invoice. The order has status "Billed" until the next vendor invoice is received.
 
This process can also be related to the quantity of goods receipt.
 
You can make the control setting as to whether the invoice receipt quantity or the goods receipt quantity should be relevant for
billing in the copy control for billing on the item level in the billing quantity field.
(In Customizing, choose Sales and Distribution -> Billing -> Billing documents -> Maintain Copying Control for Billing Documents
-> Copying Control: Delivery to Billing Document -> Item,
then select an item category.)

SAP Customizing Implementation Guide>>>>>>Logistics - General>>>>>Tax on Goods Movements>>>>>

India>>>>>Business Transactions>>>.>>Outgoing Excise Invoices>>>>>Maintain Default Excise Groups and Series Groups
 
 
Sales Org.
Distr. Channel
Division
Shipping Point
Plant
Excise Group  here enter the excise group
Series Group====series group of exports
Export Type==== deemed export
Sub Transaction Type

Hi Sudheekar, 

Migration of data from Non SAP To SAP is as good as Maintaining New data in the system. 

Following SAP Tools we can use to accomplish the requirement as mentioned below, 

LSMW -Legacy System Migration Workbench ---This is Pure Functional tool or T-code through which we can create the
recording in the system for respective transaction and make the file for data upload as per required fields to maintain w.r.t.
business requirement. 
BDC---Batch Data Communication -This is Module integration Work i.e. Functional consultant need to perform the recording of
the respective transaction like XD01 and give it to ABAP Consultant for further processing and then we can have the T-code and
Flat file with required field and format as per requirement. 

BAPI---Business Application Programming Interface.--- is once of the Most Effective tool to migrate the data like Ex: Creation of
SO in Bulk--In case of cut over data where same sales order need to create in SAP Which were closed open in Legacy system. 

IDOC---Intermediary Document ----- is a standard data structure for electronic data interchange (EDI) between application
programs written for the SAP business system or between an SAP application and an external program.

I will list out few of critical issues in

 
Implementation :
 
1 . Ensure 100% mapping of business process for all modules with SAP(avoid customization in support phase)
2.  Unit & Integeration testing should be through with all validations
3.  Master datas(Vendor,Customer) care must be taken will uploading datas thru LSMW,
If there are common vendors for all plants,Create a vendor for a plant extend it to other plants
4. Check tax procedures are customized according to requirements.
5. Complete all print document customizations before go live
6. Complete end user training(2 or more cycles) should be top priority before go live(This will avoid
cancellation/reversal of documents after post go live)
7. Ready with standard MIS reports & customized reports for business decision making
8. Excise opening balance updation in tables for RG1 register in tables(Note 951955) on go live
9. Check all tables datas are updating correctly
10. Declare go live to SAP Support
11. Check All user authorization should be correct according to their roles.
12. Centeralize all master datas creation(avoid duplication)
13. Create transaction variants to avoid entires in unnecessary fields & make certain fields mandatory.
14. Ensure document numbering is completed for all documents
15. Validate accounting entries are hit properly according to requirement in quality client with FI CTM(Core team member).
 
After Go live :
 
1. Missing authorization for users will play key part here,For ex : PGI while doing delivery,Excise capture & post in MIGO/J1IEX.
2. Do internal audit every month,identify transactions if there will possibility for misuse or wrong entries,requires
validation,identify users weak in certain areas.
3. Identify there is enhancements to be done in transaction process(By step-2)
4. Prepare a list of month & year end activities to be performed for all modules give to users
5. Prepare  a list of frequently used transaction codes module wise give it to users
6. If there is subcontracting,ensure challan creation,GR,reconcillation should be done regulary(monthly)
7. Train the users,take reports in respective modules.
8. Additonal customization might be done in print documents.
9. Instruct users/CTM's to adapt SAP Standard practise
10. Update excise tax rates after every indian budget

 Confirm quantity in schedule line

Hi,
 
T. Code: VOV8
 
Select your Sales Doc. type and Double-Click.
 
In Tab: Shpping,
 
Check Box: Immediate Delivery (press F1 to read more about this functionality).
 
Hope this may resolve your query.
 
Best Regards,
 
Amit
 
Note: There are few more settings that you may check:
 
1. T. Code: OVLZ
 
Field: Pick/pack time wrkdys whether you have maintained any value. It should have been blank
 
2. T. Code: VOV8
 
Check how many days mentioned in Lead time in Days. If it is mentioned any days, remove it.
 
3. T. Code: OVZ9
 
Checked the Box: Check without RLT .
 
4. Check in material master MRP2 view how many days are maintained for the fields In-House production and GR Processing
Time
s

1. What do you mean by drop shipment?

2. What is the use of sales area?
3. How does the rule MALA decide the picking location?
4. What is the difference between customization and configuration?
5. Is it possible to do delivery without shipping point?
6. Explain about smart forms?
7. How sales document is structured?
8. In sales order how system does picks up plant?
9. Without delivery can you do billing?
10. Could you explain about sales deals?
11. What is the use of pricing date in condition type?
12. WHAT DOES A/C GROUP CONTROL CUSTOMER?
13. Can you explain about Higher-level item category and item usage
14. Why do you need project IMG?
15. How we assigned sales organization to delivering plant?
16. How to extend material and customer to other sales areas?
17. How can we process out bound deliveries without shipping point?
18.While I am creating a customer in ship to party account group you have shipping and billing partner function tab
pages, client wants to shift all important fields in billing like payment terms, incoterms , and tax classification into
shipping tab page. He wants only shipping partner function only, how does you customize?
19. Why do I use condition indexes? How do you activate them?
20. Is it possible to release change request, without releasing task.
21. Product attributes means?
22. Can one have multiple packing for delivery?
23. Explain EDI and its usage?
24. To extend material one plants to another plant what are the configuration you done in your project?
25. What is the client specific data? Give two examples of client specific data?
26. How to stop PGI?
27. How SAP support to the client to know the customer requirements?
28. Can we assign multi distribution channel to a single customer in sap SD sales process. If yes then how?
29. What is the difference among sales deal promotion price, price agreement?
30. What is the difference between inbound and outbound delivery?
31. From Which Tcode can I view customer wise back order (Open Order?)
32. What is retro active billing? Who is will create this?
33. Where do you assign Movement Type?
34. Can anyone explain about Purchase Order & Purchase Requisition?
35. In one sales order there are two materials can maintain two different pricing procedures for these materials?
36. List the Basic Steps for SD configuration.
37. HOW YOU CAN EXTENT THE REBATE? WHAT ARE THE PROCEDURES, WHAT IS THE CUSTOMISATION FOR IT?
38. What is accounting group?
39. What are the differences between invoice and billing document?
40. What is pricing? How will it affects the billing procedure?
41. What is act key? And how it works? Normally how many pricing procedures do in implementation?
42. Tell me account key and accruals?
43. What is the docu.flow?
44. What is the transfer order?
45. What is the purpose of text determination, account determination, partner determination, output determination,
storage location determination
46. What are the five imp fields to be maintained in account determination?
47. What is meant by transfer of data from legacy code to sap?
48. What and where types of copy controls we change?
49. What do you do really in pricing determination, and what are the main differences between one pricing procedure
determination to the others, which data control these differences?
50. How to and where to maintain copy controls?
51. What is purpose of maintaining common distribution channels and common division?
52. What is sales order Item category Determination n what is delivery Item Category determine?
53. Can you deference between contract & scheduling agreement?
54. What is PMIN?
55. Explain About Dunning Procedure?
56. What is client requirement in Schedule Line Category?
57. In how many places we can block the Sales Document?
58. What is the Difference between Reconciliation A/C and Normal Posting A/c?
59. What happens if we check 'exclusive' indication in access sequence, and what happens if we do not check?
60. Can anyone tell about types of free goods?
61. What are the 16 steps in the pricing procedure?
62. Difference between plant and storage location?
63. Do u have any link for customer master and credit management?
64. Explain about sales order cycle?
65. What is the relation between sales organization and company codes?
66.Sales order is created 1st November for 200 tooth pastes 100 brushes free of goods(2+1 free goods).At the time of
delivery on 15th November you have shortage of brushes by 40. Offer closed on 15th November. How do you solve in
this scenario?
67. Can one create delivery with reference to the project?
68. What is the difference between cash sales and rush order?
69. How system picks up pricing while doing billing?
70. Diff between business sale cycle nd customer sale cycles?
71. How do we control the credit checks with specific to distribution channel and division?
72. CAN YOU CONFIGURE TWO DIFF FREE GOODS ITEMS FOR ONE SINGLE ITEM?
73. For the 1st 10 sales order I want to give discount, so what customization we have to do with
74. Can you delete order?
75. MWST? Pl explains in detail.
76. What makes Listing & exclusion Work differently than each other?
77. How to do customization of rebate processing in sap SD????
78. Which partner function realent for credit limit?
79. Name three areas/processes which use condition technique in SD?
80. Explain what a condition table and an access sequence are and the relationship between them?
81. What is a condition type? What are the two main groups of condition types?
82. Which partner function is relevant when it comes to tax calculation in the sales order?
83. Where would you specify that a condition type is a discount or a surcharge?
84. You want to list all condition records for a certain material or a certain sales organization. How would you do that?
85. Can you explain what a statistical condition is? Give an example for a statistical condition?
86. For what do you use customer hierarchies?
87. Name the influencing factors for pricing procedure determination during sales order entry?
88. Can you copy condition records? If yes, are there any restrictions?
89. Tax jurisdiction processing is a close link between which two modules?
90. Can you delete an invoice?
91. When you create an invoice can you carry out pricing again?
92. From which documents can you create a Performa invoice?
93. When you create a credit memo request do you always have to refer to a sales order or any other previous
document?
94. Can you combine orders into one invoice?
95. Can you split deliveries into several invoices? When would you do that? 
96. Can one business area be valid for several company codes?
97. There is an interface between SD and FI in invoicing. Can you think of another interface between SD and FI?
98. Can you partially settle rebate accruals?
99. Is it possible to link R/3 projects to the MS project?
100. What two ways of number assignment for documents or master data do you know? Explain the difference
between them.

23. Explain EDI and its usage?

Edi - it helps for data transfer
That means from sap or non sap to sap

24. To extend material one plants to another plant what are the configuration you done in your project?
We have to create in new plant as we have followed for First plant, where as in first plant system will give Internal
number but for second plant we have to mention
Material number.

25. What is the client specific data? Give two examples of client specific data?
1-master data
2-transction data.

26. How to stop PGI?

IN CREDIT MANAGEMENT WE STOP THE PGI BY THROUGH CREDIT LIMIT OR THROUGH CUSTOMIZATION.

27. How SAP support to the client to know the customer requirements?
Support to client- 1- implementation method
                   2- Correction method

28. Can we assign multi distribution channel to a single customer in sap SD sales process. If yes then how?
While creating customer we need to assign the customer to
The respective sales area, we should copy from previous
Sales area in XD01 through reference

29. what is the difference among sales deal promotion price, price agreement?
Sales deal promotion-- specific product for a period of time price will be less than MRP.

Price agreement-- means an agreement between customer and Vendor for a specific product or with a specific price
mentioned in their agreement.

30. What is the difference between inbound and outbound delivery?

Out bound delivery--- is Post goods Issue (PGI)
In bound delivery--- is Post Goods Received (PGR)
PGI will come under Sales Area
PGR will come under MM Module
PGI decreases physical stock and PGR increases

31. From Which Tcode can I view customer wise back order (Open Order?)
V_RA

32. What is retro active billing? Who is will create this?

Retro active billing means rebate process. When ever the customer reaches the target quantity or volume in specified
time Peried. we issues the credit memo for the customer.

33. Where do you assign Movement Type?

We assign movement type in schedule line category.

34. Can anyone explain about Purchase Order & Purchase Requisition?
In third party if a customer places an order if the Material is not available in our company if the order Document is
saved automatically purchase is raised.withthe help Of this purchase group is created

Purchase requisition--- For production of material raw Materials are required, but materials are not available in Stocks,
then the production dept. request send to the MM manage simply request him to arrange Materials for production of
finished materials.

35. in one sales order there are two materials can maintain two different pricing procedures for these materials?
No, u cannot maintain 2 separate pricing procedure for same Material in single order. But u can change the price
Manually by selecting the material and then the conditions Tab....u can also see the changed status as manually later

36. List the Basic Steps for SD configuration.

  1. Enterprise structure
  2. Partner determination
  3. Master data
  4. Business process customization
  5. Pricing
  6. Output determination

37. HOW YOU CAN EXTENT THE REBATE? WHAT ARE THE PROCEDURES, WHAT IS THE CUSTOMISATION FOR IT?
The transaction coed for extend rebate is "VB (D" in that You should fill the field like recipient and rebate Agreement.

For customization same as create condition tables but Already there are standard tables and define accessequence
And assign condition types. There are already standards are There like b001, b002, b003, b004 then assign pricing
Procedure to condition type, next create account keys and Assign to rebate process type

38. What is accounting group?

Accounting group is simply the classification of customers, Whether its sp, sh, bp, or py, and it also controls the
Fields in cmr.

39. What are the differences between invoice and billing document?
Billing Doc is the broad view Invoice (F2) is one of type of billing doc.

40. What is pricing? How will it affects the billing procedure?

Pricing has the basic price of the item. It also has the Discounts, Taxes, Rebates, & also the Cost of the item.

41. What is act key? And how it works? Normally how many pricing procedures do in implementation?
Account key determine a correct G/L account to be posted the data corresponding G/L accounts. You need to assign a
G/L account to account key that is assigned to a condition type in a pricing procedure.

42. Tell me account key and accruals?

A/c keys determine a correct g/l a/c to be posted the data corresponding g/l a/c. All customer Rebate accounts are
posted in accruals.

43. What is the docu.flow?

        Inquiry
        Quotation
        Sales Order
        Delivery
        Transfer Order
        Post Goods Issue
        Billing
        Accounting

44. What is the transfer order?

Transfer order is basically picking order where u pick the Material from storage and loading area or picking area

45. What is the purpose of text determination, account determination, partner determination, output determination,
storage location determination
1. Text determination: For transferring information from material or customer to order/delivery or invoice (and anything
in-between)
2. Account determination: For transferring financial and costing information to proper financial docs
3. Partner determination: for deterring who is legally responsible for A/R, who the goods are going to and whatever
else you drive through this functionality.
4. Output Determination: What type of Output (Fax/Mail, etc) is required, where and in what Format (ABAP
Customization may be required in some cases especially Invoices).
4. Storage Location Determination: depends on Plant, Shipping Point and Storage Conditions

46. What are the five imp fields to be maintained in account determination?
Sales org., A/c keys, condition type, a/c group for the customer, a/c group for the material

47. What is meant by transfer of data from legacy code to sap?

Before installation of SAP, Data maintained by Company is called Legacy Data. At the time of installation, it is required
to transfer Data from Legacy to SAP like Masters (Material/Customer, etc).

48. What do you do really in pricing determination, and what are the main differences between one pricing procedure
determination to the others, which data control these differences?
Pricing prosier determination-----Pricing is determined by combination of Sales Organization, Distribution Channel,
Division, Customer Pricing Procedure and Document Pricing Procedure.
Pricing prosier----Pricing prosier is the simple prosier of pricing .It identify different- 2 step, counter of condition.

49. What and where types of copy controls we change

Copy Control--- is basically meant so that Data is copied from preceding Document to subsequent one. In general case
of Standard Order, it will be Copy Control (Order to Delivery) from OR to LF.

50. How to and where to maintain copy controls

(Sales Document types and Delivery Document Types)

51. What is purpose of maintaining common distribution channels and common division??????
Common Distribution Channel and Common Division are maintained so that if any master data like customer or
material maintained with respect to one distribution channel can be used in other DCh. It prevents the multiplication of
master record

52. What is sales order Item category Determination n what is delivery Item Category determine?
53. Can you deference between contract & scheduling agreement?
Scheduling Agreement--- is the agreement between consumer and
Company having fixed delivery dates and fixed quantity.

Contract--- is the agreement between company and consumer for certain period of time.

54. What is PMIN?

PMIN is a Condition type to define minimum prices. It can be Control minimum prices below which a material should
not be sold to the customer.

55. Explain About Dunning Procedure?

Dunning procedure is used in credit management if  Customer does pay back his amount, then using this dunning
Procedure Company sends reminders to customer then after
That company has to take legal action.

56. What is client requirement in Schedule Line Category?

Schedule line category is nothing but delivery date and Delivery quantity is must.

57. In how many places we can block the Sales Document?

Sales document can be blocked at three places depending on The customer risk categories, they are
1. Sales order level (high risk customer)
2. Delivery level (medium risk customer)
3. Goods issue level (low risk customer)

58. What is the Difference between Reconciliation A/C and Normal Posting A/c?
Manual entries can be posted in the normal G/L account and the same is not possible in the Reconciliation account, as
these are automatically updated.
Reconciliation Account:- This is control account for Vendor/Customer sub ledger accounts. At the time of sub ledger creation
you have to specify this account.
Special GL account:-This is also a reconciliation account, but we dont assign this account to any sub ledger accounts. we
assign this account to the above reconciliation account with special GL indicator. So that system posts the special transactions
like advances, bad debts & BOE to this account when you use special gl indicator for posting.

59. What happens if we check 'exclusive' indication in access sequence, and what happens if we do not check?
Basically access sequence finds the exact condition record in cond.table by search statuary with the help of exclusive
indication.

61. What are the 16 steps in the pricing procedure?

    Step,
    Counter,
    Condition type,
    Description,
    Form,
    To,
    Manual,
    Mandatory
    Statistics,
    Print
    Subtotal,
    Requirement,
    Alt condition type,
    Alt condition base value,
    Act key and
    Accruals.

62. Difference between plant and storage location?

A plant is a manufacturing unit and it is a place where Materials have to be kept.

Storage location is a place in plant, where in materials Has to be stored

63. Do u have any link for customer master and credit management?
We can maintain individual customer credit limit in customer Master. In t.code (fd32).we can define the total credit limit
For sales area and credit limit for individual sales area.

64. Explain about sales order cycle?

INQUIRY
QUOATATION
ORDER
DELIVERY
BILLING

65. What is the relation between sales organization and company codes?
Many to One

66.Sales order is created 1st November for 200 tooth pastes 100 brushes free of goods(2+1 free goods).At the time of
delivery on 15th November you have shortage of brushes by 40. Offer closed on 15th November. How do you solve in
this scenario?
At 15 Th Nov 40 shortage tooth paste have given 100% free  Goods discount.Cond type is R100.

67. Can one create delivery with reference to the project?

Yes.

68. What is the difference between cash sales and rush order?
In rush order if a customer places an order delivery will Take place immediately billing will be letter.

In cash sale if a customer places an order delivery and Billing will be on the same day.

69. How system picks up pricing while doing billing?

From Sales Order

70. Diff between business sale cycle nd customer sale cycles?

Contract is the business sale cycle and schedule line is the cust.sale cycle.

71. How do we control the credit checks with specific to distribution channel and division?
By assigning credit control area to specific sales area

72. CAN YOU CONFIGURE TWO DIFF FREE GOODS ITEMS FOR ONE SINGLE ITEM?
EXAMPLE- ON PURCHASING OF ITEM A U WANTS TO GIVE ITEM B & C FREE .IS IT POSSIBLE? HOW?
Yes it is possible by the exclusive free goods.

73. For the 1st 10 sales order I want to give discount, so what customization we have to do with

74. Can you delete order?

YOU CAN DELETE THE ORDER BUT THERE SHOULD NOT BE ANY TRANSCATIONS ON THE PARTICULAR ORDER.

75. MWST? Pl explains in detail.

MWST is Tax Condition Category which will be Assigned to Country IN.
76. What makes Listing & exclusion Work differently than each other?
Listing--- only the materials which is applicable to the Customers.

Exclusion--- The materials which is not applicable to the Customers

77. How to do customization of rebate processing in sap SD????

1-activate rebate in customer master data
2-selling material should be activated in MM data
3-sales org. should be activated
4-billing doc should be activated

78. Which partner function realent for credit limit?

Sold to party is relevant for credit limit

79. Name three areas/processes which use condition technique in SD?

Material determination, pricing determination, Output determination, Account determination.

80. Explain what a condition table and an access sequence are and the relationship between them?
Condition table defines the combination of fields (the key) that identifies an individual condition record.
Access sequence is a search strategy that the system uses to find valid data for a particular condition type.

81. What is a condition type? What are the two main groups of condition types?
Condition type is a representation in the system of your daily pricing activities. Fixed Amount & Percentage.

82. Which partner function is relevant when it comes to tax calculation in the sales order?
Ship*to party.

83. Where would you specify that a condition type is a discount or a surcharge?
 In Condition Type Details Screen.

84. You want to list all condition records for a certain material or a certain sales organization. How would you do that?
By creating pricing Reports.

85. Can you explain what a statistical condition is? Give an example for a statistical condition?
VPRS.

86. For what do you use customer hierarchies?

Pricing, Rebate.

87. Name the influencing factors for pricing procedure determination during sales order entry?
Customer, Sales Document Type and Sales Area.

88. Can you copy condition records? If yes, are there any restrictions?
Yes. Field specific.

89. Tax jurisdiction processing is a close link between which two modules?
 FI & SD.

90. Can you delete an invoice?

No. You can cancel it and create cancellation document

91. When you create an invoice can you carry out pricing again?
Yes.

92. From which documents can you create a Performa invoice?

Sales order or delivery.

93. When you create a credit memo request do you always have to refer to a sales order or any other previous
document?
Only sales order.

94. Can you combine orders into one invoice?

 Yes.

95. Can you split deliveries into several invoices? When would you do that? Yes. If the data from the related reference
the system will automatically split the invoice.

96. Can one business area be valid for several company codes?
 Yes.
97. There is an interface between SD and FI in invoicing. Can you think of another interface between SD and FI?
Credit check, Tax calculation, and Cost estimate. Plant

98. Can you partially settle rebate accruals?

Yes.

99. Is it possible to link R/3 projects to the MS project?

 Yes.

100. What two ways of number assignment for documents or master data do you know? Explain the difference
between them.