SAP-Configuration-Complete-ECC (Perguntas e Respostas rápidas)

c
 


SAP Introduction What is SAP Landscape



 #$ SAP Tickets - What Is That?

  
  #
")


*+,&-

What Is Maintaining SLA  

  Basic System Navigation Question SAP R3 Transaction Codes SAP R3 Tables mySAP Certification Criteria

What Are Functional Specification? Role of a SAP Functinal Consultant

 .


 /
 $$'"

 
 
 000!

  

Role of SAP Consultant In Testing  
 Material Management Logistics Execution Warehouse Management Sales and Distribution Production Planning and Control Quality Management Plant Maintenance Project System  
 Financial Accounting and Controlling  

 Personnel Management

.
 #$1 
 Roles and Responsibilities of End Extracting Data of Workflow Users Log What Are SAP End User Manual The top ten IT skills to have for the next few years Mini SAP System Requirement and How to Get It

What Is SAP Service Management PP/DS Planned Order From APO To ECC Explanation Of LSO Transaction Codes

What Is User Specific Parameter %$

  & Successfully Implementing SAP

ABAP/4 FAQ 
  - Data Dictionary SAP Basis Components - Reporting Administration In SAP - Data Modeler - Dialog Programming   !
" - SQL/Performance ABAP Programming Hints - SAPscripts BDC Programming Tips - User Exits ABAP Functions Examples - Workbench Organizer BAPI Programming - Sample Exam Questions ABAP Questions '( $$'$
   Business Information Warehouse Sapscripts Advanced Planner and Optimizer SmartForms SAP Business Workflow Handling Units Management      Document Management System

Exchange Rate Billing Documents Rebate Management Tables Used Datasource Change Owner Done By Who Options To Handle Manufacturing Materials Restrict Specific Programs In SA38 and SE38 Major Area In Extended warehouse Management Check for Partner on Equipment Master (IE01)

# Learning ABAP or SAP Application

SAP Data Migration with LSMW Production Planning Process Computer Aided Test Tool Industries Flow Customer Relationship Management Customer User Exit For Billing

 1! 

 1!


 SAP Jobs Opportunity    Links of SAP websites

Explanation Of Purchasing Info Record Re-run Released Cost Estimate For Material Network Scheduling In Project System Documenting HR Rules And Schemas Control Of Expiry Date For Inspection Retro Billing And Self-Billing



'
 Oracle Database, SQL, Application, Programming Tips Java Programming Hints and Tips Unix System Administration Hints and Tips Linux Administration Hints and Tips

SAP was founded in 1972 in Walldorf, Germany. It stands for Systems, Applications and Products in Data Processing. Over the years, it has grown and evolved to become the world premier provider of client/server business solutions for which it is so well known today. The SAP R/3 enterprise application suite for open client/server systems has established a new standards for providing business information management solutions. SAP product are consider excellent but not perfect. The main problems with software product is that it can never be perfect.

The main advantage of using SAP as your company ERP system is that SAP have a very high level of integration among its individual applications which guarantee consistency of data throughout the system and the company itself. In a standard SAP project system, it is divided into three environments, /

$
2  
 . The development system is where most of the implementation work takes place. The quality assurance system is where all the final testing is conducted before moving the transports to the production environment. The production system is where all the daily business activities occur. It is also the client that all the end users use to perform their daily job functions. To all company, the production system should only contains transport that have passed all the tests. SAP is a table drive customization software. It allows businesses to make rapid changes in their business requirements with a common set of programs. User-exits are provided for business to add in additional source code. Tools such as screen variants are provided to let you set fields attributes whether to hide, display and make them mandatory fields. #""
 
 $
3!
. The table driven customization are driving the program functionality instead of those old fashioned hard-coded programs. Therefore, new and changed business requirements can be quickly implemented and tested in the system. Many other business application software have seen this table driven customization advantage and are now changing their application software based on this table customizing concept. In order to minimized your upgrading costs, "
$!
 "!
"
$!
0 The main purpose of using a standard business application software like SAP is to reduced the amount of time and money spend on developing and testing all the programs. Therefore, most companies will try to utilized the available tools provided by SAP. "'
4""



!


'5 '4 The difference between cutomizing and configuration is: - CONFIGURATION: we will configure the system to meet the needs of your

business by using the existing data. - CUSTOMIZING: we will customise or adapt the system to your business requirements, which is the process of mapping SAP to your business process. - CLIENT: A client is a unique one in organizational structure, can have one or more company codes. Each company code is its own legal entity in finance. ' 0'5 When considering enterprise software of any type, it is important to understand the difference between configuration and customization.The crux of the difference is complexity. Configuration uses the inherent flexibility of the enterprise software to add fields, change field names,modify drop-down lists, or add buttons. Configurations are made using powerful built-in tool sets. Customization involves code changes to create functionality that is not available through configuration. Customization can be costly and can complicate future upgrades to the software because the code changes may not easily migrate to the new version.Wherever possible, governments should avoid customization by using configuration to meet their goals.Governments also should understand their vendor's particular terminology with regard to this issue since words like "modifications" or "extensions" often mean different things to different vendors. *-- $2
 "  &4 We know that SAP R/3 is software, it particular it is client-server software. This means that the groups/layers that make up a R/3 System are designed to run simultaneously across several separate computer systems. When you install Microsoft Excel on your PC, each component of Excel (printing components, graphing components, word processing components, and etc.) is stored, managed, and processed via the hardware of your PC. When a company installs SAP¶s software each component (or "layer´ in R/3¶s case) is stored, managed, and processed via the hardware of separate and specialized computer systems. Each of the various layers is capable of calling upon the specialty of any of the other installed layers in order to complete a given task. Those components/layers that are requesting services are called ³clients´, those components/layers that are providing services are called ³servers´. Thus the term 6(("
"7,"
"89"0³client/server´. "
! ''4

SAP is an ERP (Enterprise Resource Planning) module, ECC is the version of SAP, like 4.6, 4.6c and 4.7 in that series new version is ECC-6. Its known as Enterprise core component.

" $
4 By: Kunal Landscape is like a server system or like a layout of the servers or some may even call it the architecture of the servers viz. SAP is divided into three different lanscape DEV, QAS and PROD. - DEV would have multiple clients for ex: 190- Sandbox, 100- Golden, 180- Unit Test. - QAS may again have mutiple clients for ex: 300- Integration Test, 700 to 710 Training. - PROD may have something like a 200 Production. These names and numbers are the implementer's discreet on how they want it or they have been using in their previous implementations or how is the client's business scenario. Now whatever you do in the Sandbox doesn't affect the other servers or clients. Whenever you think you are satisfied with your configuration and you think you can use it moving forward, you RE-DO it in the golden client (remember, this is a very neat and clean client and you cannot use it for rough usage). As you re-do everything that you had thought was important and usable, you get a transport request pop up upon saving everytime. You save it under a transport request and give your description to it. Thus the configuration is transported to the Unit Test client (180 in this example). You don't run any transaction or even use the SAP Easy Access screen on the 100 (golden) client. This is a configuration only client. Now upon a successful tranport by the Basis guy, you have all the configuration in the Testing client, just as it is in the Golden client. The configuration remains in sync between these two clients. But in the Testing client you can not even access SPRO (Display IMG) screen. It's a transaction only client where you perform the unit test. Upon a satisfactory unit test, you move the good configuration to the next SERVER (DEV). The incorrect or unsatisfactory configuration is corrected in Golden (may again as well be practised in the sandbox prior to Golden) and accordingly transported back to 180 (Unit Test) until the unit test affected by that particular config is satisfactory.

The Golden client remains the 'database' (if you wanna call it that) or you may rather call it the 'ultimate' reference client for all the good, complete and final configuration that is being used in the implementation. %: Landscape : is the arrangement for the servers IDES : is purely for education purpose and is NOT INCLUDED in the landscape. DEVELOPMENT ---> QUALITY ----> PRODUCTION DEVELOPMENT : is where the the consultants do the customization as per the company's requirement. QUALITY : is where the core team members and other members test the customization. PRODUCTION : is where the live data of the company is recorded. A request will flow from Dev->Qual->Prod and not backwards. 1. Sandbox server: In the initial stages of any implementation project, You are given a sandbox server where you do all the configuration/customization as per the companies business process. 2. Development Server: - Once the BBP gets signed off, the configuration is done is development server and saved in workbench requests, to be transported to Production server. 3. Production Server: This is the last/ most refined client where the user will work after project GO LIVE. Any changes/ new develpoment is done is development client and the request is transported to production. These three are landscape of any Company. They organised their office in these three way. Developer develop their program in Development server and then transport it to test server. In testing server tester check/test the program and then transport it to Production Server. Later it will deploy to client from production server. Presentaion Server- Where SAP GUI have. Application Server - Where SAP Installed. Database Server - Where Database installed. ""

; ; IMG. Type in the T-Code SPRO under That got to Main Menu which is IMG. SPRO is basically used to organize the consultant customizing during the SAP Project Phrase. 
4 If we want to stop a transaction in the middle, Right click on the end button (X) on the top right corner of the window. Then select "stop transaction". As we dont have STOP icon as we have in WINDOWS, this will help in the same way.

Its a very small tip, but will help a lot. #$!:"  .
0 - Dynamic Menu - Command Field "


($
$

4 They supply defaults to R/3 fields. If a field is indicated, the system automatically fills in default value. Depending on the field definition, the entry can also be replaced with a value entered by the user. (Concept of PARAMETER ID) .
"
"



 

"
 Assign Sales area to Sales document - Combine your Sales Organisations, Distribution Channels & Divisons 2) At VOPA-->Assign Partner Determination procedure to your Account Group of Customer Master you are using. 3) At VOPA--> Assign Partner Functions to your Account Group & Partner Determination procedure 
$

A

/"



"

3
 

$
4 Follow the following steps: 1. Create a vendor account group OBD3 2. Define no. range for vendor account group XKN1 3. Assign number range to Vendor account group OBAS 4. Define tolerance Group for vendor OBA3 5. Create 2 GL accounts FS00 a) Purchases A/c b) S. creditors A/c 6. Create Vendor master data XK01 7. change/block vendor master data XK02/XK05 8. Define document type and no. range OBA7 a) KA b) KG c) KR d) KZ *-- Vandna "

$$4 Menu path for Strategy Group is: Spro --> Production --> Production Planning --> Demand Management --> Planned Independent Requirements --> Planning Strategy --> Define Strategy Group. OPPT -- Maintain Starategy Group We can see Strategy Group in Material Master Record - MRP 3 - Planning -- Strategy Group.

10 - For Make to Order 20 - For Make to Stock

# $
/#'
* "


;%
'
B
;"



4 Spro --> Sales and Distribution --> Sales --> Sales Documents --> Sales Document Item --> Define Item Category Usage Item Category Usage: item category usages which control the usage of an item. Item category usage controls, for example, the system response if during document processing an item does not refer to a material but to a text item. Item category usage can also be maintained via the item categories %


> 
"
 $"
 $

 $
"
2! 
!


""
$

"
" $$$!3
"
2"

 $"


"
0 Getting a pop-up when the Contract is going to expire is not a Standard SAP thing. For this you need to do some programming. Instead of this the Std system has a reminder system where in the open Contracts and Quotaions are popped up when you about to create a sales order. This setting is in the Sales order header , Goto -- VOV8 --- Quotation and Outline agreement messages %"


!





"

"
 
!

0 Number Rage are use to define what number to be assign to sales document type. Number range can be assign Internal or external. In internal number range system automatically assign a number to sales document according to number range define in system. In External number range user manually assign number to sales document. For Assigning Number Range use T-Code VN01

 /#'
% # : J1I2 - Prepare a sales tax register J1I3 - Create outgoing excise invoices in batches J1I5 - Update the RG 1 and Part I registers J1IEX - Incoming Excise Invoices (central transaction) J1IEX_C - Capture an incoming excise invoice (excise clerk) J1IEX_P - Post an incoming excise invoice (excise supervisor) J1IF01 - Create a subcontracting challana J1IF11 - Change a subcontracting challan J1IF12 - Display a subcontracting challan J1IF13 - Complete, reverse, or recredit a subcontracting challan J1IFQ - Reconcile quantities for subcontracting challans J1IFR - List subcontracting challans J1IH - Make a CENVAT adjustment posting J1IIN - Create an outgoing excise invoice J1IJ - Assign excise invoices to a delivery for sales from depots J1INJV - Adjust withholding tax Item J1INREP - Reprint a withholding tax certificate for a vendor J1IQ - Year-End Income Tax Depreciation Report J1IR - Download register data J1IS - Process an excise invoice (outgoing) for other movements J1IU - Process exemption forms J1IW - Verify and post an incoming excise invoice J1IX - Create an incoming excise invoice (without reference to purchase order) J2I8 - Transfer excise duty to CENVAT account J2IU - Remit excise duty fortnightly J2I9 - Monthly CENVAT return J1IG - Excise invoice entry at depot J1IGA - Create additional excise entry at depot J2I5 - Extract data for excise registers J2I6 - Print excise registers

 /
$
$
/!
,%(%-: Sales summary - VC/2 Display Customer Hierarchy - VDH2

Display Condition record report - V/I6 Pricing Report - V/LD Create Net Price List - V_NL List customer material info - VD59 List of sales order - VA05 List of Billing documents - VF05 Inquiries list - VA15 Quotation List - VA25 Incomplete Sales orders - V.02 Backorders - V.15 Outbound Delivery Monitor - VL06o Incomplete delivery - V_UC Customer Returns-Analysis - MC+A Customer Analysis- Sales - MC+E Customer Analysis- Cr. Memo - MC+I Deliveries-Due list - VL04 Billing due list - VF04 Incomplete Billing documents - MCV9 Customer Analysis-Basic List - MCTA Material Analysis(SIS) - MCTC Sales org analysis - MCTE Sales org analysis-Invoiced sales - MC+2 Material Analysis-Incoming orders - MC(E General- List of Outbound deliveries - VL06f Material Returns-Analysis - MC+M Material Analysis- Invoiced Sales - MC+Q Variant configuration Analysis - MC(B Sales org analysis-Incoming orders - MC(I Sales org analysis-Returns - MC+Y Sales office Analysis- Invoiced Sales - MC-E Sales office Analysis- Returns - MC-A Shipping point Analysis - MC(U Shipping point Analysis-Returns - MC-O Blocked orders - V.14 Order Within time period - SD01 Duplicate Sales orders in period - SDD1 Display Delivery Changes - VL22

"
 #


"

%"

"

2%"
""

 
!
"""

""

$0 /

 !"
#!
""
#('
4 Listed here are the various ways you can find the list of transaction codes and their usage: Use transaction @@(  /: Fill in the Database table name and click the Display button. - ##' table will contain all the Tcodes and - ##'# table will contain all the Tcodes with Texts. Once you entered the screen, click in Top 
(B
(#!

( /$y If you want to display all the transaction code (total - 57,048) you have to change the Fields: 3!
" to 99999 (default 500). or Simply goto transaction =@, although this tcode is to Lock/Unlock any transaction code, you can also view all the tcode available in the R/3 system from here. or Goto transaction C& There are two ways where you can find the list of transaction codes in C&. 
"@: You must be familiar with the starting characters strings for each of the R/3 application modules. Assuming you know that most Materials Management transaction codes start with . In the Fields: Transaction code, type in 6 and press the function key + The list of transaction code starting with  will be displayed.


"*: On the Top 
, click B
( (3

and the first 500 transaction will be display. If want to display all the tcodes, make sure you remembered to change the Fields: 30" right at the bottom of the screen. % $#'


 0% " "

$""#'
4 Enter Search_SAP_Menu in the command box and when the pop box appears enter, the Tcode and it will give the nodes and menu path. This is helpful only in case of SAP Menu not in case of SPRO - ie IMG.....

/


%@@/!
#!



!

@@4 To update the data of any table, go to transaction SE16N, type ³&SAP_EDIT´. It will activate SAP editing function. --Go to table and press Ctrl+ shift + F10 where you will go to table entries. Click on F8 (execute). And then select the entries that you want to edit by selecting the checkbox and goto menu Table entry - > select change. There you edit and save the entries. --You cannot edit entries in SE11 unless it contains a Table maintenance generator. So just build a Table maintenance generator. Do not delete any entries using &SAP_EDIT...it is not recommended. --You can edit through debugging.





@D4 To delete the records from particular table its easy. Goto : se11 - Give the table name - Execute the table with the selection fields - Then data (list) screen will be displayed. - Now select the record which has to be deleted - Select that and switch 'on' the Debugging mode press enter - Then press F6 goes to subroutine where there is field called display - Instead change it to edit and then save the changes then it will take you to the screen where you can edit that records & also delete that particular records. Note: After displaying the contents of the list. Switch ON the Debug Mode the select the particular record then click display then it will take u to Debug Screen when there is a program for sy-ucomm then click F7 Button and then Change Code = EDIT then save the code the afterwards it will take u to edit mode of that particular record.

%

"
!
4 Give the transaction code as se11 In that give the table name and press display Then in that field name above there is delivery and maintenance click the same and change it as display maintenance allowed

#'
#A
  #!
 ""

 
 ,

-!
2"


"
  
4 By: Riki Paramita

To browse tables which specified for PP module only, you can use @D with a $

$$$
?!($
. First, go to @D, !
 "
$$$
,
3:

-2"


"
!($
,
3:

('2  c


!
-E and all tables within the specified area will be displayed. In tcode @D, click the /  next to the #!
.
field: Then it will pop-up a screen, look at the !"


:

Then 

$
 by clicking the F to open up the sub-compenent you want. For e.g.:


$!
""



: MAST - Material BOM STKO - BOM Header STPO - BOM Positions (detail) MAPL - Assignment for Task Lists to Materials PLKO - Routing Group Header PLSO - Routing Group Sequence PLPO - Routing Group Operations

AFKO - Production Order Header AFPO -Production Order Position (details)

!

: MAKT - Material Descriptions MARA - General Material Data MARC - Plant Data for Material MARD - Storage Location Data for Material MAST - Material to BOM Link

%$#!
 / à
      YYYYYYYYYYYYYYYYYY 
    
YYYYYYYYY YYY  YY YYYYYYYYYYYYYYYYYY YYY
YYY Y YY YY   YY YYYYYYYYYYYYYYYYYY YYY
Y Y Y YYYYYYYYYYYYYYYYYY !YYY
YYY


 "Y #Y YYYYYYYYYYYYYYYYYY YYY
YY $YY YYYYYYYYYYYYYYYYYY  YYY
YY Y"Y YYYYYYYYYYYYYYYYYY YYY
YY Y  Y YYY Y YYYYYYYYYYYYYYYYYY %%YYY&Y YYYY''Y YYYYYYYYYYYYYYYYYY %(YYY
YY)*Y( Y YYYYYYYYYYYYYYYYYY %YYY Y+
 Y$Y YYYYYYYYYYYYYYYYYY %YYY,

YY YYYYYYYYYYYYYYYYYY %&YYY
YY&YY YYYYYYYYYYYYYYYYYY- YYY
.% Y- $Y YYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYY &Y
 YYY% /Y% Y0Y%/Y YYYYYYYYYYYYYYYYYY%/YYY Y&
Y Y  1YY YYYYYYYYYYYYYYYYYY% YYY&Y
 Y2Y YY YYYYYYYYYYYYYYYYYY%YYY&Y
 Y2Y
 YY YYYYYYYYYYYYYYYYYY%/YYY(Y&
Y YYYYYYYYYYYYYYYYYY% YYY&Y
 Y2Y(YY YYYYYYYYYYYYYYYYYY% YYY Y YYYYYYYYYYYYYYYYYY%+ YYY
 Y+3Y YYYYYYYYYYYYYYYYYY%4YYY&Y
 Y&
Y- Y YYYYYYYYYYYYYYYYYY%4YYY&Y56
 7Y( 1
Y5Y Y &Y1Y
-(&YYY1Y
 YYY 
Y#  "Y,Y YYYYYYYYYYYYYYYYYY-(YYY1Y
 Y YY Y  "Y
 YY%5YYY "Y
 Y Y YYYYYYYYYYYYYYYYYY%5YYY "Y
 Y(Y Y &Y& "Y/ YY%4YYY& "Y/ Y(Y   Y YYYYYYYYYYYYYYYYYY%4,YYY& "Y/ Y Y

/#
 ˜Y ˜Y ˜Y

SAP SD Transaction codes List Task Specifc SD Transaction Codes 1 Task Specifc SD Transaction Codes 2


"
$ /$!
 SAP SD Forums - Do you have a SAP SD Question?  
/!  SAP SD Books - Certification, Interview Questions and Configuration

 '
('
 $$ #"


:'
$$ '
"



>
: " 


"
 '
#


" "
"

*
 $


3$


"


 
@G

 0It needs to be the classes that SAP Ltd. arrange and accept. For example: HR400 - Payroll Configuration."

"
!
!
$


$
0

!

"
: 1. A statement from the Project Manager on Letter Head indicating participant's experience or training. 2. A resume. 3. Certificate of Attendance from the various SAP courses attended. Terms: - Candidates must meet criteria mentioned - Certification enrolment must accompany payment (credit card details preferred) before registration will be processed - Once payment is received and confirmation provided, cancellation (i.e amendment to dates) is not permitted Here is a link to check dates of certification: "$: Check the loading group of the two items. Go to Material Master, select Sales: General/Plant view and compare for both the materials what is maintained in "Trans.Grp". It should be different. Maintain unique value and then retry. Your problem will be solved.




$!



$"



0#" "
!

>

0





4 %
====*=:

$
"

,7/ :L@N(HL*- 

0A=&& / %
====*=!
"$$
"



""
"

"
 
!

"
"

,7/ -

0#"
7/ 

 ""
 
L*2!"


"


""
 
 L@0 Delivery split happens because of the customer group also. so as you want to do single delivery, assuming that stock is available for both the materials, check in the item data the schedule lines, the delivery dates of the line items 10&20 and make sure that both are being delivered on same date. And make the customer group (VBKD KDGRP ) same for line items 10 & 20 .then single delivery will happen. for both the line items Please check the below: DELIVERY SPLIT: Delivery Split depends on the following criteria: 1) Ship to party 2) Delivery date 3) Plant 4) Shipping point 5) Shipping conditions 6) Transportation group 7) Loading group 8) Item categories of materials

Delivery split happen when the requested quantity by customer is not full met, then the system proposes different delivery dates or schedule lines dates based on material availability. Example : A sales order is confirmed with 2 schedule lines i.e on 14 feb 2008 and 25 feb 2008 If the first delivery (14 feb 2008) is created and PGI is done this means on this delivery date customer has received the goods. For the second delivery date ( 25 feb 2008), here you can create delivery only on 25 feb not before this due date, this means on this date goods will reach customer after completing the transportation planning, picking, loading, packing and transit, then in system on 25 Feb we create delivery document with PGI. Partial Delivery option will be set in customer master record sales area ----> shipping-> partial deliveries.


/

%
c
 3$"
!
$
$

c
0 By: Kevin Route is determined automatically in the sales order based on: 1. Departure zone or country of the delivering plant. 2. Destination zone or country of the Ship to Party. 3. Shipping condition from the customer master. 4. Transportation group from the material master. 5. Weight Group. Follow this:Step: 1 - Define Modes of Transport Path: Spro²Logistics Execution²Transportation²Basic Transportation Function--Routes²Define Routes²Define Modes of Transport. Step: 2 - Define Shipping Types Path: Under the Same Menu path---Define Shipping Types Select New Entries and Assign the Shipping Type (e.g. Road or Train) and Assign Mode of Transport (Mdtr) and Assign Shipping type Procedure group.

Step: 3 - Define Transportation Connection Point Path: Under the Same Menu path--- Define Transportation Connection Point. Step: 4 - Define Routes and Stages. Path: Under the Same Menu path--- Define Routes and Stages. Select the New Entries and Enter the Details Then Select the Routes stages and define Step: 5 - Maintain Stages for all Routes. Path: Under the Same Menu path---Maintain Stages for all Routes. cB#/# %. #%c. Step: 6 - Define Transportation Zone Path: Spro²Logistics Execution²Transportation²Basic Transportation Function--Routes²Route Determination²Define Transportation Zone. Step: 7 - Maintain County and Transportation Zone for Shipping Point. Path: Under the Same Menu path--- Maintain County and Transportation Zone for Shipping Point. Select the Shipping point and enter the Country and Transportation Zone Step: 8 - Define Transportation Groups. Path: Under the Same Menu path---Define Transportation Groups Step: 9 - Maintain Route Determination Path: Under the Same Menu path--Maintain Route Determination. Go to Customer master data. In Address of General data. Enter the Transportation Zone id. and save You will get the route. The system takes into account the following 4 conditions for determining the Route ± a. The country and the Departure Zone of the shipping point + b. Shipping Conditions agreed in the sales document type or with the sold to party + c. Transportation Group assigned to the material + d. The country & Transportation Zone of the ship to party (in CMR) Route can be manually overwritten during a sales order processing. You can redetermine the route in the outbound delivery based on weight (weight group) provided it is allowed in the configuration of the delivery type.

Scheduling takes into account the following times ± a. Transit Time + b. Loading Time + c. Pick/Pack Time + d. Transportation Lead/Planning Time. The loading time and pick/pack time come from the shipping point whereas the transit time and transportation lead time come from the route. The system performs backward scheduling first to confirm the required quantity checking the material availability on the material availability date. If the material availability date or the transportation planning date falls before the order date, the system automatically carries out forward scheduling and will propose a future date. A delivery type can be customized to carry out rescheduling if required during the delivery processing


/

'B$
/

'   OOH/ OOH

"$


$


4 By: Chung 1) A delivery costs that are planned in a purchase order and are entered in the system (invoice). 2) A delivery costs that are not planned in a purchase order and are not entered in the system until the invoice is received. Planned delivery costs: Planned delivery costs are agreed upon with the vendor, a carrier, or a customs office before the purchase order is created. You enter them in the purchase order. Planned delivery costs can be differentiated as follows: Origin of Costs i) Freight charges ii) Customs charges Calculation of Costs i) Fixed amount, irrespective of delivered quantity

ii) Quantity-dependent amount iii) Percentage of value of the goods Unplanned Delivery Costs: Unplanned delivery costs were not agreed on in the purchase order and are not entered until the invoice is received. You can enter the unplanned delivery costs in the invoice document alongside the costs incurred. You can post unplanned delivery costs as follows: - Distribute them prorated to calculated invoice items - Post them to separate G/L accounts The system distributes the unplanned delivery costs automatically in the ratio of the value invoiced so far to the values in the current invoice. The system posts unplanned delivery costs to a separate G/L account. Therefore, the unplanned delivery costs do not debit stock accounts or account assignment objects.

"$$' 
/

 

$  
OOH3
 "

"
;"$$';


4 Shipping condition is maintained in the shipping tab under sales area data of customer master. The shipping condition is proposed from the sales document type if a shipping condition has been assigned to it. If not, the shipping condition is proposed from the master record of the sold-to party. "$$

""$

 
4 Shipping condition is maintain in Ship to Party partner function ( sales area data tab -- shipping.)

Shipping conditions will be defaulted from the CMR of SP. If a value exists in the sales document type (eg. OR) then it will have priority and will replace the value defaulted from CMR.

/
"


"
"$$

""

4 When the system search for the route it will search through route determination like this: Shipping point*(*Sales order)** and Departure Zone **(From the order shipping point*)*+Shipping condition*(*Customer master which you enter in the order*) *+Transportation Group*(*from material master which you entered in the order**)+destination zone*(*transportation zone of the Customer in the order**)->Route System will determine the shipping point in the sales order based on these selection Shipping conditions+Loading group+Plant-->Shipping point. After determining the shipping point then only the system will start to search route. But system will not search the shipping point while searching the route. So shipping conditions will not consider two times while searching the route. ""

"
"$$$4 Both the shipping condition and loading group are useful in Stock transport order. For the Customer assigned to the receiving Plant, check the Delivering Plant in Customer master record in XD02 & check the shipping point assignment in OVXC. Shipping point will be determined only if it is assigned to the plant from the config. Shipping condition and Loading group plays a vital part for shipping point determination . The combination of shipping condition (Master data of customer /Vendor) + Loading group (material master) + Plant, determines the shipping point.

"/

%/



%"

"
!"



 
0 %"


"0
>

"!"




" $ "
!"""



+G0#"
 


!
"

0
 "!
&= +G
0%"



$

 MASS Change ---> New Pricing. System will display all the re-pricing options. Select B. It will re-price all the sales orders. You can try for one or two order initially check the results and if it is OK, then you can do for others.







 %$!
"






4 "'1" As such SAP standard does not provide release strategy for sales orders similar to purchase orders. However this requirement of your can be satisfied through authorisation profiles; what I mean to say is that the sale order to be kept incomplete by the person who does not have the required authorisation & the person with proper authorisation will complete it for further processing. This is only one way of meeting your requirement. M  In order to emulate a release strategy similar to purchase orders you can use the status profile in sales documents (BS02). IMG-Sales and distribution-Sales-Sales documents-Define and assign status profile.


!
$
 Rebates Processs in SAP is divided into three components 1) Configuring Rebates 2) Setting Up Rebates 3) Managing rebate agreeeements and payments Pre-requsiistes- Check the following: 1.The payer partner needs toi have the rebate field checked in the customer master on the sales area-billing doc tab. 2.The Billing type must be marked as relevant for rebates. 3.The Sales Organisation must be marked as relevant for rebates.

Condition Technique : Rebates, use the condition technique, but distinguish themselves from pricing in applying to transactions over time, versus on a transaction basis. Rebates have their wn field catalog and their own condition table naming convention.So you could have two condition table "001" one for pricing and one for rebates, which could have different key fields. You need to use the technical names A001 For pricing and KOTe001 for rebates when you use the query type using transaction SE 16.. Use create access sequence (AS). Enter 1 in field category for rebate specific. AS after going thru the right path of maintaining access sequence for rebates. The big difference between the rebate and the pricing access sequence is that there is no exclsuion flag available for rebate related AS. This means multiple tables for an access sequence can be aplied at the same time. Rebate related condition types are identified by codnition class -C. After defining and creating condition types for rebated include them in the pricing proceedure. The requirement should be 24 here which implies that the accruals are calculated on the basis of invoice/bill. The other fields- alctyp and altcbv does not allow you to manipulate how a rebate is calculated. Also, remove the requiremnt 24, if u want to see reabtes at order time. Now payment of rebates: Payments can be maunal or in full settlement. When you do manual payments, it defines how much can be paid out during a partial settlemetn. You use partial settlement only when rebate agreement is defined for a full year but the paoyouts are supposed to happen on a monthly, quarterly or anyother specified period. These accurals are based on sales volume and when they are posted billing is created int eh follwoing manner. Provision for accruals is debited and Sales revenue is credited. When rebate credit memo is created Customer account/ is debited and Accrual provision account is credited. Also, please note that when rebates are created without dependent ona material but on customer/material you need to refer to a material for settlement. "'$
: %"
"
$!
: http://www.sap-img.com/sap-sd/rebate-process-with-ref-to-so.htm



2
!
3$%"
$!

"
 0 What exactly do you wish to know in Rebates? The total outline of the Rebate process or each and every step in the SAP system? First of all rebates are more or less discounts which are offered to customers. The rebates are based on the volume of the business the customer does with you within a specified time. for eg if the customer agrees for Rs.1 Crore worth of business with u in 1 year, then you activate your rebate porocess. if at the end of the year the customer DOES achieve the target u offer him say 2/3/4 % whatever is decided. The rebates are passed on to the customer in the form of Credit notes. The rebate can be given to the customer at one time or in installments also. This is broadly the outline of the rebate process. 0

 Note : I recomend you to study the theory part of why rebate and why not a discount. This will help you understand better. May be I can help you with rebate process.(IN -IMG) 1. define a rebate agreement type 2. define a condition type group 3. define a condition type and place this condition Type in the pricing procedure.(REQUIREMENT=24) ALSO IN THE PROCEDURE- ACCRUAL KEY = ERU YOU ALSO HAVE TO DO THE ACCOUNT DETERMINATION FOR REBATES. Once you have defined all the 3 and assignment starts. Assign the agreement type to the condition type group Assign the cond type group to the condition type. Condition technique is also used in rebates. REBATE ACTIVATION- IN CUSTOMER MASTER, SALES ORGANISATION AND FOR THE BILLING DOCUMENT. After having done this please proceed to maintain the condition record for the rebates (transaction code-vbo1)

Note: if you maintain the requirement coloumn with the requirement as 24 - the rebate will be affected in the billing document and if you dont give the requirement as 24 your rebate will be affected in the sales order. The rebate process is completed when you have created a credit memo to the customer. The document type for the partial settlement is R3. Please make sure you open two screens SO THAT YOU CAN COMPARE THE NEW ENTRIES WHAT EVER YOU'RE DEFINING WITH THAT OF THE STANDARDS or first you try with the standard condition type boo1, boo2 boo3 boo4. AFTER YOU HAVE FINISHED A COMPLETE SALES CYCLE OF CREATION ORDER , DELIVERY AND BILLING. GO TO THE CONDITION RECORD IN CHANGE MODE (VB02) AND SETTLE THE ACCOUNT PARTIALLY. I hope this will be of any help to you.



 In a simple way, 1. First you need to create a Rebate agreement. 2. Create condition record for rebate giving the rebate rate and accrual rate. 3. when the rebate relevent billing doc is generated, the rebate and accruals are determined and posted in a seperate GL account as a noted item - amount to be settled. Also it gets copied in the rebate agreement. 4. create settlement run using credit memo request and then credit memo to settle this amount with the customer. This is what the link says. " 


!
 
"
0c %%



!

""
$
 
0 I am providing some info on rebates which I know.

Rebate agreemnts is based on agreement types.Conditon records which are created like B001 and B002 are linked to the rebate agreeements specifying the rebate rate + the accrual rates.condition records specify the rebate rate and the accrual rates. Consider an example.. You decided to give a rebate of 3% to a customer whose sales vol is $1000 for a particular SO Then the rebate value is $30.. Now when you make the rebate settlement by doiing the Credit memo and you decide to pay $27, then the accounting will be generated saying 27$ paid towards rebate and 3$ is the accrual which you owe to the customer Procedure: Rebate agreement: Transaction code: VB01 When you go to VB01, choose agreement type 0002 and then in conditions give Material rebate 1 20 20 30 Now create a sales order with a material say M-11 for SOrg 1000 12 00 with QTY 6 Now check VB03 and see rebate agreemtent it will say Accruals 120 and payments 0 since your rebate is not settled still. Rebate setllement Go to VB02 enter ur sales deal no, and change the agreemetn status to B then enter Shift+F12 and enter the amount to be paid for example u say $80 Then check in rebate payments rebate doc and partial setllemetn since you have not paid in full. View the credit memo request Remove the Billing bloock Go to VA01 and put order type G2 ,,,go to create with ref and enter ur Sales order no,,,save the doc now... Then go to VF01 and enter the credit memo reqst no generated...save the doc no and go to VF02 and say release to accounting Now the final settlement will be this way

Accruals:120 Accrual reversed:80 Rebate pay:80 Amount payable:40 So the balance 40 is still the accrual This is an example how a rebate will be processed with ref to a SO with an example.  /#$!: 


!



$

" 

4 1. Create a condition by copying a a standard condition like BO03 in V/06 2. Assign this condition in the std pricing procedure with acct key as ERB and accural key as ERU - V/08 3.Create a Rebate Agreement in VBO1 (It is O = Owl and not zero). No will be generated choose 003 - Customer rebates, enter the customer code, the validity and check for the status shld be in Open, click on the conditions enter the percentage and accrual amount. You also can have scales in this. Also you need to maintain the material for the settlement 4. Create a sales order for that customer and check the rebate agreement. 5. You can see the rebate condition in the invoice only. 6. Once you have posted the invoices, then go to rebate agrrement no. clicl on verficayion and it will show the order details. 7. For settlement change the status of the rebate to B - release for the settlement. 8. Credit memo request will b generated copy the no. and go to VA02, remove the blocks if any and create an invoice (credit memo).this will show u the accrual amount. 9. In both the invoice and the credit memo check the posting - accounting document it will show u the accrual as negative. 10. Again go to rebate aggreement and check the status it will show you D - Final settlement of agreement already carried out

'

 


#"

$
 $

:

Consignment fillup (send materials to customer consignment). Here you have a consignment fillup order and a consignment fillup delivery. Consignment issue (issue materials from customer consignment to the customer). Here you have a consignment issue order, consignment issue delivery and a consignment issue invoice. (the flow is very similar to a normal OR flow, but the materials are issued from the consignment stock instead of plant stock unrestricted). Consignment return (return materials from customer ownership to customer consignment). Here you have a consignment return order, consignment return delivery and a consignment return invoice. (the flow is very similar to a normal RE flow, but the materials are returned to the consignment stock instead of plant stock returns). Consignment pickup (pickup consignment stock and move it to plant stock). Here you have a consignment pickup order and a consignment pickup delivery. Note that in consignment fillup and consignment pickup there are no invoices since there is no change of ownership for the materials.

$


4 In consignment orders you are allowing the stock to sit in your customer location. Once he informs that he used the stock you will invoice him. If he returns the stock you will accept the stock to take it back. It is defined in 4 steps. 1. Consignment fill up: Sales document type is KB Item category KBN shedule line category E1 In this step, you are not invoicing the customer. document flow is sales order ---delivery item category. It will not be relevent for billing and pricing because you are not charging money for these goods in this step. In schedule line category, you will set movement type 631 & set for availability check and TOR.

2. Consignment Issue. Once the customer informed you that he used all the goods or partial goods then you will create consignment issue for used goods. Sales document: KE Item category: KEN shedule line category: C0 or C1 Here you are invoicing the customer(because he used the goods). you are assigning the delivery documnt and billing document to the sales document. In item category, you are setting relevent for billing, pricing, special stock. In schedule line category, your setting is 633 movement type, relevent for availability check & TOR. 3. Consignment Return: Customer found that some goods are damaged or he not able to sold the goods he want to send it back. that you are creating this document. Sales document type: KR Item category: KRN Shedule line category: D0 You will assign delivery document and billing to sales document. you will create return order, return delivery, return billing. Your setting item category relevent for billing, returns, pricing, special stock. Your setting schedule line item category: 634 movement type, NO availability NO TOR. 4. Consignment Pick up: Even if you create the consignment return the goods are not come to direct to your plant. For that you need to create consignment pick up. here the owner ship is not changing so you do not need to create billing. Assign retrun delivery to sales document type. Sales document: KA Item category: KAN schedule line category: F0 & F1 Your setting item category relevent for returns. any shedule line category relevent for 632 movement type, MRP, availability check, delivery.

Now you check your plant stock. Stock will increase. Rao

*-- Ugameswara

%





'
 '








"

 !$

>"



=* /

!
10
3$

 !&+'%
( 
2

"@*

0"""


0 "

"


$"!
  

0%
$4 1.Run trans. VBN2 to first create master record for free goods as follows: Enter following information in selection screen: - Free goods type: NA00 - Sales org, distribution channel, customer # and execute. Now in next screen create the record as follows: - First select the exclusive button and verify that you are in exclusive view. (that is if you want exclusive) - Material#, Min qty - Say 34 cartons. (check in what units you want to manage) From: 34 cartons unit of measure: Free goods: 12 Pcs Unit of measure: Pcs Calcualtion type: 1 or try the other options Deliver control: Blank or any of the other options suitable to you. Now save and exit. Now run VA01 for 34 cartons and press enter. The system will automatically propose the free goods item at no additional charge. Try higher order qtys and see if the free goods qty are scaling up. If not adjust the calculation parameters in the master record screen It should be transaction VBN1. Sorry for the error. VBN2 is to change the record. VBN1 creates it.

71 If you want to give free goods to some of the customers than 1. create a customer group say 99 for FREE GOODS In Free Goods Menu: 2. add a feild catalog for CUSTOMER GROUP 3. create a condition table (free goods) say 555 only for customer group 4. create a sequence say FREE with condition table 555 5. create a condition type say FREE with 6. maintain pricing procedure say ZFREE with condition type FREE Now assign: 7. Active Free goods Determination or Assign with your sales organisation this procedure ZFREE 8. Create free goods determination with transaction code /nvbn1 for FREE with Key Csuomer Group 99 for exclusive Give customer Group say 99 and from 34 to 34 free 12

$


c
 To make optional / mandatory you can use in IMG - S&D-> Basic > Functions-> Log of incomplete Procedures => select the fields > from the tables and the system will check for them (OVA2/VUA2) To make a filed entry enabled or grey (non-entry allowed): User exits in the program MV45AFZZ-USEREXIT_FIELD_MODIFICATION This user exit can be used to modify the attributes of the screen fields. To do this, the screen fields are allocated to so-called modification groups 1 - 4 and can be edited together during a modification in ABAP. If a field has no field name, it cannot be allocated to a group. The usage of the field groups (modification group 1-4) is as follows:

Modification group 1: Automatic modification with transaction MFAW Modification group 2: It contains 'LOO' for step loop fields Modification group 3: For modifications which depend on check tables or on other fixed information Modification group 4: is not used The FORM routine is called up for every field of a screen. If you require changes to be made, you must make them in this user exit. This FORM routine is called up by the module FELDAUSWAHL. "'$
!:#
) 
 Actually suppressing fielding sales orders userwise is quite easy. We are doing it in our company. For this we use userexit FORM USEREXIT_FIELD_MODIFICATION in MV45AFZZ. Below is the sample code IF SCREEN-NAME = 'VBKD-ABSSC'. AUTHORITY-CHECK OBJECT 'ZMV45AFZZ' ID 'SCRFNAME' FIELD SCREENNAME. IF sy-subrc = 0. SCREEN-INPUT = 1. else. SCREEN-INPUT = 0. ENDIF. endif. You place the authority check object in authorization profile in the role of the users, who should have access to the field (in this case it is VBKD-ABSSC), and there assign the corresponding fields that are to be accessed via this userexit. "'$
!:"
!


""/

 c!"

2"
"
$
2"


 "

0

A1) Normaly we use batch determination at delivery level, because at the time of order material may or may not be created.for this material should be configured with batch and batch determination should be checked in sales views of material. A2) Batch Determination during order Creation. For this you need to maintain a Classes d for you Material. Depending on the Manufacturing process you can define the characteristics for your material. Ex: Purity for Medicines, Resistance for Electric Items. You need to create a class (You might have to create a new class type) which incorporates the characteristic. First Create the Characteristic Using Ct04 and then using Cl02 create the Class including this characteristic. Then in your material master Classification View Enter this class. Then Create a Batch for the particular plant and Stor Loc using MSC1N.Give the value of the characteristics in this batch. Then go to SPRO ->Logistics General ->Batch Management and maintain the Condition Technique (Procedure, Strategy Types and assignment to sales docs etc). Then Create the Batch Determination Record using VCH1.

/


!


%
 $
 /

 ""



!


"

$$


 $$$4 Item proposal and product proposal are the same. Item proposal is the list of materials and order quantities that can be copied into the sales order from the customer master data. We use VA51 to create the item proposal. Here we get a number.This number is then linked to the customer master data in the sales view. This is very commonly used. Material determination is very closely related to item proposal /product proposal and is used to swap one material for another in the sales order using the condition

technique. I have not seen Material determination procedures used in the projects I have worked.  #$!: """ Item Proposal or Product proposal: "Item proposal is same as product proposal & SAP uses the two terms interchangeably. "An item proposal is a list of materials and order quantities that can be copied into the sales order. Items can also be selected from a list and copied into a sales order." 1) Use transaction [VOV8] to configure the document type ("MS" for product proposal). 2) Use transaction [VA51] to create a proposal. 3) Enter the item proposal on the sales area data (sales tab) of the customer master record. 4) In [VA01] to create a sales order, Select Edit & propose items." Material determination: "Material determination uses the condition technique to swap one material for another when certain conditions apply. Material determination is triggered by the material entered in the line item of the sales order. Use transaction [VB11] to create a material determination condition record. And [OV12] for configuration of material determination. Material determination is useful when old product is becoming obsolete or a new product is released by the company at specific date."  #$!:


$/A' 
"A'/
0 The procedure is as follows: ˜Y ˜Y

Create a Material - KMAT type with Item category (002) Create Charateristics in CT04 - Zbike, where in values mention the Color of the bile like Red, Blue etc

˜Y

˜Y ˜Y ˜Y

˜Y ˜Y ˜Y ˜Y

Create another characteristics in CT04 - ZPrice, where directly go the additional data tab and maintain the table SDCOM and field VKOND (ABAP Dictionary it will ask for) Assign these two characteristics to a Class in CL01 - ZBikeclass ( Type 300) in characteristics tab page. Then go to CU41 Configuration profile select the material and enter the description click on the class assignment ie assign Zbikclass. Now go back to CT04 - enter Zbike -go to values- select Red- go to extras Other Dependencies - Select Procedure enter in front 10 write $self.ZPrice='Red' and save Now go back go to extras - Other Dependencies - assignments and assign relationship ( by default it will come just save) Now select Blue- go to extras - Other Dependencies - Editor - Select Procedure enter in front of 10 write - $self.ZPrice='Blue' and save Now go back go to extras - Other Dependencies - assignments and assign relationship ( by default it will come just save) Now go to VK11 - Enter VA00 (Condition)(For Std RVA001 Pricing Procedure) - enter variant Red and Blue give the rates accordingly and create *-- " L"

 the sales order.

#

! 4 "
"
$
>


3$
"4 Variant configuration is used where you have a configurable material like computer (made up of components like processor, monitor, keyboard, mouse etc). These components are called as characteristics in variant config. Again this will be having values like processor can be either P4 or P3, monitor can be 15" or 17" etc. Based on the values selected the variant pricing will happen using the condition type VA00. Possible questions you can expect are: - What is variant configuration? - What is characteristic? - What is value? - What is class? - What is configuration profile? - What is dependency and what are the types? - What is a variant table? - And the transaction codes for the above.

6((M

.!
 
%
c
 This is regarding number ranges defining and assigning tips which you can follow as below: Whenever there is a new Sales Org being created, you will be required to maintain Number Ranges for Sales Documents which are allowed for your New Sales Area. Number Ranges can be maintained Internally by the system, however it can be maintained externally also if you customize it accordingly. In Standard SAP the Transaction code for Maintaiing Number ranges externally is VN01. Defining - The same can be reached through in IMG as : Sales & Distribution->Sales-->Sales Document Header-->Define Number Ranges for Sales Documents. Here you provide the system a specific Number range as follows: Number range Key +Start Number range+ End Number Range+Current Number For Example: If you want to propose the following Number Range *1

9000076000

9000076999

0

The Current Number field will be kept zero as you are proposing new number range and no sales documents have been created on it , Obviously.. *1 is a Unique Two digit Alphanumeric Key, while proposing your key, you should ensure that it should not be there in the system as existing. If you propose a key that is there in the system or if the Number Range (Start and End Series) is there in the system already, the system will throw a message that Interval already already exists. So choose a key that is unique, and which is not there in the system. Here , by making this , you are assigning a Key to a Number Range Series. All the symbols can be used along with numbers from 0 to 9 and Alphabets from A to Z and in any order. For example: !1, ^A, BB,Z*,M2.........

Assigning - In Assigning, you assign the particular Sales Document to the Number Range you have already proposed as above. The Assigning Part is done as follows: The Two digit Alpha Numeric Key is maintained or Assigned to the respective Sales Document type in V0V8. This can also be reached in IMG by: Sales & Distribution-->Sales-->Sales Document Header-->Define Sales Document Types Locate the particular Sales Doc Type, and double click on it to display it configuration. Here you put the Two Digit Number key in the Field- "Number range External Assignment" Besides this: If a new Shipping Point is created then Delivery Number ranges are required to be maintained. Similarly, If a new Plant is created then Billing Number Ranges are required to be maintained. #$!:A
"

"/
!
'

"/
!
'

4""
$$
4


4 1. A transaction that reduces Amounts Receivable from a customer is a credit memo. For eg. The customer could return damaged goods. A debit memo is a transaction that reduces Amounts Payable to a vendor because, you send damaged goods back to your vendor. 2. Credit memo request is a sales document used in complaints processing to request a credit memo for a customer. If the price calculated for the customer is too high, for example, because the wrong scale prices were used or a discount was forgotten, you can create a credit memo request. The credit memo request is blocked for further processing so that it can be checked. If the request is approved, you can remove the

block. The system uses the credit memo request to create a credit memo. You can use credit memos in Sales and Distribution (SD) for assigning credit memo requests to the open invoices and in Financial Accounting (FI) for assigning credit memos and payments to the open invoices and carry out clearing with them. If you use both Financial Accounting (FI) and Sales and Distribution (SD), there is a 1:1 relationship between the credit memo request and the credit memo item posted in Financial Accounting (FI). As soon as you bill the credit memo request together with other sales orders, or distribute the items of one credit memo request to several billing documents, the assignment is no longer valid and the system will not process it. For credit memos, credit memo requests, and payments, you have the following assignment options: - Assignment to a single invoice - Assignment of a partial amount to an invoice - Assignment to several invoices When you post credit memos, the payment programme processes them automatically. If the credit memo is specifically related to a particular open invoice item, the payment program automatically attempts to offset the credit memo against the open item. If it is not possible to completely offset the credit memo against an invoice, you can post a debit memo to the vendor, who is to reimburse the amount. Then you can apply a multilevel dunning program. 3. Debit memo request is a sales document used in complaints processing to request a debit memo for a customer. If the prices calculated for the customer were too low, for example, calculated with the wrong scaled prices, you can create a debit memo request. The debit memo request can be blocked so that it can be checked. When it has been approved, you can remove the block. It is like a standard order. The system uses the debit memo request to create a debit memo. 4. As mentioned above, creating a credit or debit memo request enables you to create credit or debit memos based on a complaint. For this first create a sales document with the order type for a credit or debit memo request. You can create the debit or credit memo requests in the following ways: ± Without reference to an order ± With reference to an existing order Here you enter which order the complaint refers to. ± With reference to an invoice Here you enter which invoice the complaint refers to. In all cases, you specify the value or quantity that should be in the credit or debit

memo 5. You can block the credit or debit memo request from being billed in Customizing. Go to Sales -> Sales Documents -> Sales document header -> Define sales document type and select the billing block field in the billing section. This request can later be reviewed along with similar ones, - if necessary, by another department. The request for a credit or debit memo can then be approved or rejected. #$!: M


3$"%'
/
!
 1. A transaction that reduces Amounts Receivable from a customer is a credit memo. For eg. The customer could return damaged goods. A debit memo is a transaction that reduces Amounts Payable to a vendor because, you send damaged goods back to your vendor. 2. Credit memo request is a sales document used in complaints processing to request a credit memo for a customer. If the price calculated for the customer is too high, for example, because the wrong scale prices were used or a discount was forgotten, you can create a credit memo request. The credit memo request is blocked for further processing so that it can be checked. If the request is approved, you can remove the block. The system uses the credit memo request to create a credit memo. You can use credit memos in Sales and Distribution (SD) for assigning credit memo requests to the open invoices and in Financial Accounting (FI) for assigning credit memos and payments to the open invoices and carry out clearing with them. If you use both Financial Accounting (FI) and Sales and Distribution (SD), there is a 1:1 relationship between the credit memo request and the credit memo item posted in Financial Accounting (FI). As soon as you bill the credit memo request together with other sales orders, or distribute the items of one credit memo request to several billing documents, the assignment is no longer valid and the system will not process it. For credit memos, credit memo requests, and payments, you have the following assignment options: ˜Y ˜Y ˜Y

Assignment to a single invoice Assignment of a partial amount to an invoice Assignment to several invoices

When you post credit memos, the payment programmed processes them automatically. If the credit memo is specifically related to a particular open invoice

item, the payment program automatically attempts to offset the credit memo against the open item. If it is not possible to completely offset the credit memo against an invoice, you can post a debit memo to the vendor, who is to reimburse the amount. Then you can apply a multilevel dunning program. 3. Debit memo request is a sales document used in complaints processing to request a debit memo for a customer. If the prices calculated for the customer were too low, for example, calculated with the wrong scaled prices, you can create a debit memo request. The debit memo request can be blocked so that it can be checked. When it has been approved, you can remove the block. It is like a standard order. The system uses the debit memo request to create a debit memo. 4. As mentioned above, creating a credit or debit memo request enables you to create credit or debit memos based on a complaint. For this first create a sales document with the order type for a credit or debit memo request. You can create the debit or credit memo requests in the following ways: ˜Y ˜Y

Without reference to an order With reference to an existing order

Here you enter which order the complaint refers to. ˜Y

With reference to an invoice

Here you enter which invoice the complaint refers to. In all cases, you specify the value or quantity that should be in the credit or debit memo. 5. You can block the credit or debit memo request from being billed in Customizing. Go to Sales -> Sales Documents -> Sales document header -> Define sales document type and select the billing block field in the billing section. This request can later be reviewed along with similar ones, - if necessary, by another department. The request for a credit or debit memo can then be approved or rejected. Use the same Invoice Script/smartform for Credit/debit memo's INVOICE Output type : RD00 ScriptForm Name : RVINVOICE01

Driver Program Name : RVADIN01 smartform name : LB_BIL_INVOICE Smartform Driver Pgm: RLB_INVOICE

'
%
$ #$c
 3$#c0 STO is Stock Transport order. It is used for inter company transfer of goods. Plant to plant transfer and even transferring raw material to Third party contractors (Job Work). The Process is you create a STO do delivery against the STO and create a Billing Document against the STO. 
"

($ #$c
4( 

Material should exist in both the plants (Delivering & Ordering), Internal customer should be assigned to the ordering plant ( MM -> Purchasing -> Purchase Order -> Setup stock transport order -> assign the internal customer to the ordering plant and assign the Sales area of the internal customer. Tcode : c .

Assign its Sales area to the delivering plant Assign the document type and Delivery type NB and NLCC Assign the Supplying plant --> Receiving Plant --> NB Take the delivering plant and assign the sales area. Vendor master has to be created and assaign the supply source ( Delivering Plant). Create a puchase order ME21N ---> Save Delivery VL10 G ---> Calculation rule (appropriate) --> Assaign the purchase order number here and execute. Select the Delivery creation line and do the back ground process. Start the log display and see the delivery document number by the documents button Goto VL02N --> do picking and PGI --> Then do the MIGO with respect to the delivery document. Billing (Intercompany pricing conditions should be set).

%
'$
 
 3$"
%
'$
 
0 In SAP sales & distribution module, an intercompany sales occurs when the selling organization belongs to a different company code than the delivering plant. The transaction path for accessing intercompany sales billing is: IMG >> Sales and distribution >> Billing >> Intercompany billing Let us take an example to understand intercompany sales better. Suppose there are two company codes namely 1000 and 2000. A customer may place an order for goods in sales organization belonging to company code 3000. However, the goods may be manufactured by a delivering plant belonging the company code 1000. A sales order is created indicating delivering plant of company code 1000. The sales organization then invoices the customer for the materials purchased. SAP R/3 automatically creates an intercompany billing document at the same time as the customer¶s billing

document is created. This intercompany invoice is sent from the delivering plant to the selling sales organization. As a rule of thumb, when dealing with different company codes, one may find a need to transfer stock between two different company codes. However, if the stock be transferred within the same company code, there is no need for an intercompany transaction. But in case the stock is transferred between different company codes, a transfer of value occurs and is an intercompany sale. --In inter- company sales process, no PO will raise. While creating sales order, if the end user knows there is no stock on their plant, they request for their sister concern company to deliver these ordered goods to the customer directly, after delivery they will receive intercompany invoice from the delivering company code, that¶s the reason you enter delivering plant while creating sales order. Below is the inter-company check list: Check all your settings once again for creating inter-company billing: - Material should exist in both plants. - Stock will be maintained in D-Plant (Delivering). - Now Plant - R (Receiving) become the customer of Plant-D. So create a dummy customer in Plant-D's company code and sales area. - Assign this customer number to Plant -R's details & its selling sales area. - Maintain the intercomapny billing type (IV) in ur sales doc type (OR). - Assign the Plant-D to selling sales org+ dbt channel. - Maintain relevant copy controls between documents. - Determine pricing procedure for Standard (RVAA01) as well as Intercompany (ICAA01) (Note: Dummy customer's CPP, IV doc's DPP along with Delivering plant's sales area)

- Maintain the condition records for Condition type PI01- VK11 (Note: In ICAA01, you won't find any PI01 Ctype, but you'll find IV01-, if you observe the details of IV01 C.type in V/06, it has the ref Ctype as "PI01" , through which the condition record of PI01 is shared to IV01 also..) - Now create VA01, enter the required fields, in delivering plant -enter Plant-D, @ item level as well as @ header level, and save, - Create Delivery VL01n, with ref to SO, - Create Billing VF01 (with ref to DEL)--- observe bill type-F2, - Create Billing VF01 (with ref to DEL again)--observe the bill type-IV.

.
c
'
' "
"


4 By: Anuradha .
c
'
:( 
$@:
/
#$
IMG > Sales and Distribution > Sales > Sales Documents > Sales Document Header: 1. Sales Document Type: The sales document types represent the different business transactions, such as Inquiry, Quotation, Sales Order, etc. To create new sales order type, always copy as with reference to similar sales order. If possible use standard sales order. 2. Define Number Ranges For Sales Documents: Maintain number range with discussion with core team. 3. Assign Sales Area To Sales Document Types: A. Combine sales organizations / Combine distribution channels / Combine divisions: Ensure to maintain these, else Sales Order creation will give error. B. Assign sales order types permitted for sales areas: Assign only required Sales Order Types to required Sales Area. This will minimize selection of Sales Order Type as per sales area.


/
%
: 1. Define Item Categories: If possible use Standard Item Category. Incase if required to create new, copy as from standard & maintain New. 2. Assign Item Categories: If possible, use standard. Formula for deriving item category: Sales Document Type + Item Category Group + Usage + Higher Level Item Category = Item Category "


: 1. Define Schedule Line Categories: If possible use Standard Schedule Lines. Incase if required to create new, copy as from standard & maintain New. 2. Assign Schedule Line Categories: If possible, use standard. Formula for deriving Schedule Line: Item Category + MRP Type / No MRP Type. 
$*: IMG > Logistic Execution > Shipping > Deliveries > 1. Define Delivery Types: If possible use Standard Delivery Type. Incase if required to create new, copy as from standard & maintain New. 2. Define Item Categories for Deliveries: If possible use Standard Item Categories for Delivery Type. Incase if required to create new, copy as from standard & maintain New. 3. Define Number Ranges for Deliveries: Ensure to maintain number range. 
$&: IMG > Sales and Distribution > Billing > 1. Define Billing Types: If possible use Standard Billing Type. Incase if required to create new, copy as from standard & maintain New. 2. Define Number Range For Billing Documents: Ensure to maintain number range. 3. Maintain Copying Control For Billing Documents: Maintain relevant copy controls such as Sales Order to Billing, Deliver to Billing, etc. The configuration differs from scenario to scenario & requirement of the client.

/

%
c
 "





$$
!
 "


"


4

There is No storage location determination at Sales order level.. Only we can enter manually. Storage location will be determined at Delivery level only.. System does not determine storage location at sales order level. User has to indicate it at time of creating sales order. The storage location entered in the order item is copied into the outbound delivery. If no storage location for picking is specified in the order item, the system determines the storage location when it creates the outbound delivery and copies it into the delivery item. The system determines the picking location based on a MALA, RETA, MARA rule defined in the delivery type. This functionality is not available in the standard SAP. If you want the system to check the stock at a specific storage location, the storage location has to be entered manually at item level or you have to go for development so that it will be defaulted under the specific conditions specified. You have to create a Z-table and maintain the table with data under which that specific storage location has to be determined. A userexit has to be used so that it will default the appropriate storage location after checking the table. Storage loction determination in Sales order is only possible via a user exit. You cannot configure storage location into sales order: you need to use user exit MV45AFZB USEREXIT_SOURCE_DETERMIN or You can use userexit_save_document Userexit_save_document_prepare or The relevant forms to be used are: USEREXIT_MOVE_FIELD_TO_VBAK -- to default in Header. USEREXIT_MOVE_FIELD_TO_VBAP -- to default in item. User exit: MV45AFZZ ---

Standard SAP can't determine storage location at sales order level. If required to give manually. But at deliver it'll determine automatic. Do the proper settings at Delivery level: SPRO --> LOGISTICS EXECUTION --> SHIPPING --> PICKING --> DETERMINE PICKING LOCATION --> Define Rules for Picking Location Determination. If sales order level by default require, then you have to use user EXIT.

3$#"

c c$

c
 "$


4 An open sales order is where the order has not been delivered (physical goods). Open Sales order : I will explain taking an example, suppose there is an order for 100 qty and against this order, only 50 are being delivered till its delivery date . i.e. it is partially delivered. then its status will be open . because it is not fully delivered. You can check the open order status in VA02 in status tab. (double click on item and at item level chk the status) or check in transaction VA05 all the open orders. In SAP SD, the document flow will summarize the status of each document. In order, they are: 1. Sales order : once delivery has been created, the status of the order changes from "open" to "completed". 2. Outbound delivery : when items are picked and posted for goods issue, the status remains at "being processed"; the status becomes complete only when billing is done. 3. Billing document : when billing document is created and saved, and posted to accounting, the status of the delivery becomes "complete"; the status of billing becomes "complete" as well; an accounting document is created and the status is "not cleared". 4. Payments posting affects the status of the accounting document; hence, you look at table BSEG. once payment is posted with reference to this accounting document, the status becomes "cleared".


 !
"
"


$
4 Check in Transaction VA05 and in table the status filed will tell you the status of open order. Table VBAP / VBAK / VBUK (header) and VBUP (item) ""!
$
"

$ 
4 Check table VBAK / VBAP / VBRK / VBRP and VBFA you can chk the document flow. '


!


$


""$$

! $
"!



4 Yes, that sales order will be considered as complete order. not open order. Delivery will be open against which billing is not happened. 
$


4 Go to transaction VA05, here you can see list of all Sales order open for any particular sales area. You can either do mass maintenance to close all the open order by giving rejection reason. Or you can check one by one order & reject the pending item. Go to VA02, input the sale order and execute. Now select the line item and assign Reason for Rejection which you will find on the right top side. If you have not delivered any quantity, then you can delete the sales order from the tcode VA02 - Enter your doc no- in the menu bar go to sales document-then DELETE.

# %
c


 




, =@-

2
 
$0 !
"4

This is due to activation of userexit V45A0002. You need to deactivate this. Take the help from ABAPer to find the project which is assigned to the userexit and deactivate the same. or Can you also check in your SU3 Parameters whether there is any entry with Parameter ID - VAU? If some value is set for this parameter , it will be copied by default in SOLD-TOPARTY during creation of the Sales Document (VA01) You can remove this ID or clear the Value. You can also check if there is any Transaction Variant associated with your Transaction in SHD0 through which the default sold-to-party can come. --'"
$

 
"
"
!

>

"$


 
: c




2$"

>

 $"



"



"
$"

>0"




$
2"

$

 



"

0 

"
"
$$0 

$"

2$$

$ 0 
"
!
4 As long as you have not created subsequent document like delivery or invoice, you can change the sold to party in sale order either in creation mode (VA01) or in change mode (VA02). But once you created the subsequent document, you cannot change the sold to party bocz, the said field will become uneditable. --
$



""


$

4 $$



"


"
P@@P
P!P2 !!

 "




"
"


 
P*@P2
""
""



"


0 These will get redetermine -->Tax -->Price -->Frieght -->Payment terms -->Shipping conditions -->Partner (Ship to party, bill to party and Payer). -->Route. If the Sold to party is changed from 11 to 21, then the new SP (21) may be valid for some other Sales Area, may have different SH,PY &BP. So accordingly those data will change. If different SP, then Price may vary, Shipping condition may vary. So those data may change. As different SH may be different, then Route may be different, Plant may be different, and as Tax is mostly Plant dependent, so Tax may change. If SP is different PY may be different, so Payment Term, Incoterm & Credit limit may be different, so those data will be changed/redetermined accordingly.

'

/
%
c
 
: %


"
$

!

((H
0 "


"$


"

4#"

%
0 
:

Sales order takes profit center from material master view Sales: Plant/General data. Profit center is assigned in (material master record) MMR in sales orgn 2 view. If you assign there automatically it will trigger in the sales order. In the item data -> account assignment tab . This profit center is used in MMR because, once you do OR- LF- F2 for that material this material value has to trigger in the profit center in FI properly. After doing F2 and when you save a the Invoice i.e., F2, automatically an accounting document gets generated along with a profit center document also gets generated if you have assigned profit center to your MMR. %

2%

$

 *7$ ! "

$

"




0  
"

$

"

4 Check 0KEM for any sales order substitution for profit center. In general, the material master profit center defaults to profit center, but at sales order you can change the profit center otherwise check 0KEM %

""
"
%
$
"""""
  '

"

c
.c#

"


2! "$"
 
2$

$ 

"

$"

%  "$4""
%
"$

"
 
 '!


4 Please check OKB9, or Simple, It is in substitution, Go to transaction GGB1 and see under the node profit center accounting. You will see that you can substitute the profit center in the sales order using substitution.

You can define your own here. %
"

 '

"




"


 4 You can do this by transaction variant. Goto tcode SHD0, give t code as VA01. Make a transaction variant and make the fields mandatory. or Please include the Field Profit Center (PRCTR) in incompletion Procedure of Sales Order Item. So without Profit Center Entry Sales Order will be incomplete. Goto T.code OVA2 copy the procedure you are now working with and add the field vbap-Prctr. In VUP2 you can assign your new procedure to your item category.

'"
 "
"
#"

%%B$
 .

": SPRO --> IMG --> Logistics-General -->Logistics Information System --> Logistics Data Warehouse --> Updating --> Updating Control --> Settings: Sales --> Update Group --> Assign Update Group at Header Level 2
$
: Sales Org: say,1234 DstCh: Division: Customer Statistic Group: + Statistics group for sales document type: 1 and Sales Org: DstCh:

Division: Customer Statistic Group: + Statistics group for sales document type: 2 SPRO --> IMG --> Logistics-General -->Logistics Information System --> Logistics Data Warehouse --> Updating --> Updating Control --> Settings: Sales --> Update Group --> Assign Update Group at Item Level 2
$
: Sales Org: DstCh: Division: Customer Statistic Group: + Material Statistic Group: 1 Statistics group for sales document type: 1 Statistics group for the item category: 1 and Sales Org: DstCh: Division: Customer Statistic Group: + Material Statistic Group: 1 Statistics group for sales document type: 2 Statistics group for the item category: 2 Note: Once, you will maintain Settings for LIS-Update, it will update onwards transactions and will not update for already done transactions.

&  "
c
 #
c
 For third party order, either you can create the material master with item category group as BANS, so the system will automatically pick TAS in the sales order for the material or you can change the item category manually to TAS in the order. This will trigger a PR, based on the PR a PO will be generated. /
%
'
 $

IMG -> Sales and Distribution -> Sales -> Sales Documents -> Sales Document Item > Define Item category groups Defining Item Category -> Sales and Distribution -> Sales -> Sales Documents -> Sales Document Item -> Define Item Categories Item category TAS Description 3rd party with SN CM Item type Blank Completion rule Blank Special stock Blank Relevant for billing B Billing plan type Blank Billing block Blank Pricing X Statistical value Blank Revenue recognition Blank Delimit. start date Blank Business data item X Sched. line allowed X Item relev. for delivery Blank Returns Blank Weight/Vol.- relevant X Credit active X Determine cost X Aut. batch determ. Blank Rounding permitted Blank Order qty = 1 Blank Incomplete proced. 28 PartnerDetermProced T TextDetermProcedure 01 Item cat. status group 1 Screen seq. group N Status profile Blank Create PO autom. Blank Config. strategy Blank Mat. variant action Blank ATP material variant Blank Structure scope Blank Application Blank Value contract material Blank

Contract release ctrl Blank Repair procedure Blank Billing form Blank DIP profile Blank %
'
 IMG -> Sales and Distribution -> Sales -> Sales Documents -> Sales Document Item > Assign Item categories '

 MM01 1. On the screen Create Material (Initial Screen) enter the material number if External. 2. Choose Select View(s). (Basic View 1&2, Sales Views, Purchasing views and accounting views). 3. Enter the relevant data and save the material. Use material group BANS in the item material group field. '
/ '
 VK11 '
A

 XK01

""



>
c 3$ %
3$
!"

!



" ;
3$;"


"

0 #!
" !
 : Go to VF02, input the billing document and execute. From top menu bar, click on "Goto -- Header -- Foreign Trade/Customs".

There again click on "Incompleteness analysis" which will be below to "Head.text" tab so that it will take you to the areas where you need to fill in the required datas. Once you gave all the data and save, you can check the log as "Document complete". : This will resolve the issue for current Invoice; but if the same error is occurring for every Invoice, maintain default values. To get the default values for foreign trade data go to 1. IMG --> Sales and Distribution --> Foreign Trade/Customs --> Basic data for foreign trade --> Define Business Transaction Types And Default Value --> Define Default Business Type (SD) In this step maintain assignments for country/sales org/dist channel / item category / and transaction type combination. 2. IMG --> Sales and Distribution --> Foreign Trade/Customs --> Basic data for foreign trade --> Define Procedures and Default Value --> Define procedure default In this step maintain assignments with the combination of country/sales org/dist channel/division/exp.imp group/item category/ procedure. Apart from the above we need to maintain Comm./imp. code no./country of origin and region of origin at material master %.#: Go to VTFL, select your billing type and delivery type and click on blue magnifying lens on top left so that it will take you to a screen where most probably, you would be maintaining "B" for "Determ.export data". Maintain blank field there and save. Now system will not throw incomplete error message.


#
 
3
#'
 
$

3



4 If you want specific material to be added or excluded to a customer, you can do it in "Listing and Exclusion".

Here is a small note on listing and exclusion, it may be helpful. 

3: Material listing: Whatever the materials that are placed in the listing for a customer he can access to those materials only. Maintaining records for material listing: Logistics Sales and distribution Master data Products Listing/Exclusion VB01 Create Specify the condition type for listing Select the required key combination Enter the required materials in listing and save it. Material Exclusion: Whatever the materials that are placed in exclusion for a customer he cannot access those materials. 

3: Logistics Sales and distribution Master data Products Listing/Exclusion VB01 Create Specify the condition type for exclusion Select the required key combination Enter the required materials in exclusion and save it. 
">

3: SPRO Sales and distribution Basic functions Listing/Exclusion

Maintain condition tables for listing/exclusion Maintain access sequence for listing/exclusion Maintain listing/exclusion types Go to new entries and define condition types one each for listing, exclusion Procedure for maintaining listing/exclusion Define the procedure one each for listing and exclusion Activate listing/exclusion by sales document type Select the required sales document type and assign the procedure for listing and exclusion Note: 1. Listing type A001 2. Exclusion type B001 3. Procedure for listing A00001 4. Procedure for exclusion B00001


c
.!
 %/=+ %"


""$


$
0#"


$$
 /=+"

>0

/=+
""

 
!
0,!
! /

!


"

0#"



/=+" 

>2!"


!
"/=+0 /




%P
!
>
0 ""
!
"

/"/=+4 Solution: Check in Material Master - MRP3 View. Availability Check might be maintained as "01" - Daily requirement. If is, then the sales order number will not appear in MD04 list. SO number will appear for 02- Individual requirement. Fyi:

Once sales order is created - it will be appear in MD04, once delivery is created wrt: SO ( w/o PGI), then delivery number will appear, SO number will not appear. Once PGI is done against to this delivery document. Then the line item from MD04 will be deleted. To recovery / delete the inconsistent entries, you can run the prog: / ' *@ It makes sense as well that for 01, the orders on the same day are summarized. Your understanding is perfectly right. This is the reason, why you can't see the SO number in MD04 for Materials which has AC:01. In MD04- line appears as summarized requirement for the whole day, it could consist all the SO numbers on that day. So you can¶t see the SO number in this case. #"
 "
 !'"
 

3

,A-2"
 : 1. Go to the sales order. 2. Select particular line item. 3. Click on Display availability button at the bottom 4. You shall get the availability screen. 5. ON the top , click on SCOPE OF CHECK 6. You shall see that on top left section, there are two fields A) Availability Check ( eg 01, 02 etc) B) Checking rule ( A , B etc ) Your focus should be on Availability Check. If it is 02, it indicates Individual Requirement. If your availability check option is 01, it means table VBBS shall be updated with Daily ( total records / requirements )

If your availability check option is 02, then ideally table VBBE should have been updated for that sales order PS: For existing sales order that were already created, it will still shows blank as the system only copied the MRP Settings once. New sales order or new item line in the same sales order with the materials will work after MM - MRP View 3 - Availability Check had been changed to "02".


/


/ 3$
"
$



"



0 By: Micro Irrigation First determine one account group ( Trans code OBD2 ) assign number range for acct group ( Trans code OBAR ). Define partner determination procedure: IMG -> SD -> Basic Functions -> Partner Determination -> Setup Partner Determination -> Partner Determination For Sales Doc Header Click on Partner Type Go To New Entries and Define Partner Types Customer KU Vendor LI Contact Person AP Sales Employ SE Select Partner Type KU and Go To Details Icon and Maintain Partner Functions SP Sold To Party SH Ship To Party BP Bill To Party PY Payer Come Back and Click On Assign Partner Type To Sales Doc Header KU To TA Assign Partner Functions To Account Group

SP To ACC GROUP SH BP PY Same. For Sales Doc Header The Partner Functions Can Be Determined From Customer Master.


$ 
/

 

5
"
 
/

 

4 We can determine partner determination procedure by using the transaction code VOPA. In the business different people interacts to make a transaction with the business while making transactions with the business every partner performs certain roles those are called as a partner functions. Depending on the partner type every partner fulfill certain mandatory partner functions. SAP determines relevant partner functions automatically to relevant partner object type. Flow: Customer master, Sales, Delivery, Billing, Document header and items. A) Partner Types. 1) Customer(KU) He performs partner functions like Sp, Sh, Bp, Py. 2) Vendor(LI) Partner Functions (FA- Forward Agent). 3) Contact Person (AP) Partner Functions-CP. 4) Sales Employee(PE) Partner Funcitons-SE Authorized Partner to release the order Contracts are release by raising sales orders. In the business one specifies partner is authorized to enter and to release contracts.

At Header level( sales document) there is a control by which system carries out checks against partner whether he is authorized to release the contract. Partner type(KU) and Partner Functions( AA- Sold T party) to release the contracts. Aw- ship to party to release the contracts and this partner functions assigned to partner determination procedure (kab). Partners to check credit limits: We define partner functions Km-credit Manager. kb- credit representations both belongs to partner type pe(personal) Configurations settings: 1) Define Account Group( OBD2) 2) Assign Number range key to Account Group (OBAR) 3) Define partner determination procedure for customer master. a) Define partner functions Path: Img -> sd -> basic functions -> partner determination -> set up partner determination -> set up partner determination for customer master. Click on partner function control button under dialog structure Partner Function Name Partner type error sp sold to party ku 07 sh ship to party ku 07 bp bill to party ku 07 py payer ku 07 partner type Pe Km credit manager pe kb credit represent pe

09 09

b) Define partner determination procedure. c) Assign partner functions to partner determination procedure. d) Assign partner determination determination procedure to account group. e) Assign partner functions to account group. For sales document. a) Define Partner functions to sales document header

1) Define partner functions img -> sd -> basic functions -> partner determination -> setup partner determination > set up partner determination for sales document header 2) Define partner determination procedure. 3) Assign partner functions to partner determination procedure 4) Partner Determination procedure assignment.


c%$

 A bill of material (BOM) describes the different components that together create a product. A BOM for a bicycle, for example, consists of all the parts that make up the bicycle: the frame, the saddle, wheels, and so on.


 When you enter the material number of a bill of materials that is relevant for sales order processing, the system displays the material that describes the whole bill of materials as a main item. The individual components are displayed as lower-level items. There are two ways to process a bill of materials in Sales. Once you have entered a bill of material in a sales order, the system runs pricing, inventory control, and delivery processing at: - Main item level if the material is assembled, or - Component level if the material is not assembled The type of processing used by the system is determined by the 

 $ that you enter in the 


 for relevant materials.


%


 If you want the system to carry out pricing, inventory control, and delivery processing at main item level, enter   in the %

$
 of the
:
 0*

"



"
"
$. This means that the components only function as text items and are not relevant for delivery. The following graphic shows how a bill of material is processed at main item level.


'$


 If you want the system to carry out pricing, inventory control, and delivery processing at the component level, enter B in the %

$
 of the
: 
0*

"



"
"
$. In this case, only the components are relevant for delivery. During processing the system automatically creates a delivery group. The latest delivery date among all the components becomes the delivery date for the entire delivery group.

7"
c 4 %"

$
c0% 
" 4 Once you enter a material (for whch you have created a BOM thru CS01) in the sales doc another material pops under the main material line item as a sub-item (s). If it doesn't then your BOM isn't working. In my experience BOMs work if all maintenance has been done properly. A number of things to check is: 1. The bom hasn't been defined for the plant used, or you haven't defined the plant in SO. 2. Main item category - has BOM application SD01 been assigned to it? 3. Item categories for main items and sub-items have not been mainteined properly. 4. Sales items maintenance - You should assign item categories for BOM header items and sub-items to a specific sales doc. 5. Has the BOM itself been configured properly (i.e. right plant, BOM usage '5')? 6. Are you trying it out on an order created after all BOM maintenance was done? 7. Also , what's the 'Structure scope' set as? Anything except C may be useful here? We have that set to A, since our BOMs are all single-level. You could set it to B if BOM are configured multi-level. Those are probably main reasons why BOM shouldn't work. Apart from that, just recheck your whole config - the truth is out there somwhere.  :

"%c

 / "!
4 By: Mike %c # %  We need to maintain Material master records for the BOM Item and for the components also. The item category group of the BOM items is µERLA/LUMF¶ and the item category is µNORM¶. Creating BOM item: - Logistics - Sales and distribution - Master data - Products - Bills of material - Material BOM CS01 create Specify the data for the following fields. Material: Specify the material for which components are to be maintained. Plant: Specify the plant of BOM item. BOM usage: Specify the application in which BOM is maintained (5 for SD). Alternative BOM: Specifies the sequence of a BOM within a group of BOMs. (L = stock item N = Non-stock item) In the overview screen specify the components which makes the main item and the corresponding quantities and save it. Note: During sales document processing if we enter the BOM item the system automatically determines corresponding components. 1) For the BOM to be exploded in the sales document the following customizing setting is required.

A) If the item category group is ERLA the item category of the BOM is TAQ, in the definition of which we have to specify the value A (Explode single level BOM) in the structure scope. B) If the item category group is LUMF the item category of the BOM item is TAP in the definition of which we have to specify the value A in the field structure scope. 2) If the item category group is LUMF the system shows price for the components but not for the BOM item. For this the following customizing setting is required. A) The item category of the BOM item is TAP which is not relevant for pricing, so the BOM item is not Priced. B) The item category of the components is TAN which is relevant for pricing, so the components are priced 3) If the item category group is ERLA the system shows price for the BOM item but not for components. For this following customizing setting is required. A) The item category of BOM item is TAQ, which is relevant for pricing, so the BOM is priced. B) The item category of components is TAE which is not relevant for pricing, so the components are not priced. While creating sales document to get the list of alternative BOMs in the definition item category of BOM item we have to check the field ³Manual Alternative´ 24-07-2007 ITEM CATEGORY DETERMINATION FOR BOM ITEM SD type

ITCaGr

OR OR OR OR OR OR OR

ERLA NORM LUMF NORM NORM NORM NORM

NOTE:

Usg

TAQ TAP TAE TAN

HLItCa TAQ TAE TAP TAN TAN TAE TAE

A ± Explode single level BOM item B ± Explode multi level BOM item

DftItCa

CS01 ± Transaction code for creating BOM Item Statistical value µx¶ or µy¶ Make TAP relevant for pricing but values for statistical only.

'5
c "
"

$5$"






 "
4 By: John You can create a sales bom, and price it at header level or sub level. If you want to assemble the products and depending upon the assemblies you want to price. For eg. if the customer asks for a certain combinationa of Material A, B and C respectively, then you create a Material Master record Material D with item category group as LUMF. While the Materials A, B and C are created with standared item category groups NORM only. Then create a sales BOM using Tcode CS01 and enter the following details: Material : Material D Plant : Plant in which you created the material. BOM Usage : 5 (Sales and Distribution) then give the Materials A, B, and C and give their respective quantities. Before you have to create pricing condition records for Materials A, B, and C. Then configure the item categories ( T - code : VOV4). When processing the sales order, just give the Material D and the system will pick up the corresponding assemblies for that material and populate in the order. The item category for the header item will be TAP and the item cateory for the items will be TAN. In this cas the Material D is called as the higher level Item , and all the assemblies are called as the sub items. Here the subitems are relevant for pricing and delivery where as the header item is not relevant for neither pricing nor delivery. It just acts as a text item. #"$
c $


0This is used when you dont know what quantities of assemblies the customer is going to order and if the price of the assembly keeps varies.

#"

"
c""$"



0The difference is that the Material Master D has to be confugured using the item category group ERLA. Creation of BOM is same. But you need to maintain the pricing condition record for the header item. The item categories in this case would be Header item : TAQ Sub item TAE; Where the header item is relevant for pricing and delivery. and subitems are not relevant for neither the pricing nor the delivery. Depending upon your requirement you configure accordingly. In Summary: -->Befor going to create sales BOM you need to create: Master data for that Header Material and Components in the MM01 transaction. -->If you want Header price you create Header Materil with ERLA Itemcategory group. -->If you want pricing at item level you create header material with LUMF Itemcategory group. -->To create Sales BOM go to the transaction CS01 there you give enter the data Header Material which you have created in the MM01 transaction. Delivering Plant. BOM Usage as '5' (Sales and Distribution) ***Then proceed with enter system will take you the BOM detail screen here you maintain the details of the components (How many components you need to make a Header material) -->Check the item category determinetion settings in the transaction VOV4. -->Maintain the Pricing procedure according to that. -->Now you can create sales order with the BOM material


& 
 '5
"
"$
: 1. Create Vendor XK01 2. Create Material ± Material Type as "Trading Goods". Item category group as "BANS". 3. Assign Item Category TAS to Order type that you are going to use. 4. A sale order is created and when saved a PR is generated at the background 5. With reference to SO a PO is created (ME21N). The company raises PO to the vendor. 6. Vendor delivers the goods and raises bill to company. MM receives the invoice MIRO 7. Goods receipt MIGO 8. Goods issue 9. The item cat TAS or Schedule line cat CS is not relevant for delivery which is evident from the config and, therefore, there is no delivery process attached in the whole process of Third party sales. 10. Billing

*-- Seema Dhar

/(&$

'


c
 VA01 Order Type Sales org, distr chnl, div Enter Sold to PO # Material Quantity Enter Save

/(&$

A
"
 "

""$
 
 VA01 Order Number Goto Item Overview Item ->Schedule Item /(&$

A
"
 "

 ME52N Key in the PR number Save /(&$

 "
 "



 c ME57 Key in the PR number Toggle the "Assigned Purchase Requisition" Execute Check the box next to the material Assign Automatically button Click on "Assignments" button Click on "Process assignment" The "Process Assignment Create PO" box , enter Drag the PR and drop in the shopping basket Save /(&$




  MIGO_GR PO Number DN Number Batch tab , click on classification Serial Numbers tab Date of Production Flag Item OK Check, just in case Post Save /(&$

'

% 
MIRO Invoice Date Look for the PO , state the vendor and the Material Check the box

Clilck on "Copy" Purchase Order Number (bottom half of the screen) Amount State the baseline date Simulate & Post Invoice Number *Invoice blocked due to date variance /(&$

'




 VL01N In the order screen , go to the menu Sales Document , select "Deliver" Go to "picking" tab State the qty and save /(&$

'

!
 VF01 Ensure that the delivery document is correct in the Enter Go to edit -> Log à


'
:#'
,@-'
:
"

$"
0 ,*-"

 
%


P 
 ' 
P:


$"0 ,&-
$"!
>
/



'"
0 By : Ahmednsp Cross selling is a concept by which the business can improve the sales. By using this concept the business can offer combination material for ordered material. Ex: If the customer placed for the order for computer then computer stand can be suggested as a combination material. It can be mapped by using cross selling concept that uses condition technique. When the user raises the sales order and specifies ordered material then system automatically pup-up a box in which system displays suggested material '
:

@-/



$


: Path: - IMG - SD - Basic function - Cross selling - Define determination procedure for cross selling a) Create condition table: Here we define condition table ex: - material b) Maintain access sequence: Here we define access sequence ex: C001 and assign condition table ex:011 that we define in previous step. c) Define condition type: Here we define condition type C001 and assign it to access sequence C001 that we define in previous step. d) Maintain procedure: Go to new entries and define cross selling profile Ex: CS0001 and assign our condition type C001 that we define in the previous step. *-
Ent Str-->Defintio-->Controlling-->Maintain Controlling Area , here you can create controlling area

3$
c#" 



: *$




(%?$
'
$

 
$
$
0$
!
$
"
 
0#"
$"

%$
0 
$
% "$"


"

"


0 % 
$$
$
0'
% 
!

 !$
0"
!

"
4 By: Balaji )""$
0 The third party sales process is as under. 1) Singapore company creates an order for the singapore customer. 2) Because of the configuration settings of the sales document type, item category & schedule line category, as soon as the order is saved a PR (purchase requisition) is automatically generated. This is converted into PO (purchase order) and sent to the indan company. 3) Indian company supplies the material directly to the singapore customer. 4) Indian company sends the invoice to the singapore company. 5) Singapore company does the invoice verification in MM using tcode MIRO. 6) Singapore company raises the invoice to the singapore customer. In standard SAP, item category TAS is used for this. The schedule line category is CS. Here you can see a field 'order type' with value 'NB'. This triggers the automatic creation of the PR.

"






0 1) If you are always following a third party process for a material then you have to create the material using item category group BANS. The procurement type should be marked as external procurement (F) in MRP 2 view of the material master record. 2) If you are not always allowing third party order processing then you can create a material master record with item category group as NORM and the procurement type should be marked as (X) meaning both types of procurement (in house manufacturing

and external procurement). In the item category the billing relevance should be 'F'.

""
/


<
!


%% #"
%
,%-
$"
 
: ˜Y ˜Y ˜Y ˜Y ˜Y ˜Y ˜Y ˜Y

Sales Information System Purchasing Information System Inventory Controlling Shop Floor Information System Plant Maintenance Information System Quality Management Information System Retail Information System (RIS) Transport Information System (TIS)

Out of this SIS (sales information system ) is one. In the standard system, the following information structures are available in the Sales Information System: ˜Y ˜Y ˜Y ˜Y ˜Y ˜Y

S001 "Customer" S002 "Sales office" S003 "Sales organization" S004 "Material" S005 "Shipping point" S006 "Sales employee "

These information structures form the data basis for the respective standard analysis of the same name. In addition to the above information structures, the standard shipment also includes information structures that are used internally (S066/67 Credit Management, S060 rebate processing and S009/14 sales support). %

"
"

'# 0 ""
 
""%
0%"
 

 

0

MCTA is reading data in table S001, which will not give invoice details as this is a summation of data based on the billing date. T-code MCVV will allow you to simulate how a single invoice would update all SIS structures. You would need to create a custom SIS structure and add the invoice as a characteristic. Use S600 - S999 in the customer namespace then MCSI to execute any custom reports. Run MC22 and re-generate your info-structure (make sure you play with S001). Create new invoices and run MCTA again.

!'"
   
 !"
 "
>2 


2M$>
0 When it is converted to an order, the first availability check is carried out, as well as credit checks. The system will check stock in the plant, plus what is contained in the availability checking rule (scope of check) eg: can add POs for replenishment, purchase reqs, different planned orders, and subtract sales orders, deliveries etc already created against that material in that plant (and possibly Storage location). If there is enough stock in the plant/SLoc, the system will give you a confirmed date, or give you a date based on the production time or purchasing time from the material master. The date the system proposes is based on the customer's requested delivery date. SAP first backward schedules looking at the required delivery date, less transportation time, less transportation lead time, less pick and pack time, less production/purchase time if applicable. If the date it calculates is equal or later than today¶s date, then it will confirm the customer¶s required date. If it falls in the past, SAP will then forward schedule for today¶s date, plus the times listed above to get the date when the customer can actually have it. ATP is the single most complex part of the SD module, depending upon how PP and MRP is set up. MRP works semi-separately, depending on how it is set up. Basically, MRP looks at the demand on the plant, and if it the stock does not meet expected sales orders and deliveries, it will create a purchase requisition (outside purchase) or requirement or

planned order (for production) to cover the shortfall. When MRP is started, it will turn the PR into a PO or the requirement into a production order.

/
/

!
 !"
 /
/



!
"
 

2"
0 !
:



"
! $

"
!"
 ! "
 0 
"
"





"
0 

3$
"
!

"0%
 "


"
 !!

!0 
"""




  ""
"
 ;
>

;
"
 

,cA@&-0 
""


>

4%"!M
 

4 I also encountered this abnormally recently using material determination. In order to combat the problem, the first product substitution should be for the original material. I've illustrated this below: Original Product: ABC Substitutes: DEF, XYZ In order to perform product substitution ONLY in the case of ATP failure for product ABC, structure the Material Determination record as follows: Material Entered: ABC Substitutes: ABC DEF XYZ #"



!

 !"
 
$
 0 Availability check can be configured both at requiremnt class and at the schedule line categories level.

Whilst the availabilty check at the requirement class level via global and mandatory configuration the schedule line catgry availability check deals with the order. It is mandatory that the reqmnt class is flagged off for avlblty check and the schdelu line cat need not be. The following are the mandatory for Availability check to happen-1. Must be swithced on at the requirment class level and at the schedule line level. 2. Reqmnt type must exist by which a requiremnt class can be found 3. There must exist a plant and is defined 4.Checking group must be defined in Material Master records(it controls whthr the system is to create individual or collective reqmnt) A combination of checking gropup and checking rule will determine the scope of availbaility check.

'
$


/

 Material Determination is used to swap one material for another.It is possible to get a list of materials for substituiton,but remember you can substitue only one material from the list. This can be done through substituiton reason T Code [OVRQ] See the substitution reason number for Manual Material Selection - check the Entry box - check the Warning box - select A for Stategy - save. Go To VB11 to create Material Determination (taking into consideration that all the previous steps for material determiantion i.e. maintaining condition types,maintaining procedures for material determination and assigning procedures to sales doc. types have been done) Create one material determination,dont forget to give the Subst reason on top and also on the line. Click the Variants Icon on top left-Sreen opens

Specify different materials you want to swap with the material you have enterd Note that the subst reason is already copied on the screen Remember materials should be of the same sales area,atleast Divisions should be same.

 "
 Backward scheduling is the calculation of deadline dates: the arrival time at the customer site is calculated as the earliest possible goods receipt time at the customers unloading point on the requested delivery date. All four of the delivery and transportation scheduling lead times are subtracted from the customer's requested delivery date to determine if this date can be met. The transit time, loading time, and pick/pack time are subtracted from the customer¶s requested delivery date to calculate the required material availability date. The system calculates backward scheduling as follows: Requested delivery date minus transit time = Goods issue date Goods issue date minus loading time = Loading date Loading date minus transportation lead time = Transportation scheduling date Loading date minus pick/pack time = Material availability date By default, the system will calculate delivery dates the closest day, taking into consideration the working days of the shipping point and a rounding profile. In this case the system assumes a 24 hour work day and lead times can be entered in days up to 2 decimal points. This is referred to as daily scheduling. Precise scheduling calculated down to the day, hour and minute is supported. This allows the scheduling of a delivery within a single day. It is activated by maintaining the working hours for a particular shipping point. Backward scheduling is always carried out first. If the material availability date or transportation scheduling date is calculated to be in the past, the system must then use forward scheduling. Forward scheduling is also done if no product is available on the material availability date calculated by backward scheduling. The system does an availability check to determine the first possible date when product will be available. This new material availability date forms the starting point for scheduling the remaining activities. The

loading time, pick/pack time, transit time, and transportation lead time are added to the new material availability date to calculate the confirmed delivery date. *-- Manoj Mahajan

' !'"
 #""'"
  $ 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.

 c
 
B'c=DA8A* "
"



!


'c=DA8A*4"

!
! 
 
"
0 CO06 - Material - Back order Processing (rescheduling program SAPLATP4) V_RA - SD Document - Backorder Processing (rescheduling program SAPMV75B) V_V2 - Execute Rescheduling/ Rescheduling Sales and Stock Transfer Documents: by material

The rescheduling program (SDV03V02) behind the V_V2.

'c=D
>P!
"
 %"
"

>


'c=D2!$$ ;$




"!
"
;0%


"
!

000

 

""

>P!
"
2
% "
4 Run the report SDRQCR21 for the said material/plant and then check if its confirmation from CO09 goes out or not. This report is basically is run in case of inconsistency of stock, removal of confirmation of stock and if some stock is blocked under some unwanted processes like old SO's, deliveries, STO's etc then that stock can be released via this report.

'>"


 %P
 



%

"
"


 "
>"
,
$
"


 
-0 ; "

>"

"
;"

"
 >
"



,
-0 "%

: ('



"
:*C(=C(*==C ("


:>

*C(=C(*==C >
"

30%P
 

0 To solve your issue: T. Code: VOV8 Select your Sales Doc. type and Double-Click. In Tab: Shipping, Check Box: Immediate Delivery (press F1 to read more about this functionality).

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.



#"
$
 # '"
 

"
$
 # "
 4 When we creat a sales order, we can only confirm the delivery of goods, for the required delivery date if the goods are available for all the necessary processing activities which take place before delivery. #$
 !"
 : There are 3 types of availability checks in sales document processing: 1. Check on the basis of ATP quantities (Available To Promise) 2. Check against Product Allocation 3. Check against planning. '"
 "
! # 
 The ATP quantity is calculated from the ware house stock, The planned inward movements of stocks (purchase orders, planned orders, production orders, etc) and The planned out ward movements of stock (Sales orders, delivery documents, etc.) This type of check is performed dynamically for each transaction with or without replenishment lead time (RLT).

RLT : It is the time that is needed to order or produce the requested material, the system determines the RLT according to specific times maintained in the material master record. Depending on the material type RLT can be calculated according to various time periods. For ex: In the case of trading goods it is determined according to the planned delivery time, purchase processing time and the goods receipt processing time. !"
  #: Availability is checked up to the end of Replenishment Lead Time. If the material availability data is calculated on the basis of current date to lie after the RLT, item it self can be confirmed despite insufficient stock being available. In this case the system assumes that any quantity requested by the customer can be procured by the material availability date and consider the goods to be available. Controlling availability check in sales document processing. We need to customize SD Specific settings and General Settings General Control Features: The following control elements need to be maintained in customizing and in the material master record. 1. Strategy group: The allowed planning strategies i.e. the main strategy and further possible strategies are combined in a strategy group. It is specified in the Material Master Record in MRP3 view. Note: In customizing, the strategy groups are assigned to MRP groups depending on the Plant so that the strategy group is automatically proposed in the Material Master. 2. MRP group: The MRP group combines the material from the point of material requirements planning which is specified on the MRP1 view in the Material Master Data. /$
'

: 1. Requirements class: It controls all control features for planning and is also specifies whether the availability check is to take place for materials in the SD documents on the basis of ATP quantities and whether the requirements are to be passed on. SPRO Sales and distribution Basic functions

Availability check and transfer of requirements Availability check Availability check with ATP planning or against planning Define procedure by requirement class '"
 $: Checking group controls whether the system is to create individual or collective requirements in sales and shipping process. In addition a material block for the availability check with transfer of requirements can be set here. The checking group can also be used to deactivate the availability check. SPRO Sales and distribution Basic functions Availability check and transfer of requirements Availability check Availability check with ATP planning or against planning Define checking groups Checking rule: We use the checking rule to control the scope of availability check for each transaction the SD process. Checking rule in the combination of checking group determines the scope of availability check '
"
 
SPRO Material management Purchasing Purchase order Set up stock transport order Create checking rule $
 !"
 SPRO Sales and distribution Basic functions Availability check and transfer of requirements Availability check

Availability check with ATP planning or against planning Carry out control for availability check Go to New Entries and define the scope of check in the combination of checking group and checking rule. The following elements can be involved in the availability check STOCKS: []Include safety stocks: Minimum stock at plant/ware house []Stock in transfer []Include quality inspection stock []Include Inward movement Out ward movement Purchase orders Sales requirements Purchase requisitions Deliveries Planned orders Release orders etc. Production orders If we do not check the field [] µcheck without RLT¶ the system considers RLT while checking the availability of the material Note: Blocking the material for availability check SPRO Sales and distribution Basic functions Availability check and transfer of requirements Availability check Availability check with ATP planning or against planning Define material block for other users If we check the field Block [] during the availability check of a material the users cannot make changes in the Material Master, cannot create PO, cannot create sales orders. Note: During the Material Master creation the system automatically proposes the checking group. Further the following setting is required. SPRO Sales and distribution Basic functions

Availability check and transfer of requirements Availability check Availability check with ATP planning or against planning Define checking groups default values. We need to assign the checking group to the combination of material type and plant.




/$
"%
$
#
 Scenario :- Problem with Down payment settlement using installment payment term. 1. When we create Sales order, (sales item value = 100) use payment term : 0009 (Installment Payment term, 30%, 40%, 30%). In the Billing Plan, I specify 2 records, 1st record is Downpayment request 30% of Order value, billing type is FAZ . the 2nd record is Final invoice 100%, billing type is F2. 2. Create Billing type Down payment request , it will document as Noted item in the accounting document. 3. Receive Downpayment from customer via FI screen , at this stage the asccounting document is created as following Dr. Cash/Bank 30 Cr. Advance from customer 30 4. When I create Billing document for the sales item, the down payment value will be proposed for settlement at Billing Creation, I then accept the default value of down payment clearing. The accounting document is as below Dr. AR 30 (*split AR by installment payment term) AR 40 AR 30 Cr. Sales 100 Dr. Advance from customer 30 Cr. AR 9 (DP. 30% * 30) Cr AR 12 (DP. 30% * 40) Cr AR 9 (DP. 30% * 30) It seems SAP settlement Down payment by Installment Payment term. I was wondering that is there are alternative or an option to setup the Down payment settlement independent of Installment term. I meant, I don't want to have the last 3 Credit item as above, I want only 1 line item of credit, the accounting should be

Dr. AR 30 (*split AR by installment payment term) AR 40 AR 30 Cr. Sales 100 Dr. Advance from customer 30 Cr. AR 30 (Not separate by Installment payment term) Solutions : Suggesstions on how I could proceed? Your problem with Down payment settlement is common. Many users object to the down payment or security lodgement mechanism. In our case we often park and apply the advance manually to final invoice. However, following the above case we sometimes use this with our PS orders: 1. Create Sales order, (sales item value = 100) with billing plan with three steps 30% down payment,30% std billiing on order completion and 70% on delivery. A little different to your original Billing Plan, but 1st record is Downpayment request 30% of Order value, billing type is FAZ . the 2nd & 3rd records are std F2 invoices 30% ,70%. 2. Create Billing type Down payment request , it will document as Noted item in the accounting document. 3. Receive Downpayment from customer via FI screen , at this stage the accounting document is created as following :Dr. Cash/Bank 30 Cr. Security deposit payment 30 ( In many countries this may be subject to TAX laws) 4. Create the First Billing documents , the down payment value will be proposed for settlement at Billing Creation, then accept the default value of down payment clearing as these equal each other. The accounting document is as below Dr. AR 30 Cr. Sales 30 Dr. Advance from customer 30 Cr. AR 30 5. Create the Second Billing document ( down payment value has expired and will not be proposed) The accounting

document is as below is then standard for the last installement. Dr. AR 60 Cr. Sales 60 This alternative provides a cleaner option with the Downpayment.


/!(B$'  A@+#'%("%$B$'  After executing the program, you have to use SM35 to process the update program. Envirionment : 4.6x Require flat file :ROW 1 BGR00 ROW 2 BKOND1 ROW 3 BKOND2 - no scale ROW 4 BKOND2 - no scale ROW 5 BKOND3 - with scale ROW 6 BKOND2 - no scale Sample flat file for uploading table A305 - Customer/Material with release status :0BIPRICE 123SAPABAP X 1VK15 A305V PR00 2ALL 990000123456SAP8204142100 2002043020020401 50USD 100PC 2ALL 990000123456SAP8217168100 2002043020020401 50USD 100PC 3 100PC 2 3 200PC 1 2ALL 990000123456SAP8220133910 )YYY#YY#Y#Y#Y72Y  5;;Y2Y& Y Y5Y Y Y Y 22222222222222222222222222222222222222222222222222222222222222222222222222222 2222222222222Y Y

ëY+Y YëY YYYYYYYYYYëY5YYYYYYYYYëY YYYYYYëY - "YëYYYYëY Y 22222222222222222222222222222222222222222222222222222222222222222222222222222 2222222222222Y Y ëY&):4YYYYYYëY5YYYYYYYYYYYëY;YYYYYYYYYYYYYYYYYYYYëY 5YYYYYYëY ;;;;;YëY;;;;;;YëY Y ëY 5,/YYYYYYëY 
Y YYYYYYYYYYYëY(Y& Y YYYYYYëY 5YYYYYYëY ;;;;8YëY;;;;;;YëY Y ëY )YYYYYYëY  YYYYYYYYYYYYYYYëY:
Y Y YYYYYYYëY - )YYYYYYëY ;;;;;9YëY;;;;;;YëY Y ëY/& YYYYYYëY/Y(YYYYYYYYYYYYYYëYY YYYYYY()4=)DY% -/4Y>Y' Y>Y YYYYYY)4=)DY% -/4Y>Y' Y>Y Y  ) 7Y4 ( Y,+Y( & @Y, /5&Y!;Y YYYYYYYY( -/4Y&)5/ )/54Y & @Y  ) 7Y4 Y,+Y( & @Y Y  ) 7Y4 ( Y,+Y() Y, /5&Y;Y YYYYYYYY( -/4Y&)5/ )/54Y & @Y

 ) 7YYY/ )4Y-(4Y  52/ )4Y YYYYYYYY/&45 4Y-(4Y  52/&45 4Y YYYYYYYY 4 5Y-(4Y  52 4 5Y YYYYYYYY%4- ;Y YYYYYYYY,& 5DY YYYYYYYY4)4 5Y YYYYYYYY( )4=)8;;Y YY4 Y,+Y() Y Y &4-4 )Y„Y+5,Y%/Y@ 454Y%4- Y( Y=%4- Y YY -4 5Y  5Y YY -4 5Y ,&Y YY  52,E4 ) - &Y?Y>%454-4 >Y YY  52,E4 )(YYY?Y%/2%4- Y YY45+,5Y54  4 45Y YY45+,5Y54 ,&Y YY-,,Y )Y() Y YYYY &4Y() 2)  4Y YYYYYY@ 4 Y>% >Y YYYYYYYY(+Y() 2+ 4Y?Y>/ 5>Y,5Y YYYYYYYYYYY() 2+ 4Y?Y>-(+ 5>Y,5Y YYYYYYYYYYY() 2+ 4Y?Y> 5 5>Y,5Y YYYYYYYYYYY() 2+ 4Y?Y>45 5>Y,5Y YYYYYYYYYYY() 2+ 4Y(&Y( ()( -Y YYYYYYYYY,%4Y() 2) 4:Y),Y% Y YYYYYYYYY&4-4 )Y&( -4Y„Y+5,Y) 5)Y@ 454Y&5 &Y?Y&:2- /Y YYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYY YYY 5%@Y?Y% 2 5%@Y YYYYYYYYY(+Y&:2&/5 Y?Y;Y YYYYYYYYYYY54- 4Y>F>Y@() Y) 5)2%)4=)Y( ),Y() 2( )4=)Y YYYYYYYYY4 (+Y YYYYYYY4 (+Y YYYYY@ 4 Y>% >Y YYYYYYY(+Y() 2+ 4Y(&Y( ()( -Y YYYYYYYYY54- 4Y>F>Y@() Y>(>Y( ),Y() 2( )4=)Y YYYYYYY4 (+Y YYYYY@ 4 Y>, % >Y YYYYYYY,%4Y() 2) 4:Y),Y, % Y YYYYYYY&4-4 )Y&( -4Y„Y+5,Y)DC!)Y@ 454Y&5 &Y?Y&:2- /Y YYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYY YYY%4@4Y?Y> >Y YYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYY YYY -Y?Y>%>Y YYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYY YYY& -Y?Y, % 2& -Y YYYYYYY(+Y&:2&/5 Y?Y;Y YYYYYYYYY54- 4Y>F>Y@() Y)DC!)2%)4=)Y( ),Y() 2( )4=)Y YYYYYYY4 (+Y YYYYY4  &4Y YYYYY(+Y() 2( )4=)Y4F>Y YYYYYYY54- 4Y>F>Y@() Y() 2+)4=);Y( ),Y() 2( )4=)Y YYYYY4 (+Y YYYYY(+Y() 2 ( Y?Y>(>Y YYYYYYY54- 4Y>G>Y@() Y()4=)Y( ),Y() 2( )4=)Y YYYYY4-&4(+Y() 2 ( Y?Y>/>Y YYYYYYY54- 4Y>G>Y@() Y/)4=)Y( ),Y() 2( )4=)Y YYYYY4-&4Y YYYYYYY54- 4Y>G>Y@() Y)4=)Y( ),Y() 2( )4=)Y YYYYY4 (+Y YYYYY , 4 &4Y() 2( )4=)Y YYYYY,(+:Y() Y

YYY4 -,,Y 4 &4-4 )Y Y (+Y&/ )4Y?Y>=>Y YY&,5)Y() Y:Y/ )4Y%4- Y,& 5Y4)4 5Y 4-&4(+Y&,(Y?Y>=>Y YY&,5)Y() Y:Y%4- Y,& 5Y4)4 5Y/ )4Y 4-&4Y YY&,5)Y() Y:Y/&45 4Y%4- Y,& 5Y4)4 5Y/ )4Y 4 (+Y Y -,,Y )Y() Y YY -4 5Y@+- Y YY(+Y&/ )4Y?Y>=>Y YYYY(+Y@/ )4Y 4Y() 2/ )4Y YYYYYY&(Y YYYYYY@5()47.;;Y() 2/ )4Y YYYYYYYYYYYYY;89Y() 2/&45 4Y YYYYYYYYYYYYY;9H;Y() 2%4- Y YYYYYY@+- Y?Y>=>Y YYYYYY@/ )4Y?Y() 2/ )4Y YYYYYY@ 4 5Y?Y() 2 4 5Y YYYY4 (+Y YY4-&4(+Y&,(Y 4Y>=>Y YYYY(+Y@%4- Y 4Y() 2%4- Y YYYYYY&(Y YYYYYY@5()47.;;Y() 2%4- Y YYYYYY@%4- Y?Y() 2%4- Y YYYY4 (+Y YY4-&4Y YYYY(+Y@ 4Y 4Y() 2/&45 4Y YYYYYY&(Y YYYYYY@5()47.;;Y() 2/&45 4Y YYYYYY@ 4Y?Y() 2/&45 4Y YYYY4 (+Y YY4 (+Y YY(+Y@ 4 5Y 4Y() 2 4 5Y YYYY@5()47.;89Y() 2/&45 4Y YYYYYYYYYYY;9H;Y() 2%4- Y YYYYYYY@+- Y?Y>=>Y YYYYYYY@ 4 5Y?Y() 2 4 5Y YYYY4 (+Y YYYY(+Y@+- Y?Y>=>Y YYYYYY@5()47Y;9Y() 2 ( Y YYYYYYYYYYYYY;IY() 2,& 5Y YYYYYYYYYYYYY;!HY() 24)4 5Y YYYYYYYYYYYYY;D!Y() 2( )4=)D;Y YYYY4-&4Y YYYYYY@5()47Y.;9Y() 2 ( Y YYYYYYYYYYYYYY;IY() 2,& 5Y YYYYYYYYYYYYYY;!HY() 24)4 5Y YYYYYYYYYYYYYY;D!Y() 2( )4=)D;Y YYYY4 (+Y YY@5()47.;D!Y() 2+B,-Y YY@5()47.;D!Y() 2+B 4@Y 4 -,,Y Y

+,5Y54  4 45Y YY --Y+/ )(, Y> 4, /4 )B54 B 4 45&>Y YYYYYYY4=,5)( Y YYYYYYYYYYYY )4B,+B 4YYYY?Y  52/ )4Y YYYYYYYYYYYY,E4 ) - &&YYYYYYY?Y  52,E4 ) - &Y YYYYYYYYYYYY,E4 )(YYYYYYYYYY?Y  52,E4 )(Y YYYYYYYYYYYY)(4B,+B 4YYYY?Y  52/)(4Y YYYYYYYYYYYY/&45 4YYYYYYYYYY?Y  52/&45 4Y YYYYYYY) -4&Y YYYYYYYYYYYY(B  5YYYYYYYYYYY?Y(  5Y YYYYYYY4= 4)(, &Y YYYYYYYYYYYY ,B,&()(, B+,/ Y?YY YYYYYYYYYYYY,) 45&YYYYYYYYYYYY?Y8Y Y YY &4Y&:2&/5 Y YYYY@ 4 Y>;;;;>Y YYYY@ 4 Y>;;;>Y YYYYYY4&& 4Y&9Y YYYYYY-4 %4Y YYYY@ 4 Y>;;;8>Y YYYYYY4&& 4Y&9Y YYYYYY-4 %4Y YY4  &4Y 4 +,5Y Y +,5Y54 ,&Y YY-,,Y )Y(  5Y YYYY 4 Y(  52/ )4Y YYYYYYYYYYYYYYYYYYYYYYYY( Y=/ )4Y YYYY 4 Y(  52/&45 4Y YYYYYYYYYYYYYYYYYYYYYYYYYY( Y= 4Y YYYY --Y+/ )(, Y> 4, /4 )B54 B,&()(, &>Y YYYYYYYYY4=,5)( Y YYYYYYYYYYYYYY 4 /45YYYYYY?Y(  52 4 5Y YYYYYYYYYYYYYY) -44:YYYYYYYYYY?Y ,&2) 4:Y YYYYYYYYYYYYYY) -4 4YYYYYYYYY?Y ,&2)  4Y YYYYYYYYY(,5)( Y YYYYYYYYYYYYYY 4 45YYYYYYYYYYYY?Y  5Y YYYYYYYYY) -4&Y YYYYYYYYYYYYYY4(),&YYYYYYYYYYY?Y( & @Y YYYYYYYYY4= 4)(, &Y YYYYYYYYYYYYYY ,B,&()(, B+,/ Y?YY YYYYYYYYYYYYYY,) 45&YYYYYYYYYYYY?Y8Y YYYY &4Y&:2&/5 Y YYYYYY@ 4 Y>;;;;>Y YYYYYYYY-,,Y )Y( & @Y YYYYYYYYYY 4 Y( & @2 ( Y 4Y>4>Y YYYYYYYYYY -4 5Y() Y YYYYYYYYYY,%42 ,554&, ( Y(  5Y),Y() Y YYYYYYYYYY,%42 ,554&, ( Y( & @Y),Y() Y YYYYYYYYYY &4Y() 2)  4Y YYYYYYYYYYYY@ 4 Y>, % >Y YYYYYYYYYYYYYY,%4Y(  52,E4 )(Y),Y() 2%4- Y YYYYYYYYYYYYYY,%4Y( & @2) 4:DY),Y() 2,& 5Y YYYYYYYYYYYY@ 4 Y,) 45&Y YYYYYYYYYYYYYY,%4Y( & @2) 4:09;YY),Y() 2%4- Y YYYYYYYYYYYYYY,%4Y( & @2) 4:09DYY),Y() 2,& 5Y

YYYYYYYYYYYYYY,%4Y( & @2) 4:0IYY),Y() 24)4 5Y YYYYYYYYYY4  &4Y YYYYYYYYYY,%4Y>FYG>Y),Y() 2( )4=)Y YYYYYYYYYY 4 Y() Y YYYYYYYYYY -4 5Y() Y YYYYYYYY4 -,,Y YYYYYY@ 4 Y,) 45&Y YYYYYYYY4&& 4Y&9Y YYYYYYYY-4 %4Y YYYY4  &4Y YY4 -,,Y 4 +,5Y Y Y ),2,+2 4Y @5()47.Y&:2 )/&:2/A4()Y YYYYYYY!;Y>& -4&Y,545Y 4Y (&),5:>Y YYYYYY8;Y>">Y&:2 ,Y @5()47Y.Y&:254(Y YYYYYYYYYD;Y>& -4&Y,545&Y&) )(&)( &>Y &(Y /-( 4Y (+Y&/ )4Y?Y>=>Y YY@5()47.;;Y>  "Y>Y YYYYYYYYY;9Y>)>Y YYYYYYYYY;89Y>/Y >Y YYYYYYYYY;9HY>&Y,>Y YYYYYYYYY;IY>- >Y YYYYYYYYY;!HY>&Y >Y YYYYYYYYY;D!Y>  ">Y 4-&4(+Y&,(Y?Y>=>Y YY@5()47.;;Y>&Y,>Y YYYYYYYYY;9Y>- >Y YYYYYYYYY;8Y>&Y >Y YYYYYYYYY;8IY>  "Y>Y YYYYYYYYY;Y>)>Y YYYYYYYYY;!Y>/Y >Y YYYYYYYYY;D!Y>  >Y 4-&4Y YY@5()47.;;Y>/Y >Y YYYYYYYYY;!Y>)>Y YYYYYYYYY;8!Y>  "Y>Y YYYYYYYYY;9HY>&Y,>Y YYYYYYYYY;IY>- >Y YYYYYYYYY;!HY>&Y >Y YYYYYYYYY;D!Y>  ">Y 4 (+Y /-( 4Y

*--- End of Program All the site contents are Copyright © www.sap-img.com and the content authors. All rights reserved. All product names are trademarks of their respective companies. The site www.sap-img.com is in no way affiliated with SAP AG. Every effort is made to ensure the content integrity. Information used on this site is at your own risk.

The content on this site may not be reproduced or redistributed without the express written permission of www.sap-img.com or the content authors.

B
3
/! "

"
B
3
/!"4 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. This IMG step describes additional installation-specific processing in sales document processing. In particular, the required INCLUDES and user exits are described. Involved program components System modifications for sales document processing affect different areas. Depending on the modification, you make the changes in the program components provided: - MV45ATZZ For entering metadata for sales document processing. User-specific metadata must start with "ZZ". - MV45AOZZ For entering additional installation-specific modules for sales document processing which are called up by the screen and run under PBO (Process Before Output) prior to output of the screen. The modules must start with "ZZ". - MV45AIZZ For entering additional installation-specific modules for sales document processing. These are called up by the screen and run under PAI (Process After Input) after data input (for example, data validation). The modules must start with "ZZ". - MV45AFZZ and MV45EFZ1 For entering installation-specific FORM routines and for using user exits, which may be required and can be used if necessary. These program components are called up by the modules in MV45AOZZ or MV45AIZZ.

You will find all User Exits on Sales and Distribution along with functionality.

'
B
3 "
"


3!



4 „




  

  

 
  
  USEREXIT_NUMBER_RANGE (Module pool SAPLV60A, program RV60AFZZ) The internal number range used in the standard system is specified in the billing type table and can be changed in this user exit. This user exit is only called when the billing documents is created. USEREXIT_ACCOUNT_PREP_KOMKCV (Module pool SAPLV60A, program RV60AFZZ) In this user exit additional fields for account determination that are not provided in the standard system are copied into communication structure KOMKCV (header fields). USEREXIT_ACCOUNT_PREP_KOMPCV (Module pool SAPLV60A) In this user exit additional fields for account determination that are not provided in the standard system are copied into communication structure KOMPCV (item fields). USEREXIT_NUMBER_RANGE_INV_DATE (Module pool SAPLV60A, program RV60AFZC) Depending on the number range, table TVFKD is used to set the billing date (countryspecific requirements in Italy). USEREXIT_NUMBER_RANGE is automatically deactivated when this user exit is being applied. USEREXIT_FILL_VBRK_VBRP (Module pool SAPLV60A, program RV60AFZC) This user exit is only called when the billing document is created. It is used to provide the header and the item of the new billing document with deviating or additional data. USEREXIT_PRINT_ITEM (Module pool SAPLV61A, program RV61AFZB) Printing the item line of a billing document can be supplemented or changed. USEREXIT_PRINT_HEAD (Module pool SAPLV61A, Program RV61AFZB) Printing the header line of a billing document can be supplemented or changed. User exits in program RV60AFZD Short descriptions of the user exits are contained in the program: USEREXIT_RELI_XVBPAK_AVBPAK

USEREXIT_NEWROLE_XVBPAK_AVBPAK USEREXIT_NEWROLE_XVBPAP_AVBPAK =
 

 
 
 
  „ !"  
    #  !"$% EXIT_SAPLV60B_001: Change the header data in the structure acchd You can use this exit to influence the header information of the accounting document. For example, you can change the business transaction, "created on" date and time, the name of the person who created it or the transaction with which the document was created. EXIT_SAPLV60B_002: Change the customer line ACCIT You can use this exit to change the customer line in the accounting document. This exit is processed once the ACCIT structure is filled in with data from document header VBRK. EXIT_SAPLV60B_003: Change the customer line in costing The customer line is filled in differently for costing. You can use exit 003 to influence the ACCIT structure. EXIT_SAPLV60B_004: Change a GL account item ACCIT You can add information to a GL account item (such as quantity specifications) with this exit. EXIT_SAPLV60B_005: User exit for accruals Once all relevant data for accruals was entered in the GL account item, you can add to this data with this exit. EXIT_SAPLV60B_006: Change the control line ACCIT You can use exit 006 to add information to the control line. EXIT_SAPLV60B_007: Change the installment plan You can use exit 007 to add information to the installment plan parameters in the GL account item. EXIT_SAPLV60B_008: Change the transfer structure ACCCR, ACCIT and ACCHD After the accounting document is filled in with data, you can use exit 008 to change the document once again. EXIT_SAPLV60B_010: Item table for customer lines You can use exit 10 to influence the contents of customer lines before they are created.

EXIT_SAPLV60B_0011: Change the parameter for cash account determination or reconciliation account determination You can use this exit to change inbound parameters in order to influence account determination. .
: Use enhancement "SDVFX008", Component : "EXIT_SAPLV60B_008". SDVFX008 will indeed trigger while you create accounting document through VF01 or VF02. We have done similar development to update SGTXT field in BSEG. Check whether the function exit is activated.

 
"    Let's say you want to pack a material shirt_jai in test_pack. Using MM01, create material type=packaging test_pack [SPRO] IMG-Logistics Execution-Shipping-PackingDefine Packaging Material Types Let's say JPAC. The settings that I chose: Plant determ. - Plant is entered manually in handling unit Pack. matl. cat. - Packaging materials Generate Dlv. Items - blank Number assignment - Number range interval 'HU_VEKP' IMG-Logistics Execution-Shipping-PackingDefine material group for packaging material Let's say JGRP IMG-Logistics Execution-Shipping-PackingDefine allowed packaging materials JGRP - JPAC MM02: Check settings for the materials First, test_pack

Sales:General/Plant -> Matl. Grp. Pack. Matls: JGRP (Note) Sales:General/Plant -> Packaging Mat. Type: JPAC (Note) Basic Data 1 -> Material: JMAT Then, shirt_jai Sales:General/Plant -> Matl. Grp. Pack. Matls: JGRP Sales:General/Plant -> Packaging Mat. Type: Basic Data 1 -> Material: JMAT VL01N Outbound Delivery -> Packing Enter the materials at top and at bottom (Select shirt_jai and Edit - Pack) This is how the basic process of packing works. '
 ": Jairam "
!
: http://www.geocities.com/jairam143/

#"
;   
;"3$
3$
: You created a order for a material(R-1160 - hard disks) for a qty - 120 pieces. You need to create a delivery and A)pack 40 pieces each of the material are grouped together into larger cardboard boxes (PK-100 - shipping/packing material) and B)these 3 cardboard boxes are put into pallet (PK-095). : A)Packing 40 pieces each of material (40 x 3 = 120 pieces) 1)Goto [VL02N] to change the delivery, you already created. Or you can do the following steps while you are creating a delivery also. 2)Go to "pack" icon. 3)In the upper section, enter the "packing material" (PK-100) 4)In the lower section, change the "partial quantity" to 40 of material R-1160. 5)Select both the lines of upper section and lower section and click the green ok. It generates a shipping unit/handling unit number. 6)Now, select both lines of upper & lower section & click the button "per part. qty"

(New HU per part qty of material) Check: click "General Overview" icon to see whether it packed 40 pieces of material in 3 cartons. B)Packing all 3 cartons in one big carton(PK-095) 1) from above screen, click "pack HUs" (pack shipping unit) 2)enter the packaging material (PK-095) in the upper section and select this line. 3)select 3 lines of PK-100 in lower section since you want to pack them in PK-095. 4)selecting both lines, click "pack" icon. 5)Now all the 3 cartons(PK-100 with 40 pieces each of material) are packed in one big carton (PK-095). Check: "General overview" icon. Then "save" the delivery.

/


!


'#$





3$"



!


 =@, '-7=*'
 '0 These are the condition type that will display the results of the unit costing for certain type of sales document. EK01 : 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. EK02: If you use this condition type, the result of unit costing is simply a statistical value which you can compare with the price. 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. %"

"!



 ==J ==G2% 
3
 ==J"

3*


4%"

"

3"
$
2!"
 !

$
"
%



0 %
"2 "%4 I think u need to change the validity of the condition record for the condition type K007 defining it not valid for that particular 2 months. And also the settings of the Requirements as it is correct that it overrules the exclusion.   


"
$
 
 To accumulate the amount of condition types in accounting document without affecting the pricing display in billing document. As an illustration :L KK 3500 L/KK 1000LKK 500(all condition types are shown separately in pricing view) Journal: Dr Vendor 2000 Cr Sales 2000 (L KK(L/KK(LKK) One way to do it is :Mark the condition types you want to group as statistical and remove the account assignment key. Create a subtotal in your pricing procedure that will add them together and put in the account assignment key for it. This way the individual components will still display on your pricing screen but FI will only get one posting.

 
'#$

/
 Up to now you, you still cannot exclude certain condition types and subtotal lines from being processed or displayed in the condition screen by restricting the authorizations.

You have to implement SAP Note No. @=GD*@( "5"
 "
 



'
.
  

""



$$

" "$
$4 You create PP in spro > Sales and Distribution > Basic Functions > Pricing > Pricing Control > Define and Assign Pricing Procedures > Maintain Pricing Procedures You can't attach PP to specific plant. Pricing Procedure is determined thru trx OVKK. The defining parameters for pricing procedure determination are: 1. SalesOrg 2. Distribution Channel 3. Division 4. Document Procedure (defined in Sales doc\Billing doc maintenance) 5. Pricing procedure assigned to customer (defined in customer master) Hope this helps. ! Reg pricing procedure. 1. Use transaction code v/07 to create a access sequence and assign tables based on which you want to carry on pricing as accesses. 2. Use transaction code v/06 to define condition type. It can be for base price, discount, freight etc., (Do assign relevant access sequence) 3. Use transaction code v/08 to define pricing procedure. 4. Assign this to your relevant sales area+ dpp+cupp. While specifying requirement, we can give reqt no.22 which specifies that plant has to be set. This is generally done for output taxes since output taxes depend upon the

delivering plant. But directly there is no assignment between plant and pricing procedure. Hope this helps,

";$
;?;!
 
;?;
>

 
;"
  

'

3$
3";$
;?;!
 
;;
>


;"
$$

4 The alternate base value is used as the calculation basis only, while the alternate calculation is used to modify the final value. For example, imagine you have a condition type ZZ01, with a condition record maintained (master data) for $100. Now, condition ZZ02 also exists lower in the schema, but with a rate of 10%. The standard calculation would result in a final value of $110. The alternate base value could say, "don't use $100 as the basis -- use the original price PR00 only, which was $90." Then, the final value would be $100 + (10% of $90) = $109. The alternate calculation routine says, "ignore the 10% altogether. Instead, use an externally calculated 20%." Then, you end up with a final value of $100 + (20% of $100) = $120. Put them both together, and you could end up with $100 + (20% of $90) = $118. Now once again, Alternative Calculation Type: Normally if you want to calculate a value you have to use a calculation type for determinating the value. This calculation type is either addition, subtraction or multiplication. Similarly SAP also has got a default calculation type in the control data of the condition type. There you have the options of either Qty based , Fixed Amount Based or Percentage based. Here what happens is suppose if you define Your condition type that calculates the base price of a material on Qty based. Then the calculation will be done based on the quantity of the material. If the customer orders 10 Nos and you have maintained a unit

price of 100 Rs for each material then the value determined is 1000 INR. Similarly if the discount condition type , you maintain the calculation type as %. This means if you maintain the value of 10 % in the condition record. Then this percentage is taken as the calculation type and the condition value is determined. In some cases you have to forego the default calculation types and use the customer specific method for calculating a value. For ex if you are calculating the Freight charges for a Material . it depends on so many criteria like, the weight, volume and also the minimum amount etc etc, in those cases, you forego the default value and then use the alternative calculation type in calculating the condition value against the particular condition. Alternative Condition Base value : If you have to calculate any value then you have to have a base value for it. For ex if you want to calculate the discount of 10 % for a material then you have to have a base value on which this 10% is calculated. Normally you take the condition value of the base price of the material to calculate the value. Now you don't want to take the base value and take other values as base value which are derived on some formulae. So you create a routine which will do the mathematical operations in the routine and derive you a value which is now used as the base value for calculating the condition value for a particular condition type. Requirement: A factor in the condition technique that restricts access to a condition table. The system only accesses a condition table to determine the price if the requirement specified has been met. Example: The system uses an access sequence to determine the price of a material. One of the accesses in the sequence contains the requirement "in foreign currency." The system only uses the table behind this access if the sales order for which the price must be calculated is in a foreign currency. *-- Ajay Kumar Veeranki


($ %2%!
" ( !

 Bc# #%c.4

You can always 'Update" pricing manually in a quotation the same way you do in a sales order, either in create or change modes. Menu path Edit --> New Pricing or press the 'Update pricing' button on the item conditions tab. If you are asking how to reprice a quotation when it converts into a sales order, that can be done with the copy controls of the Item Category. IMG: Sales & Dist --> Sales --> --> Maintain Copy Control for Sales Docs --> Sales Doc to Sales Doc (transaction vtaa). Just choose the combination of documents and the respective item category. The field you need to be concerned with is "Pricing type". However, from a business process perspective it makes absolutely NO sense to reprice a quotation when converting to a sales order. After all, the entire point of using quotations is to firm up details like pricing before creating the sales order.


/ 

 )P
 $

>!
+0D0)
 

$
! >
2
"
$
 >
 0 
3$
2

@$

2*$

2&2
0$ '2"
$
 Q@==0 %"


@=$

$ '2"
$
QG=0 

2">0%"

 

@@$

2@*2@&2
0"
Q@==0 #"
 
""QG="$$
@=2*=2&=2
0($
"
 ! >@=0 )"

"$!


! >@=2 "

"
"
$"

@$ 
0) $



$
$!
"
 "
$$
2

"$
3
0 )

"

!"
"2!P
M 
"

0

Taking your requirements literally. Standard SAP scale pricing will not do it in that you only want the reduced price to come into effect when the order quantity is multiple of some bulk factor. It is agreed with that creating a separate material number is not a good idea. You can try this :1. Define/Select a UOM for selling in bulk (i.e. cas, pallet, box whatever) 2. Maintain UOM conversion between your base UOM and this new UOM 3. Configure you bulk pricing condition type by usual means (it should be a base price rather than discount). 4. Place this new bulk price behind your normal "PR00" price in the pricing procedure 5. Create a new condition base value routine via VOFM where you check XKWERT to see if it is a whole number. If it is not then set XKWERT to zero. 6. Assign this new routine to your bulk price condition in your pricing procedure in ALT condition base value column. 7. Maintain bulk price conditon record in the Bulk UOM. That should do it.

/



 
""$$  )

"$$$

,"
0! "
"$($
"
-


"

$
0)

 !
""
!


2
"



 ,

>

2$
$$

-0 #"




"


$,;

; "
"$$$
-0 %"


>

2""
"$$$
P
 
7c70 '$



"
!


>

4 Structure 7c7 refers to header of the sales order, but shipping point of course is on item level. You'll have to do some settings to reach your goal, it is possible. 
$@ Append structure 7c . Do this by changing through @@ the table 7c L.

This is the include for structure 7c . Add a component e.g. ZZVSTEL with component type VSTEL. Save, activate. If you want to make more points, assign search help H_TVST to the component. Ask a programmer if you don't understand this part. 
$* Change user exit A+G LL. Say there that field ZVSTEL should be filled with information from your shipping point. Do this under part FORM B K%#8 %'%. 8  8#7c . The coding should be like tkomp-zzvstel = vbap-vstel. Save, generate. 
$& Make a new table as you did before, but first maintain your new field in Condition: allowed fields. When you create your new table you will see you have two shipping points. With the button technical view you can check which one ZZVSTEL or VSTEL. 
$+ Finish with the steps you did before. That was ok. Now, you will see in your sales order that the shipping point is filled with information.


!



Used transaction AcAI. This configuration is by order type. There is a field called $$$
. There you can select pricing date as requested delivery date. ( $
$
!
"

>

 0
,

This control is set at the document level as oppose to the condition type level (PR00). That means your other condition types such as surcharges and discounts are also determined using the requested delivery date.

If your requirement is for PR00 to alone to be priced at delivery date then this will not work.

$



"


! 
4"

"

4 The pricing date is proposed based on the setting you make in the Sales document configuration. ( T code : VOV8) You have a field" Prop.f.pricing date " in the Requested delivery date / pricing date / purchase order date segment. Then you can choose the follwoing options: Blank - Indicates the current date as the pricing date A - Indicates the date based on the requested delivery date B - Indicates the date based on the order validity start from date And the pricing in the billing document is copied from thte sales order / Delivery document.. It again depends on the setting u have in the copy control from order - billng or delivery - billing. In the copy control, in the item settings you have two fields relavant for this. One is pricing source and the other is pricing type. The pricing sources are generally the order. But if you want you can change it to other values mentioned in the drop down, but this values have no effect if the pricing type is B. Any other value other than B in the pricing type will take the reference document price mentioned in the pricing source field. but for the pricing type B. The new price is determined in the billing order.


$'"
 "


 ' 
"""
!

"
 "
 $



 ;A7@@;4 Other than "VK13", to display the price, you can use V/LD - Execute Pricing Report to check the prices entered into the Pricing Master.

Normally Pricing Report - "07 Cust.-specific Prices with Scale Display" will do. Other Pricing Reports you can tried are these: 222222222222222222222222222222222222222222222222222222222222222222222222222Y ë-5ë5YYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYëY 22Y222222222222222222222222222222222222222222222222222222222222222222222222Y ë;ë  Y#YY-Y@
Y&YYYYYYYYYYYYYYYYYYYYYYYYëY ë;8ë  Y#YY 
Y@
Y&YYYYYYYYYYYYYYYYYYYYYYYëY ë;9ë( Y3Y&YYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYëY ë;ë( Y@
Y&YYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYëY ë;!ëY-Y)Y@
Y&YYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYëY ë;DëY-Y)Y3Y&YYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYëY ë;Hë
2#YY3Y&YYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYëY ë;Cë
2#YY@.
Y&YYYYYYYYYYYYYYYYYYYYYYYYYYYYYYëY ë;IëY-.Y "Y 
Y3Y&YYYYYYYYYYYYYYYYëY ë;ë-Y. "Y 
Y@
Y&YYYYYYYYYYYYYYYYYYYYYëY ëëY 
Y@Y&YYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYëY ëë)*YYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYëY ë!ëYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYëY ëDë( 1
YYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYëY ëHë
Y Y&
"Y'Y
YYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYëY ëCë
Y Y&
"Y'YYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYëY ëIë
Y Y&
"Y'YY 
YYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYëY ë8;ë
Y Y&
"Y'YY 
YYYYYYYYYYYYYYYYYYYYYYYYYYYYëY ë8ë
Y Y&
"Y'Y
.YYYYYYYYYYYYYYYYYYYYYYYYYëY ë88ë
Y Y&
"Y'Y
.Y 
YYYYYYYYYYYYYYYYYYYëY ë89ë
Y Y&
"Y'YY 
.YYYYYYYYYYYYYYYYYYYYYYëY ë8ë
Y Y&
"Y'YY 
.Y 
YYYYYYYYYYYYYYYYëY ë8!ë% ). )=YYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYëY ë8Dë  ./& YYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYëY ë8Hë(4&Y*YYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYëY ë8Cë   Y'Y
YYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYëY ë9;ë   Y'Y
Y YYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYëY ë9ëY-Y3Y5Y&
YYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYëY ë ëYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYëY ë ëYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYëY 222222222222222222222222222222222222222222222222222222222222222222222222222Y

B$
$ You can update the condition pricing for a range of sales order. For e.g. if you create sales order for 15 months or so, and at the beginning of each year, you have to update the prices for lots of sales orders. Other than using A =* and make an Update of the conditions at item level which is a big work because you will have lots of open sales order after so many months. Use A =G, select your Orders and on the result screen :click (H'"
(H.
  (menu).

or if you don't want to do that Online, write your own abap report and use Function /8B78' .  (check where-Used at &J, Trace A =G on how to fill the parameters, Function   => New Pricing)




 


$
  The first method is not to set the pricing condition A  as statistical. Simply remove == and it will work fine if you always use A  as your pricing base inside the pricing procedure. A  will reads both prices based on the price control in the material master. Price control S for standard price. Price control V for moving average price. It is this simple if you do not have any other "Prices" in the price procedure. However, if you are using one pricing procedure where for some items you price using A  and some others using ==, then you should use requirement routines to enable the correct price condition type at the right time. The second method involves more work as you need to write a formula (Ac) to get that information. This is how it goes :1. Set A  to be the first step in the pricing procedure and to be subtotal B (as standard). 2. Set == with alt. calc. type formula, which sets the value of == to be equal to the subtotal B. The routine (created with transaction Ac) is: RV64A901 FORM FRM_KONDI_WERT_600. XKWERT = KOMP-WAVWR. ENDFORM.

The pricing procedure than looks like that: Step 1 A  statistical, subtotal B, reqt 4 Step 2 == Altcty 600

'

 -----Original Message----Subject: Customer discounts on effort only Hi All, We have a requirement of giving a discount to customer based on the total amount invoiced so far (across financial years). Where do we set this up? We have seen so far the discounts are calculated based on the value of the current invoice. The discount should be on a graduated scale basis for example 0 - 100000 No discount 100000 - 200000 5% 200000 - and above 10% This means that discount would only start after the customer's net sale value crosses 100000. For example, if the customer has been billed for 99000 and the current invoice is for 3000, a discount of 5% should be given on 2000 i.e. 100. Another complication is that, the discount is not based on the total amount billed so far, but only on the effort billed and not on reimbursements (like airfares, living expenses, visa charges, beeper charges etc). The discount applies only to the effort and not to the reimbursements. In the above example (invoice of 3000) say the effort billed is only 1500, the rest being reimbursements. The discount is only on the 500. (the rest being taken up by the lower limit for eligibility of 100000) For example the customer might have been billed say 150000 so far but actual effort billed might be only 90000, the rest being reimbursements of actual costs and hence the customer is not eligible for the discount. Kindly help, -----Reply Message----Subject: RE: Customer discounts on effort only

Hi, The solution for this is Using rebate condition types and suitable condition records. Of this to handle your first problem that is the rebate has to be applied only on the "effort" you have to set up a line in the pricing procedure which gives the rebate basis i.e the value to be used for rebate cond types. This I believe solves your problem of rebate only on effort. Your second problem i.e the discount should start getting applied automatically when it reaches the first scale for which the values span few financial years. This I am not really sure whether it can be made possible in the invoice itself. But a work around is not giving the discount directly in the invoice but settling it against the rebate agreements by Credit notes periodically. Hope it helps. Thanks -----Reply Message----Subject: RE: Customer discounts on effort only Hi Arent we looking at rebate agreeement. That appears to be a straightaway solution to your problem. You activate the sales organization and the payer for that Regards -----Reply Message----Subject: RE: Customer discounts on effort only I am in SAP R/3 rel.30F. We have 2 options to meet your requirement. 1. Using scale in condition type ( tcode V/06 ), choose scale basis G.Scale based on a formula ( be: your based amount is invoice ). Define scale formula. You need ABAPER to define it. 2. Using routine in Alt.calc.type ( tcode V/08 , Maintain Pricing Procedure ). Here, you also need ABAPER to create routine.

hope this help -----End of Message-----


$'

' 
 For creating commission agent, you have to follow below steps. 1) Establish Partner Functions for the Commissionee(s) Menu Path: TOOLS ->; BUSINESS ENGINEER ->; CUSTOMIZING ->; SALES AND DISTRIBUTION ->; BASIC FUNCTIONS ->; PARTNER DETERMINATION ->; DEFINE PARTNER FUNCTIONS Transaction Code: VOPA 2) Assign the Partner Functions to Partner Procedures Menu Path: TOOLS ->; BUSINESS ENGINEER ->; CUSTOMIZING ->; SALES AND DISTRIBUTION ->; BASIC FUNCTIONS ->; PARTNER DETERMINATION ->; DEFINE PARTNER FUNCTIONS Transaction Code: VOPA 3) Create a Partner Procedure for the Commissionees Menu Path: TOOLS ->; BUSINESS ENGINEER ->; CUSTOMIZING ->; SALES AND DISTRIBUTION ->; BASIC FUNCTIONS ->; PARTNER DETERMINATION ->; DEFINE PARTNER FUNCTIONS Transaction Code: VOPA 4) Create New Customer Account Group(s) for Commission Agents Menu Path: TOOLS ->; BUSINESS ENGINEER ->; CUSTOMIZING ->; LOGISTICS GENERAL ->; LOGISTICS BASIC DATA: BUSINESS PARTNERS >; CUSTOMERS ->; CONTROL ->; DEFINE ACCOUNT GROUPS AND FIELD SELECTION FOR CUSTOMER Transaction Code: OVT0 5) Assign the Partner Functions to the Customer Account Group(s) Menu Path: TOOLS ->; BUSINESS ENGINEER ->; CUSTOMIZING ->; SALES AND DISTRIBUTION ->; BASIC FUNCTIONS ->; PARTNER DETERMINATION ->; DEFINE PARTNER FUNCTIONS ->; GOTO ->; PARTNER FUNCTIONS ->; ENVIRONMENT ->; ACCOUNT GROUP ASSIGNMENT Transaction Code: VOPA 6) Assign the Partner Functions to the Partner Procedure for the Sales Document Header

Menu Path: Tools ->; Business Engineer ->; Customizing ->; Sales and Distribution >; Basic Functions ->; Partner Determination ->; Define Partner Functions Transaction Code: VOPA 7) Assign the Partner Functions to the Partner Procedure for the Sales Document Item (OPTIONAL) Menu Path: TOOLS ->; BUSINESS ENGINEER ->; CUSTOMIZING ->; SALES AND DISTRIBUTION ->; BASIC FUNCTIONS ->; PARTNER DETERMINATION ->; DEFINE PARTNER FUNCTIONS Transaction Code: VOPA 8) Edit the Pricing Communication Structure (KOMKAZ) to Hold the New Functions (Client Independent) Menu Path: Menu Path: TOOLS ->; ABAP WORKBENCH ->; DEVELOPMENT ->; DICTIONARY Transaction Code: SE11 9) Edit MV45AFZZ ± userexit_pricing_prepare_tkomk (Client Independent) Menu Path: TOOLS ->; ABAP WORKBENCH ->; DEVELOPMENT ->; ABAP EDITOR Transaction Code: SE38 10) Edit RV60AFZZ - userexit_pricing_prepare_tkomk (Client Independent) Menu Path: TOOLS ->; ABAP WORKBENCH ->; DEVELOPMENT ->; ABAP EDITOR Transaction Code: SE38 11) Edit MV45AFZB - userexit_new_pricing_vbkd changing new_pricing (Client Independent) Menu Path: TOOLS ->; ABAP WORKBENCH ->; DEVELOPMENT ->; ABAP EDITOR Transaction Code: SE38 The following code should be inserted into program MV45AFZZ to allow the system to re-execute pricing if the user makes a change to the relevant partner function (alteration, addition, deletion). 13) Add the KOMKAZ Fields to the Pricing Field Catalog (Client Independent) Menu Path: TOOLS ->; BUSINESS ENGINEER ->; CUSTOMIZING ->; SALES AND DISTRIBUTION ->; BASIC FUNCTIONS ->; PRICING ->; PRICING CONTROL ->; DEFINE ACCESS SEQUENCES ->; MAINTAIN ACCESS

SEQUENCES Transaction Code: OV24 14) Create Condition Tables (Client Independent) Menu Path: TOOLS ->; BUSINESS ENGINEER ->; CUSTOMIZING ->; SALES AND DISTRIBUTION ->; BASIC FUNCTIONS ->; PRICING ->; PRICING CONTROL ->; DEFINE ACCESS SEQUENCES ->; MAINTAIN ACCESS SEQUENCES Transaction Code: V/03 15) Create an access sequence containing the new tables (Client Independent) Menu Path: TOOLS ->; BUSINESS ENGINEER ->; CUSTOMIZING ->; SALES AND DISTRIBUTION ->; BASIC FUNCTIONS ->; PRICING ->; PRICING CONTROL ->; DEFINE ACCESS SEQUENCES ->; MAINTAIN ACCESS SEQUENCES Transaction Code: V/07 16) Create a new condition type Menu Path: TOOLS ->; BUSINESS ENGINEER ->; CUSTOMIZING ->; SALES AND DISTRIBUTION ->; BASIC FUNCTIONS ->; PRICING ->; PRICING CONTROL ->; DEFINE CONDITION TYPES ->; MAINTAIN CONDITION TYPES Transaction Code: V/06 17) Add the Condition Type to the Pricing Procedure Menu Path: TOOLS ->; BUSINESS ENGINEER ->; CUSTOMIZING ->; SALES AND DISTRIBUTION ->; BASIC FUNCTIONS ->; PRICING ->; PRICING CONTROL ->; DEFINE AND ASSIGN PRICING PROCEDURES ->; MAINTAIN PRICING PROCEDURES Transaction Code: V/08 11) Create Commsission Report ZZCOMMISSION (Client Independent) Menu Path: TOOLS ->; ABAP WORKBENCH ->; DEVELOPMENT ->; ABAP EDITOR Transaction Code: SE38

/
 ! ' #"
%$#$  /
 
 
000 Whenever we define our pricing procedures, we remain least interested in creating our own Condition Types,Condition

Tables & Access Sequences. What we do is, we just define our own pricing procedures by using the existing condition types (i.e: PR00, K004, K007, KA02, KF00 etc.) & then assign that Pricing Procedure with " Sales Area, Document Pricing Procedure & Customer Pricing Procedure " . After that we put the values against each Condition Types, mentioned in our Pricing Procedure by using the T-Code "VK11". But we also need to know about the Condition Tables, Condition Types & Access Sequence Creation. So for that purpose we have to use the following T-Codes respectively : "V/05", "V/06" & "V/07". Now it will become easy to create the same. Also to inform that, using T-Codes is more smarter than following paths through IMG screen. Utsav Mukherjee - utsavmukherjee143@hotmail. ""



A7@@A7&@,
-4 $
 == 

>

 =*0 "
 
>

!
&=+ !
0."
%

"
 ==A7&@ "
#!
&=+
"
$
 =*0"
% 

"
 ==A7@@
$0 Difference between VK11 and VK31 - if you go through the menu path you will get the vk 31 as condition record from the tamplets whereas vk11 as simple condition record. In VK11 you can store condition record for more than one condition type. This means you can have same condition record for different condition types.This feature is given to enhance the system's performane and not to create the duplcation of the work for each condition type. Again system is not allowing to store the record in the vk31 for the condition type pr00 and access sequence pr02.This is because if you see this ac seq cointains two accessses 20 and 30 having the same table no.But you see there is the difference between the technical view of it for transfering the data from document field and condition field,so you can not maintain the data at VK31. ""



!




%
4%  
$$

"


0

 !
$$



0 Difference between header and item condition - as YOU CORRECTLY SAID HEADER CONDITION IS APPLICABLE FOR THE WHOLE DOCUMENT where

as item is for item.Ex-Say fright is dependent on the total weight of all the items in the documents then header condition adds on weights of all items and calculates the record accordingly. You have two different types of the header conditions. a) In one you can duplicate the same value throughout the document for each item.Say discount 2% at header level which is also applicable to all the items b)Second is the accumulation of the values of all the item at the header level,as earlier explained for the weight/fright. These differenes are controlled through the indicator of group condition in the cond.type configuration. And so obviously header condition can not have the condition record and hence access sequence.  /#$!:A"M

/'#$
(%$""
: 
!
/% cL= '$
!


,% 
 - You can modify condition type from customising; Sales and Distribution->Basic Functions->Pricing->Pricing Control->Define Condition Types->Maintain Condition Types Change condition type ZOBP's plus/minus indicator to "A" which means only positive is allowed. *-- Arvind Rana %$$

"


"
>

2!2 ! 20"
"

"



"

 
""
 $0 1. Requirement: Denoted by nos and maintained in VOFM, this is a condition required for a particular condition type to be executed. Eg. PR00: req 2 ie item relevant for pricing VPRS/EKO1: req 4 ie cost Rebate BAO1 Req 24/Req 25 etc 2. Subtotal: this represents where a which table a value is stored, which can be processed for further calculation.

Eg. for PR00, if this value is to be used for credt check of a customer, we mark the subtotal as A. 3 Alternate Calculation type: this is also denoted by numbers and maintained in VOFM. Eg. Suppose for 45 units , each unit is charged $100 per unit, the order value comes out to be $4500, that is calculation is done as per unit price, if the client wants calculation type to be based on volume or wieght, alternate calculation type can be configured. 4. Alternate base value: Denoted by no. and maintained in VOFM. Eg, if the pricing scale is maintained and pricing for 45 units comes under the scale of $100 per unit., the base value is 45 units, but if the client wants a standard base value in some casesto be assumed inspite of maintaining the scale, an alternate base value is confihured, that is the base value based on which the order value is to be calculated changes. 5. Accruals: Accruals are maintained for rebate agreements, it constitutes the total accumulated value which customer has earned through rebate, one the rebate for certain amount is settled the amount from the accruals get deducted. *-- Nitin


#.
'#!
  

!
 ,'#
">
-:( I will explain you the process with below example...Please follow steps in below sequenceTry 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').



: 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 customerspecific 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. For more information, see Transaction SPRO via the path 'Sales and Distribution -> System Modifications -> Create New Fields (Using Condition Technique) -> New Fields for Pricing' and OSS Note 21040. *-- Manoj Mahajan



' $' "
"

4 Header conditions are those which appear in the header level of any sales order. these conditions are to be entered manually and get distributed automatically and the basis for distribution are taken from the NET VALUE of items mentioned at item level. When we go to the conditions section in a sales order, where the details of pricing is mentioned, here we add these conditions. Whenever any Header Condition is used, it overrides the PR00 condition type. Examples of header condition. - HA00 - % Based Header Condition. - RB00 - Absolute or numeric value which applies to all items. - HB00 - Numeric value or Absolute value.

*-- Vivek Chokshi

""



!


$"

4 Group Condition: You can use this is feature of a condition type to apply price or discount for a material based on common property. Header Condition: This is a manual condition which you apply to header (Condition screen) of a sales document. This amount is applicable to all items. B
"

$$$

: 

"

"

'0%


"
 
c
0"



"$


, 
-0"$$
4 "

4 Header Conditions - Automatic pricing does not take header conditions into account; you can not create condition records for them in the standard system. Header conditions are entered manually in order processing. R/3 includes the following header conditions: - Percent discount (HA00) - Absolute discount (HB00) - Freight (HD00) - Order value (HM00) Header Condition: If this condition is marked as a header condition, it is possible to enter the condition type in the header condition screen. Checks for changing the condition manually are unaffected by this. Group Condition: Group conditions are helpfull incase of discounts. If group condition is selected then the discount percentage or quantity is applicable for the total sum of the quantity in the PO for those materials belonging to the same material group. Suppose if two materials of same matl grp have discounts for 100 qty and above but in PO if the two matls are bieng procured for 50 qty then they cant avail discounts but if group condition is selected then the sum of the quantity of both matl of same matl group is considered (50 + 50) and discount can be availed for 100 qty. Further Group condition: Indicates whether the system calculates the basis for the scale value from more than one item in the document. The nature of header condition is that whatever value you are giving in sale order / billing, line item wise, it will be distributed proportionately.

If you access V/06 and the header condition type, you can see that the condition type - does not have any access sequence - field Group condition is selected Normally Freight Header condition like condition type "HD00" is calculated on the basis of weight. This is a Manual condition and you have to enter it in the header screen. It will be proportionately distributed on each item on the basis of weight. If you will uncheck the group condition field, the same freight amount will be copied to each item, possibly irrespective of different weight which may not be logical. That is the standard behaviour of the header condition type. Based on whether the group condition field is ticked on or off, it will either split the header condition value to the items on pro-rata basis or it will just duplicate the header value to all the items. What you are experiencing with Fixed Amount Header conditions is standard behaviour. Please see below Notes: - 876617 FAQ: Header conditions / Header condition screen - 317112 Behavior of conditions w/ calculation rule B changed - 485740 Conditions with fixed amount in copy activities To achieve what you wish (absolute amount), solution is in the below Notes: - 84605 Transfer absolute amount condition to billing doc. - 25020 Value changes during over/underdelivery - 25144 Freight conditions during milestone billing "
!
3'$

4 '3 The system can exclude conditions so that they are not taken into account during pricing in sales documents. Material 4711 costs 150 USD. Some customers receive a discount of 10 USD per 100 pieces. However, a specific customer can buy the material for 100 USD. Since this is a particularly good price, the customer should not also have a discount of 10 USD per 100 pieces. Therefore, this discount is to be excluded from pricing. To do this, you must follow two steps:

You must set a condition exclusion indicator for the price. You can do this in two ways: If you want to set the condition exclusion indicator a follows then you specify it: - for all condition records of a condition type (e.g. with condition type PR00) when defining a condition type in SD Customizing - for an individual condition record (e.g. only for material 4711) in the detail screen of a condition record (in the Condition exclusion field) You must set a condition for the discount in the pricing procedure in Customizing for sales. If this condition is set, the discount is not valid if the condition exclusion indicator is set. Condition 2 is available in the standard R/3 System. The condition exclusion indicator is not valid for condition supplements. This means that if a condition record contains condition supplements they will be taken into account during pricing. '3 $R In any normal situation there could be more than one condition type in a pricing procedure offering a discount to a customer. Should the discounts be automatically determined, there is the risk that the customer will receive all the relevant discounts and thus purchase the product for a lower price than he should. By using µcondition exclusion groups¶ you can ensure that the customer does not receive all the discounts, but instead only receives the best of the available discount condition types. Menu path ± IMG - Sales & Distribution - Basic functions ± pricing ± condition exclusion ± condition exclusion for groups of conditions (OV31). A condition exclusion group is merely a grouping of condition types that are compared to each other during pricing and result in the exclusion of particular condition types within a group or entire groups. It is important to note that the condition types you want the system to compare must exist in the pricing procedure and must have valid condition records created for them. If for example, a sales order is created using the pricing procedure that the exclusion group is assigned to, you can see that the condition offering the most favorable discount to the customer is represented in the pricing procedure.

For instance, condition type K007 has offered a discount of 10% off the sale price or a real value of $30, while another condition type K005 has offered a real value discount of $10. The system then takes the best discount for the customer between the two, which is K007 and makes the other discount K005 inactive. This can be seen by double clicking on the condition type K005, where you can find a entry saying µInactive A condition exclusion item¶. There are four possible methods of using condition exclusion groups ± A ± best condition between the condition types B ± best condition within the condition types C ± best condition between the two exclusion groups D ± exclusive E ± least favorable within the condition type F ± least favorable within the two exclusion groups 'S'3 $T First step is to define a µcondition exclusion group¶ by using a four character alpha numeric key. Next step is to assign the relevant condition types to the exclusion groups such as discount condition types, freight condition types. After completing the assignment of the condition types to the exclusion group, proceed with assigning the condition exclusion group to the relevant pricing procedure. After selecting the pricing procedure for which you want the condition exclusion to be active, select the folder µExclusion¶ where you can assign the relevant condition exclusion procedure to the relevant condition exclusion group. When using the condition exclusion group to find the best condition record in a condition type ± only use one condition type per exclusion group. The most important thing to remember here is to ³deactivate´ the Exclusive Indicator on the access sequence assigned to that condition type. Otherwise, the system will merely find the first condition record and stop searching for other records.

"


!


$
$?
34


$: A Pricing report basically helps to get the list of all the pricing details which we have maintained in the system. We can get details of all the condition types including the scales. We can get the details as per our requirement i.e., Sales org/Dc/Division/Plant /material etc wise. The selection criteria would be as per the Key combination which you select in the IMG screen You get following information from pricing report. 1. It informs you about the customer specific price agreements that were made within a certain period 2. From pricing report you can know which condition records exist for freight charges 3. Which condition records exist for customers in a particular region or country You can create your own pricing reports with V/LA. Also V/LD is very useful. This can be customized. The sales personnel use it to 1. get information for price (discounts) that existed at previous period (Say June 200X) 2. Inform potential buyer about the current price (and discounts) 3. Review price and discounts. Though all the above T Codes and there are many More standard SAP Reports have very high utility, it is not widely used. Clients prefer customized reports when it comes to pricing reports - all Z programs and Transactions. These kind of reports are generally required by the Top Management for periodical review // Finance team for price control // Master data team for record purposes // Process audits by Internal/external agency // Of late, for every SOX audit done in the company...especially the change records for prices. '%
3

Condition index is very useful for searching the condition record for a customer. It becomes easier and faster to search for condition records for a customer or material just like it become easier to search a topics in the book with help of index. You have to mark the "condition index" check box in the condition type and you have to activate the index in customization. You can set the discount for fast ten orders through "condition update". First, in your discount condition type(V/06) activate the "condition update" check box. Second, in the condition record, in additional data put "maximum number of orders" as 10. You may also create the condition record for discount through VK31. Now go to change(VK32), scroll to the right, you will find a column "N". This is maximum number of order field. Here you can put value 10 and save it. Now, system will give the discount to the first 10 orders. "


"
!
 
,/

-


 '$
4 First check the Material Master UOM Conversion - Additional Data - Units of Measure. Condition base value is a concept used in pricing procedure and actual term used is alternate condition base value. This is a formula assigned to a condition type in order to promote an alternate base value for the calculation of the value. If you have to calculate price of a material then you have to have a base value for it. For e.g. if you want to calculate the discount of 10 % for a material then you have to have a base value on which this 10% is calculated. Normally you take the condition value of the base price of the material to calculate the value. Now, you don't want to take the base value and take other value as base value which are derived on some formula. So you create a routine which will do the mathematical operations in the routine and derive you a value which is now used as the base value for calculating the condition value for a particular condition type.

As per my understanding there is Alternative Condition Base Value, It is a routine which is assigned to the condition type in the pricing procedure. Go to transaction V/08 here you select pricing procedure then go in to the control data of the pricing procedure here you can find Alter native Condition Base Value in the 14th column of the pricing procedure control data. ""



!


: @0'!
 
 *0' 
0 &0' 1. Conditional base value When a value is derived for a condition type, based on certain calculation this value is taken as base. 2. Conditional value. For the number of units ordered depending on the condition amount mentioned this value is derived. 3. Conditional amount This is nothing but the unit list price what you are mentioning for the line item. @-""



$
2!
 
2 
>

$$

4 *-"




 


!
 


 $
"
$ $

 
2"
"
 
 

!
 


$

 $$

4 **Alternative Calculation Type:** This function allows you use a formula as an alternative in finding the value of the condition type, instead of standard condition technique. this can be used to calculate complex tax structures.

Alternative condition base value The alternative condition base value is a formula assigned to a condition type in order to promote an alternative base value for the calculation of a value. Example An absolute header discount is, for example, distributed in the standard system according to the cumulative value of the items. If the system distributes the absolute header discount according to volume based on the Alternative formula for condition base value , a header discount of $30 results in the following discounts: Item Value Volume . 1 $1000 2 cbm 2 $500 4 cbm Stand. disc. Volume disc.(With Formula) $20 $10 $10 $20 Condition formula for alternative calculation type Alternative formula to the formula in the standard system that determines a condition. Requirement This function is used to assign a requirement to the condition type. This requirement can be used to exclude the system from accessing the condition type and trying to determine the value. This can be used to specify that the condition type should only be accessed if the customer has a low risk credit.

m
    

 %

/$
2"
"

 
>

=@&
2!$$

%P

"
 
>

=@&20$
(@D2'A(+0

Please refer to the following documentation for requirement 013: RE LV61A013 Title Rounding as per Table T001R Purpose This is an example of a pricing requirement. This requirement is met if an entry has been made in the 'Unit to be rounded up to' field in Table T001R. Table T001R stores the rounding rules for company code and currency combinations. This requirement can be assigned to the condition type in the pricing procedure that is used to calculate the difference when rounding. Using this requirement, the difference is only calculated when necessary. Example A company has the requirement to carry out rounding for certain company code and currency combinations. This information is stored in Table T001R. In the document pricing procedure, the user has configured the SAP delivered condition type DIFF to calculate the difference when rounding occurs. The user also assigns pricing requirement '13' to the condition type DIFF in the pricing procedure so that the condition is only calculated when a corresponding entry has been maintained in the table T001R. Please check the customizing table T001R. or try this go to IMG path --> SAP Netweaver --> General Settings --> Currencies --> Define rounding rules for currencies. Here maintain the rounding unit which will be stored in Table T001R. then in the t-code ob90 you can maintain that. Go to v/08 maintain in condition base value 16 routine. Purpose This is an example of a condition value formula. This type of formula can be used to influence the value shown for the condition in pricing. A condition value formula is assigned to a condition type or value line in the pricing procedure.

Formula '16' was delivered along with condition type DIFF to support the rounding unit rules that can be defined in T001R for company code / currency combinations. Condition type DIFF was delivered to perform the rounding at the end of the pricing procedure with the total value. Using formula '16', the system computes the rounded value and assigns the difference to the condition type DIFF. In-17 c.base value Round according to T001R Purpose This is an example of a condition value formula. This type of formula can be used to influence the value shown for the condition in pricing. A condition value formula is assigned to a condition type or value line in the pricing procedure. Formula '17' was delivered so that a condition value could be rounded off according to the rounding unit rules (e.g. plus 5 or 10 or 100 units) that can be defined in T001R for company code / currency combinations. When formula '17' is assigned to a condition type, the condition value will always be rounded using T001R.

"

%
$



$
4 1) Create Rounding rule ( Unit of measure rounding rules ) Path : Materials --> SPRO Quantity Optimizing and Allowed --> Order Optimizing --> Purchasing --> Management Unit of Measure Rounding Rules --> Logistics Units of Measure Here give new rounding rule and % rounding up and down values 2) Create Unit of measure groups Path : Order Optimizing --> Purchasing --> Materials Management --> SPRO Unit of Measure --> Quantity Optimizing and Allowed Logistics Units of Measure Groups Create new group for YD and ROL 3) Dynamic rounding profile

Path : Order Optimizing --> Purchasing --> Materials Management --> SPRO Maintain Rounding --> Quantity Optimizing and Allowed Logistics Units of Measure Profile Here give Rounding profile name and plant and click on Dynamic to create new profile In next screen give desc. For rounding profile, rounding off method as 2, and rounding rule which you have created. Assign created Rounding profile in info record also UOM group Maintain minimum order qty as 1 Rol and Order unit as ROL in Info record In material master maintain conversion as 1 Rol = 3500 yards

#'


7c 27c .

  To use a field in pricing, one creates a condition table. This condition table is created using the allowed fields from the field catalog. Should the fields one requires not be included in the list of allowed fields, one can add the fields from the list of available fields. However, one may find that a new field may not be in the list of available fields. For this reason, one must create new fields for pricing. The document and item data in SD is stored in data tables, such as VBAK and VBAP (for the order transaction). Many of the fields from these tables are available in the field catalog. The field catalog is a structure (KOMG) that consists of two tables (KOMK and KOMP). These tables contain the header and item data for pricing respectively. They are called KOM ³x´ because they are communications structures used to communicate the transaction data with the pricing procedure. Table KOMG contains the fields of tables KOMK and KOMP. If you require a field that is not in KOMG, it means that it is not in KOMK or KOMP. This means that the field you require cannot be used in pricing because there is no communication of this field from the transaction to the pricing procedure via the communication structures. To use a field not defined in the field catalog, you need to add this field to the KOMK or KOMP structures, and then write the ABAP code to transfer the data in the field from the transaction tables to the communication structure. Follow these steps:

1. Create the field in the KOMK (header data) and KOMP (item data) tables using the standard includes provided for this requirement. 2. Write the code in the user exit to read the transaction data and transfer it to the KOM ³x´ structures. Menu Path The menu path here is IMG, Sales and distribution, System modification, Create new fields (using the condition technique), New fields for pricing. "

7c77c

This process requires some knowledge of the ABAP dictionary and how to use the ABAP dictionary to create and change fields and tables. You may have to use an ABAP skill to assist you. If the field is from the header table (for example, the order table VBAK), you¶ll need to add it to the include table KOMKAZ in table KOMK. If the field is from the item table (for example, the order item table VBAP), you¶ll need to add it to the include table KOMPAZ in table KOMP. Let¶s say you need to use the ³base material´ to define a price and the base material is not in the pricing field catalog. The base material is a field on the material master basic data screen and is defined as MARA-WRKST. Since this relates to the material, it is at the item level, so you would add the field to the KOMPAZ include table. Note When you add a field to these tables, it must start with ³ZZ.´ Therefore, the field you add would be ZZWRKST. In ABAP, when you add the field, use the same domain as in the field in the original table MARAWRKST. After adding the field, generate the structure KOMP. This field is not available in the field catalog and can be used in condition tables. "
  '
The field in the communications structure will be blank unless the ABAP code transfers the data from the material master to the field KOMPZZWRKST. Pricing occurs in the order and in the invoice, so you need to put this code in both places. For the order transaction, write the ABAP code in user exit USEREXIT_PRICING_PREPARE_TKOMP in include program MV45AFZZ. For the billing transaction, write the ABAP code in user exit USEREXIT_PRICING_PREPARE_TKOMP in RV60AFZZ.

Note : The TKOMP is for the item level. If you are writing the code for a field at the header level, you would use the user exits that end with TKOMK. The ABAP code would select the Base material field from the material master table using the material from table VBAP/VBRP. It would then transfer this field to the structure TKOMP from MOVE MARAWRKST to TKOMP-ZZWRKST.

!



  This SAP message will appear if the system is unable to find the G/L codes match from the configuration in transaction VKOA No account is specified in item 0000001001 Message no. F5 670 Diagnosis No account was specified for account type "S" in item "0000001001" of the FI/CO document. System Response The Financial Accounting program cannot process the document. Procedure A system error has probably occurred in the application you called up. Check the data transferred to item "0000001001" of the FI/CO document. Assuming that one of the key combination is Account Assignment Group, you will have to check whether have the Account Assignment Group been input in the Customer Master (Billing tabstrips - Accounting sections - Field name: Acct assgmt group). The Account Assignment Group will be copied automatically into the sales order. Check whether the configuration in transaction VKOA have been done correctly. Check whether the sales order (VA03 - Goto - Header - Financial Accounting - Field name: AcctAssgGr) have been filled in automatically. Check whether the billing document (VF03 - Goto - Header - Header - Field name: AcctAssgGr) have been filled in automatically.

If the customer master have not been maintained and the user have already input the sales order, then the user will have to maintained the Account Assignment Group manually either in the sales order or the billing documents. Take note for One Time Customer, the user have to input the Account Assignment Group manually into the sales order. One Time Customer can be used by many customer, therefore, the system will not be able to determine the Account Assignment Group manually.

/
AA=+ There are two types of variant in A=+. One is the selection variant before clicking the /$ Button. You can set the start variant via C& using the '"
mode. The second variant is the  display variant. This is after clicking the Display Billing List Button. After creating your layout display variant, you can set it by clicking :
 -> /$A ->  Select the layout display variant you want and click : -> /





'3""!



"
! 
 #"


3
""


 $0


3$
: 
+J@@@G=B/0




@=B/$
 @==$

0 

2$

!"

@==B/0
" $$
2"

""
@=B/ $
@==$

0#"


2"!

3
$0 To create a condition exclusion procedure which will be determined in the billing document. Assign the procedure to the pricing schema, and maintain copy control so that pricing is not copied from Sales Order. To achieve this, copy the standard pricing to a ZXXXX Pricing. Define new document pricing procedure in &=(A8#A7A for billing. Assign new document pricing procedures to billing types in &=(A8#A78 Define the Condition Exclusion Groups in cA&@. Assign the Condition type for the Condition Exclusion Groups in cA&*. Assign the Billing Pricing Procedure in Ac7I for the Condition Exclusion Groups. When billing document is being created just enter manually your new price and the pricing program logic will include only the higher price one, excluding the rest that are lower price.

#$: '

>>IMG>>>Sales & Distribution>>>Billing>>>Billing Documents>>>Country-specific features>>>Maintain Maximum No. Of Billing Items. This is where you can define a maximum number of items allowed for all billing documents within a given sales organization. However, maintaining data here is not enough alone to bring about a billing split by number of billing items. You must also go to copying control for order/delivery to billing document at item level under "Data VBRK/VBRP" and maintain routine 006 "individual invoice limited" or a similar routine that accesses the data maintained here.  /#$!: 

/
.

 

;/


!;


4 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. 


"

!

"
" !




&CG0"%
"
0 Check if Item Category is checked for Billing or not. .
c
'
:( 
$@:
/
#$
IMG > Sales and Distribution > Sales > Sales Documents > Sales Document Header: 1. Sales Document Type:The sales document types represent the different business transactions, such as Inquiry, Quotation, Sales Order, etc. To create new sales order type, always copy as with reference to similar sales order. If possible use standard sales order. 2. Define Number Ranges For Sales Documents: Maintain number range with discussion with core team. 3. Assign Sales Area To Sales Document Types: A. Combine sales organizations / Combine distribution channels / Combine divisions: Ensure to maintain these, else Sales Order creation will give error. B. Assign sales order types permitted for sales areas: Assign only required Sales Order Types to required Sales Area. This will minimize selection of Sales Order Type as per sales area. 
/
%
: *1. Define Item Categories: If possible use Standard Item Category. Incase if required to create new, copy as from standard & maintain New. *2. Assign Item Categories: If possible, use standard. Formula for deriving item category: Sales Document Type + Item Category Group + Usage + Higher Level Item Category = Item Category "


: 1. Define Schedule Line Categories: If possible use Standard Schedule Lines. Incase if required to create new, copy as from standard & maintain New.

2. Assign Schedule Line Categories: If possible, use standard. Formula for deriving Schedule Line: Item Category + MRP Type / No MRP Type. 
$*: IMG > Logistic Execution > Shipping > Deliveries > *1. Define Delivery Types: If possible use Standard Delivery Type. Incase if required to create new, copy as from standard & maintain New. *2. Define Item Categories for Deliveries: If possible use Standard Item Categories for Delivery Type. Incase if required to create new, copy as from standard & maintain New. *3. Define Number Ranges for Deliveries: Ensure to maintain number range. 
$&: IMG > Sales and Distribution > Billing > 1. Define Billing Types: If possible use Standard Billing Type. Incase if required to create new, copy as from standard & maintain New. 2. Define Number Range For Billing Documents: Ensure to maintain number range. 3. Maintain Copying Control For Billing Documents: Maintain relevant copy controls such as Sales Order to Billing, Deliver to Billing, etc. Note: Ensure that Copy Control settings are done Sales Order to Sales Order (QT --> OR): VTAA Sales Order to Delivery (OR --> LF): VTLA Sales Order to Billing (OR --> F1): VTFA Delivery to Billing(LF --> F2): VTFL Billing to Sales Order (F2 --> RE): VTAF The configuration differs from scenario to scenario & requirement of the client.



#'
/
   OOH/

#

: 
"
$
:
c
((Hc!/

, 
-((H 2""$$
"


4 $

"$
:((H 

$((H
 c
4,%""



$


4After performing the process Sales Order --> Outbound Delivery (Goods issue) --> Billing, the billing document will be passed on to the FI consultants. But if there is a

cancellation then, this billing doc. which will have a accounting document also that will also get cancelled. In the FI customer open line items. Cancellation of billing - VF11 Cancellation of delivery - VL09 Then go to VL02N and remove the picking qty and make it blank then Goto VA02 and cancel the order. You can delete the Sales Order if transaction have been done: In VA02 , just enter into the sales order goto menu path -> Files-> Cancel or delete option will be there will be there. After deletion / cancellation of that sales order that order doesn't exist in the database. For example , if your sales order number is 1055 and you have deleted or cancelled that sales order, then that sales order number doesn't exist in the database and you cant create another sales order with the same order number 1055. When you create another sales order the number will skip to the next one i.e, 1056. You can only reject the Sales order if there are existing transations: 1. First you need to cancel the billing document using T-code VF11, so it will reverse all the updated accounting entries. 2. Now you need to cancel the Post goods Issue using VL09, once it is reversed, the delete the delivery using VL02N. 3. Once the delivery is deleted, the sales order will be open. Now put a reason for rejection in the line item/s, and reject the order, the order will get closed. It is not advicable delete a sales order. "'
/
 "
 !


"


!
4 Goto to tcode SE16 Table: VBRK

Field: VBRK-ZUONR - Assignment (this field link the original and cancelled billing documents) Cancel billing documents must be successfuly released to accounting. Usually it failed when user tried to cancelled current period with previous date.

"

A=+%    OOH/%

"

!!
4 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. 5. Continue further to complete the task, now you batch job will run at a specified time which you mentioned, if you mentioned as immediately, then once you comple this process, your vairant will run, and billing documents will be created.

6. Plese ensure that all the deliveries are perfect, meaning there is no billing block or any thing. You can check the status of your batch job using t. code SM37. /


!


"
 . #==/%/$0 RSNAST00 is a program which is related to output related activities. Using this program, we can schedule the creation of outputs (PDFs, email etc) in total for any document created in any of the applications. The details are read and stored in the database table NAST. The same program is customised for each applications using programs like SD70AV1A which are also used for the same purpose but only for sales orders. SDBILLDL is the program for Billing due list. This program finds out all the orders or deliveries or both which are due for billing and it will trigger the billing creation. It reads tables like VBAK, VBAP, VBUK, VBUP, LIKP, LIPS etc and the created billing documents are stored in tables VBRK, VBRP.

3$#"
'
$








3$
"

$



!

!


 $


0%" !



4"
"
 

>

4 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

': /=@(@GG:





0
c 
"

"
'!"


0 %K(=GJ:.

$ 


,-
0#" !

"


>

$

"

,

$

!-0 .
$$
/ 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


 
( 

  
& 

   

 
' 
:

Retro billing and Self-billing are entirely different processes and can be executed independently. Let me explain using a very simple example: You sell 10 units of a material A for $100 per unit - Amount $1000 Invoice is sent to customer for $1000 on say Sep 20, 2099 # c(%%. Now due to price negotiations price may change to $90 w.e.f Sep 01, 2099. Thus you will update your price conditions in VK12 for this material/customer to $90 with validity from Sep 01, 2099. But as you have already invoiced the customer in past so to take care of the extra billing . You will execute retro-billing process. You will go to VFRB and enter the selection criteria for the material and suitable dates, system will provide you the list of candidate invoices to which this price reduction is applicable and hence you can simulate or even execute retro-billing after providing Cr/Dr memo type and order reason. These documents will get attached to the original invoice Important to Note - you must maintain the 'use of order reason for retro-billing' in Order reasons configuration for this to work properly. (%%. Here customer raises invoices for itself. Supplier does not send the invoice to customer. Customer may send a self-bill for the above case like $80 a piece. This will hit the supplier system in form of EDI/Fax/Paper etc and on verification in system will show in Self-bill Monitor VSB1n. On processing, system will generate a credit memo of $200 for the customer and a debit memo for same amount with reference ?_?_?. Now the customer while paying will pay $800 as per its self-bill and the same would be settled against original invoice of $1000 and SB credit Memo of $200. Other debit memo of $200 (with ?_?_? reference) will remain open in system which may be

cleared off by a retro billing run where supplier may reduce the price by $20 or take further action as needed.

3"
 
/
 a„  
(a  
 
  



 

  
  

 

 


   
  
)(  

 
 *=     

     

   



  
) 
    
  + & 
(





 
 
 

(a, 
      
   =
  
  
 
  
  



 
 
)  
  
 



 
 
 
 

    
   ( 
 
 


        
a 

 )     )
   a
 



  
  
     



a   

 
     a   
 
 
    

 
    
  -     : )"
"


3"

,c=I-

!
! 
: 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. %"
!
"


&
3"

2$



: VBRP-KURSK Exchange Rate for the conversion Loc.currency Doc.currency. for Price Determination The determination of this exchange rate depends on the setting of TVCPFLP-PFKUR in customizing copy-control VBRK-KURRF Exchange Rate for the conversion Loc.currency Doc.currency. For FI postings If there is a manual entry in the sales order field VBKD-KURRF (Goto -> Header ->

Accounting), then it is copied into VBRK-KURRF. Otherwise VBRK-KURRF is determined during invoice creation. It is supposed that manual entry has higher priority. See the OSS note 36070. KOMV-KKURS Exchange Rate for the conversion Cond.currency Loc.currency At price condition level. It is always determined according to the Pricing date. See the OSS notes 92613, 97487. During VF01 the system determines the Exchange rate for FI posting VBRK-KURRF from the currency tables according(OB08) to the billing date only if the field Exchange rate for FI posting is empty in the source sales document (VBKDKURRF). If the sales document has this field filled, manually or copied from a reference invoice (by copy control routine), then it is copied in the subsequent billing document. This is the standard working of the system. #"

3"

"!
!
$,A#  A#-"




0#"
"
"

: Pricing Exchange Rate Type (V_TVCPFLP-PFKUR) A Copy from sales order B Price exchange rate = Accounting rate C Exchange rate determination according to billing date D Exchange rate determination according to pricing date E Exchange rate determination according to current date F Exch.rate determination accord.to date of services rendered

#/''


 Credit and risk management takes place in the credit control area. According to your corporate requirements, you can implement credit management that is centralized, decentralized, or somewhere in between. An organizational unit that represents the area where customer credit is awarded and monitored. This organizational unit can either be a single or several company codes, if credit control is performed across several company codes. One credit control area contains credit control information for each customer.

For example, if your credit management is centralized, you can define one credit control area for all of your company codes. If, on the other hand, your credit policy requires decentralized credit management, you can define credit control areas for each company code or each group of company codes. Credit limits and credit exposure are managed at both credit control area and customer level. You set up credit control areas and other data related to credit management in Customizing for Financial Accounting. The implementation guide is under Enterprise Structure -> Definition or Assignment -> Financial Accounting and then Maintain credit control area. You assign customers to specific credit control areas and specify the appropriate credit limits in the customer master record. #$!:7$ Settings for determining the credit control area of a document. The settings of items 1 - 4 are taken into account according to their priority. The credit control area found is stored in field VBAK-KKBER. 1. Transaction c&I Check which credit control area is assigned to the company code. Company code: Credit control area: 2. Transaction cA Check which credit control area is assigned to the sales area. Sales area: Credit control area: 3. Transaction K/=* or A/=* Check which credit control area is assigned to the payer. Payer: Credit control area: 4. Transaction &J Is user exit EXIT_SAPV45K_001 being used? 5. Transaction cL7 For the settings under items 2 - 4, field "All company codes" must be marked in Transaction c+G, or the credit control area must be entered under the relevant company code in

table T001CM of the credit control areas allowed. Company code: Credit control areas allowed: 6. Settings for the credit checks 7. Transaction cA 7 Which settings do exist for the sales document type used? Sales document: Check credit: Credit group: 8. Transaction cA / Which settings do exist for the delivery type used? Delivery type: Credit group for delivery: Credit group for goods issue: 9. Transaction c=@ Credit management/Change risk category Definition of the risk category for each credit control area. This risk category can be assigned to a credit account by using Transaction /&*. 10. Transaction cA I Here, the individual credit checks for key fields o credit control area o risk category o credit group are set. Take these key fields from the above settings and go to the detail screen. In particular, check whether fields "Reaction" and "Status/block" are set correctly. To carry out follow-up actions in case of a credit block, the credit check status must be set (field "Status/block"). 11. Transaction /&* Credit master data for the payer of the relevant document. Credit account: Credit limit: Risk category: Currency:

12. Settings for updating the credit values Update of the credit values is required for the limit check (static or dynamic credit limit check). 13. Transaction cA J Update of the credit value is active for the corresponding item type if the check box is marked. This field corresponds to field "Active receivable" in Transaction AcAJ. Item type: Active receivable: 14. Transaction A credit management.

-----End of Reply Message-----


 


$


"
 ! -----Original Message----Subject: Sales value field in not getting updated after creating the billing we are on 4.6b. we are going for credit management but facing one problem. in fd32customer credit management change - the sales value feild in not getting updated after creating the billing. eg. when i create the order - the order value get updated in the sales value in fd32. after creating the delivery - that value remains same in the feild of sales value. but when i am going for billing (delivery related), the bill value is appearing in 'receivables' but the amount in 'sales value' is not getting reduced. because of this the credit exposure is increasing continuously. update group for corrosponding credit ctrl area is 12. also the item is mark for credit update. can anyone tell the missing link? thanking in advance -----Reply Message----Subject: RE: Sales value field in not getting updated after creating the billing Hi, You need to check couple of settings like: 1. Your customer should be assigned the credit control area. 2. In your Item Category Credit should be active. Regards, -----Reply Message----Subject: RE: Sales value field in not getting updated after creating the billing

customer is assign to concorn CCA and item category is mark for credit active -----Reply Message----Subject: RE: Sales value field in not getting updated after creating the billing Hi, Check the credit update group in the transaction OB45. The credit update group controls when the values of open sales orders, deliveries and billing documents are updated. It should be '000012'. Further also refer to the OSS note 18613. Have fun -----End of Message-----

/





$
 '
'"
  #$
 3$



!


$

"
 $
0% "
 2


!


"
 0 % ' /%#''7: Tr.Code - FD32 It Considers the Doc.Value + Open Items. Doc.Value : Sales Order Has been saved but not delivered Open Item : Sales Order has been saved , Delivered, Billed & Transfered to FI, but not received the payment from the customer. Eg: Customer Credit Limit is Rs.1,00,000/Suppose Doc.Value + Open Item Value is Rs.1,10,000/Here credit limit exceeds then system reacts. Options : A) Warning Message B) Error Message (Sales Order won't be saved) C) Error Message with Delivery Block

B#c #%'' /%#''7: Give extra credit facilities to the particular customer. STATIC CREDIT LIMIT DETERMINATION :Checking Group + Risk Catageory + Credit Control Area. A) Credit Checking Groups : Types of Checking Groups. 01) Sales 02) Deliveries 03) Goods Issue At all the above 3 levels orders can be blocked. B) Risk Catageory : Based on the risk catageories company decide how much credit has to give to the customer. HIGH RISK (0001) : LOW CREDIT LOW RISK (0002) : MORE CREDIT MEDIUM RISK(0003) : Average Credit Static Credit Check it checks all these doc value & check with the credit limit 1) Open Doc.Value / Sales Order Value : Which is save but not delievered 2) Open Delivery Doc.Value : Which is delivered but not billed 3) Open Billing Doc.Value : Which is billed but not posted to FI 4) Open Item : Which is transfered to FI but not received from the customer. DYNAMIC CREDIT CHECK : 1) Open Doc 2) Open Delivery 3) Open Billing 4) Open Items 5) Horizon Period = Eg.3Months Here the System will not consider the above 1,2,3& 4 values for the lost 3 months Then assign the Sales Doc & Del Documents. Sales Doc.Type(OR) + credit Check(0) + Credit Group (01)

Credit Limit Check for Delivery Type : Del.Type (LF) + Del Credit Group (02) + Goods Issue Credit Group (03)


B$'
' 
 
 Given below is the set up for credit card payment processing: Set Up Credit Control Areas: Define Credit Control Area Transaction: OB45 Tables: T014 Action: Define a credit control area and its associated currency. The Update Group should be µ00012¶. This entry is required so the sales order will calculate the value to authorize Assign Company Code to Credit Control Area Transaction: OB38 Tables: T001 Action: Assign a default credit control area for each company code Define Permitted Credit Control Area for a Company Code Transaction: Tables: T001CM Action: For each company code enter every credit control area that can be used Identify Credit Price Transaction: V/08 Tables: T683S Action: Towards the end of the pricing procedure, after all pricing and tax determination, create a subtotal line to store the value of the price plus any sales tax. Make the following entries: Sub to: ³A´ Reqt: ³2´ AltCTy: ³4´ Automatic Credit Checking Transaction: OVA8 Tables: T691F Action: Select each combination of credit control areas, risk categories and document

types for which credit checking should be bypassed. You need to mark the field ³no Credit Check´ with the valid number for sales documents. Set Up Payment Guarantees Define Forms of Payment Guarantee Transaction: OVFD Tables: T691K Action: R/3 is delivered with form ³02´ defined for payment cards. Other than the descriptor, the only other entry should be ³3´ in the column labeled ³PymtGuaCat´ Define Payment Guarantee Procedure Transaction: Tables: T691M/T691O Action: Define a procedure and a description. Forms of Payment Guarantee and make the following entries Sequential Number ³1´ Payment Guarantee Form ³02´ Routine Number ³0´ Routine Number can be used to validate payment card presence. Define Customer Payment Guarantee Flag Transaction: Tables: T691P Action: Define a flag to be stored in table. Create Customer Payment Guarantee = ³Payment Card Payment Cards (All Customers can use Payment Cards)´. Define Sales Document Payment Guarantee Flag Transaction: Tables: T691R Action: Define the flag that will be associated with sales document types that are relevant for payment cards Assign Sales Document Payment Guarantee Flag Transaction: Tables: TVAK Action: Assign the document flag type the sales documents types that are relevant for payment cards. Determine Payment Guarantee Procedure Transaction: OVFJ

Tables: T691U Action: Combine the Customer flag and the sales document flag to derive the payment guarantee procedure Payment Card Configuration Define Card Types Transaction: Tables: TVCIN Action: Create the different card types plus the routine that validates the card for length and prefix (etc«) Visa , Mastercard, American Express, and Discover Create the following entries for each payment card AMEX American Express ZCCARD_CHECK_AMEX Month DC Discover Card ZCCARD_CHECK_DC Month***** MC Mastercard ZCCARD_CHECK_MC Month VISA Visa ZCCARD_CHECK_VISA Month The Routines can be created based on the original routines delivered by SAP. *****SAP does not deliver a card check for Discover Card. We created our own routine. Define Card Categories Transaction: Tables: TVCTY Action: Define the card category to determine if a payment card is a credit card or a procurement card. Create the following two entries Cat Description One Card Additional Data CC Credit Cards No-check No-check PC Procurement Cards No-check Check Determine Card Categories Transaction: Tables: TVCTD Action: For each card category map the account number range to a card category. Multiple ranges are possible for each card category or a masking technique can be used. Get the card number ranges from user community. Below is just a sample of what I am aware are the different types of cards.

Visa Credit Expires in 7 days. 400000 405500 405505 405549 405555 415927 415929 424603 424606 427532 427534 428799 428900 471699 471700 499999 Visa Procurement Expires in 7 days. 405501 405504 405550 405554 415928 415928 424604 424605 427533 427533 428800 428899 Mastercard Credit Expires in 30 days 500000 540499 540600 554999 557000 599999 Mastercard Procurement Expires in 30 days 540500 540599 555000 556999 American Express Credit Expires in 30 days 340000 349999 370000 379999 Discover Card Credit Expires in 30 days 601100 601199 Set Sales Documents to accept Payment Card Information Transaction: Tables: TVAK Action: Review the listing of Sales Document types and enter ³03´ in the column labeled ³PT´ for each type which can accept a payment card Configuration for Authorization Request Maintain Authorization Requirements Transaction: OV9A Tables: TFRM Action: Define and activate the abap requirement that determines when an

authorization is sent. Note that the following tables are available to be used in the abap requirement (VBAK, VBAP, VBKD, VBUK, and VBUP). Define Checking Group Transaction: Tables: CCPGA Action: Define a checking group and enter the description. Then follow the below guidelines for the remaining fields to be filled. AuthReq Routine 901 is set here. PreAu If checked R/3 will request an authorization for a .01 and the authorization will be flagged as such. (Insight does not use pre-authorization check). A horizon This is the days in the future SAP will use to determine the value to authorize (Insight does not use auth horizon period). Valid You will get warning message if the payment card is expiring within 30 days of order entry date. Assign Checking Group to Sales Document Transaction: Tables: TVAK Action: Assign the checking group to the sales order types relevant for payment cards Define Authorization Validity Periods Transaction: Tables: TVCIN Action: For each card type enter the authorization validity period in days. AMEX American Express 30 DC Discover card 30 MC Master card 30 VISA Visa 7 Configuration for clearing houses Create new General Ledger Accounts Transaction: FS01 Tables: Action: Two General Ledger accounts need to be created for each payment card type. One for A/R reconciliation purposes and one for credit card clearing. Maintain Condition Types Transaction: OV85

Tables: T685 Action: Define a condition type for account determination and assign it to access sequence ³A001´ Define account determination procedure Transaction: OV86 Tables: T683 / T683S Action: Define procedure name and select the procedure for control. Enter the condition type defined in the previous step. Assign account determination procedure Transaction: Tables: Action: Determine which billing type we are using for payment card process. Authorization and Settlement Control Transaction: Tables: TCCAA Action: Define the general ledger accounts for reconciliation and clearing and assign the function modules for authorization and settlement along with the proper RFC destinations for each. Enter Merchant ID¶s Transaction: Tables: TCCM Action: Create the merchant id¶s that the company uses to process payment cards Assign merchant id¶s Transaction: Tables: TCCAA Action: Enter the merchant id¶s with each clearinghouse account  /#$!: " " 

/ 
%'


 3$!$



4 Let me explain in simple terms:

1) You have a Customer which you had felt, he is doing good business and supplied material on Credit of 45 days. 2) Since this customer is good as you felt, you have not managed Credit Checks as well. So, he had comfortably reached to the fullest credit (or even more) which you can afford for any customer. 3) One fine day you got realised that, there is very bad debt with this customer and need to recover from him and till then, there will be no further supply to the customer. 4) Your company's legal department has laid a policy that, inorder to recover any bad debts, like: a) We will send a normal payment reminder. b) In case customer doesnt respond, we will send at least further reminder (dunning notice) may be 9 times (9 reminders) (Dunning level) and what intervels of time (dunning frequency) c) Still if the customer doesnt resopond for the reminders, you will file a law suit against the customer for recovering the Payments. d) Finally, after getting veridict, you may proceed for auction of his property or as per the order for Law. Now in SAP, the definition of Dunning procedure is a pre-defined procedure specifying how customers or vendors are dunned. For each procedure, the user defines - Number of dunning levels - Dunning frequency - Amount limits - Texts for the dunning notices In SAP, you will maintain the Dunning Procedure at customer master. Referring to this your SD Team / FI Team (user team) will effect Dunning PS: You might remembered the dunning procedure laid by Relaince Mobile, sometime back, sending street rowdies for recovering the bad debts from users. That is dunning. Remember Reliance, you will not forget dunning forever. #$!:7 "
!

3$
4

They are the transactions with a customer that are relevant for credit limits on a specified date. The credit exposure is updated based on the update algorithm assigned to the credit control area. 000012 - updated at Sales Order 000015 - updated at Delivery 000018 - updated at Billing To look at only Receivables for a customer look in FD32. If you have bad data run the reorganization program through SE38. Check Note 425523 - Collection of consulting notes: Credit update and related. Surely you must run report RVKRED77 (Note 400311 - RVKRED77: Reorganization credit data, new documentation and related will help you). @0

3$

,

/&*-4 It¶s simple summation of Receivables + Special liabilities (like down payments, advance) + Sales value *0%B$
O====@*'' "


c
2"

3$
 

!c 
0 $
O====@G2"


c
2"

3$


 !c 
0 %"
4 I think in case of 000015 Open sales order values should not be considered. &0"

3$
$"



$
0%

"
 
""
 


3$
"
"
3





4 Credit exposure is in fact the main player. In credit management if the customer¶s credit limit is 10000 and credit exposure is 9900 then customer can only be able to buy now worth of 100 only. It¶s the credit exposure which should not crossed over the credit limit. For reporting purpose, where we can get customer credit exposure which showing in FD32.

Go to t.code F.31 for an overview of the credit exposure, and also you can use s_ALR_8701212218 to overview the credit exposure.

 /'%.' By Shesagiri "'%.4 CIN Means Country India Version In Indian Taxing procedure, Excise Duty plays a vital role in manufacturing cenario¶s. Excise related configuration is known as CIN configuration. CIN Configuration is a topic in itself. Some info on CIN Configuration (it may not appear as understandable below, but if you check on screen, it will be understood better) Country Version India comes with four pricing procedures as follows: - JINFAC (Sales from manufacturing plants) - JINEXP (Export sales) - JINDEP (Sales from depots) - JINSTK (Stock transfers CIN: IMG > Logistics - General > Tax on Goods Movement > India > Basic Settings > Maintain Excise Registrations In this IMG activity, you maintain the data relating to your excise registrations. - Enter each of your excise registrations, specifying a four-character code for each Excise Registration Ids In this activity, you maintain excise registration IDs. You create one ID for each of your business's excise registrations. - For each excise registration in your business create a registration ID, and state: - Which taxes the registration covers (additional excise duty, special excise duty, and cess) Fields for any taxes that are not covered will be hidden in transactions involving excise duty. - The maximum number of items to be printed on each excise invoice - Whether you are allowed partial CENVAT credits Maintain Registration ID NUMBER, Excise code number, excise registration number

ECC Number: Specifies the organization's ECC number. Excise Registration Number: A number assigned to each premises or location that has registered as a manufacturer with the excise authorities. Every entity with an excise registration number is required to keep its own excise books. Excise range: Specifies the excise range in whose area the excise registration is located. Excise Division: Specifies the excise division in whose area the excise registration is located. Excise Collectorate: The code of the excise collectorate in whose area the excise registration is located. Indicator for confirming, AED usage Additional Excise duty Percentage. These are livable under the additional duties of excise act. These duties are in addition to basic excise duty and special excise duty. Example - Additional Excise duty is livable in case of textile products, tobacco and sugar. Similarly for SED CESS Number of Items in Excise Invoice Shows the maximum number of line items that the authorities allow per excise invoice. Dependencies - This information is used when you create an excise invoice in Sales and Distribution (SD) for factory sales and for other movements. This information is used to split the transfer postings' items into multiple subcontracting challans. Excise register set description: Description of the excise registers set. Partial CENVAT Credit: Indicates that the excise registration ID is allowed to credit only a portion of its input excise duty to its CENVAT account Dependencies - When you post a goods receipt, the system splits the input excise duty on the material into its deductible and nondeductible amounts. It posts the deductible duty to the appropriate CENVAT account, and adds the nondeductible duty to the material value. This information is also shown when you post the vendor's excise invoice. Maintain Company Code Settings. In this IMG activity, you maintain the data relating to your company codes. Document Type for CENVAT Postings. It controls, which document type the system uses when making CENVAT postings in Financial Accounting (FI). Here ED is document type for cenvat posting.

Indicator for providing debit account overwriting Debit Account Overwrite Indicator. X - Indicates debit accounts can be overwritten. Use In excise journal voucher transaction. It provides the flexibility to the user to enter the debit account of his choice depending on the nature of transaction. Automatic balance Indicator - Excise year start month. The calendar month marking the beginning of the excise year. This start month represents the month for the start of the excise invoice number range. The month 04 is entered here indicating April of the calendar year as the start month for excise invoices. Any change by the Excise authorities regarding start month should be taken care of by an entry in this field and initialization. Excise invoice selection procedure :Excise invoice selection type. To indicate the method opted by the company for selecting the excise invoice. It can be either earliest or latest invoices that were received. Number of excise invoices to be selected Indicates the number of excise invoices that needs to be selected in the excise invoice selection. Days to be considered for excise invoice selection Number of days from document date for excise invoice selection. Example - If the value of this field is 20 and today is 28-03-97. The excise invoice selection will show the related invoices only for the period 08-03-97 to 28-03-97. Document type for TDS FI posting: Financial accounting document type for TDS posting. Document type for FI posting on Utilisation Financial accounting document type for TDS posting. Indicator for item level excise duty round off - This indicator is to be used for deciding whether Item level excise duty amount rounding off is required during procurement cycle. If marked 'X' then the excise duty amount will be rounded off to the nearest rupee at the Purchase order level. This will not round off the CENVAT credit to be taken. If the duty amount is less than one rupee then no rounding is done Rounding off of Excise duty for outgoing excise invoice - You can round off the Excise amount to be paid during an outgoing Excise invoice by marking this indicator as 'X'. The rounding is done at the item level for each item where the amount is greater than 1 Rupee.

Immediate Credit on Capital Goods - Instructs the system, when you verify a goods receipt for capital goods, to immediately post half of the input excise duty to the appropriate CENVAT accounts. The rest is posted the CENVAT on hold account, for use in the following year. CVD Clearing Account - Specifies which G/L account the system credits when you take a CENVAT credit on countervailing duty in the Incoming Excise Invoices transaction. Exchange rate type - Key representing a type of exchange rate in the system. - You enter the exchange rate type to store different exchange rates. Example - You can use the exchange rate type to define a buying rate, selling rate, or average rate for translating foreign currency amounts. You can use the average rate for the currency translation, and the bank buying and selling rates for valuation of foreign currency amounts. Exchange rate type to be used for Export excise duty converts - When you are creating an Excise invoice for export sales then the exchange rate for duty calculation will be picked up using this Exchange rate type. Maintain Plant Settings - In this IMG activity, you maintain excise information relating to your plants. Plant Settings - In this activity, you maintain excise information relating to your plants. For each plant: - Specify whether it is a manufacturing site or a depot. - Assign it an excise registration ID. - You can assign the same ID to more than one plant, if required. Depot - Indicates that the plant in question is a depot. - Depots are required to prepare register RG 23D, and follow different procedures for goods receipt and invoice generation. - Number of goods receipt per excise invoice. - Multiple GR for one excise invoice, Single credit - Multiple GR for one excise invoice, multiple credit Maintain Excise Groups - In this IMG activity, you define your excise groups. For each excise group, you can also control how various excise invoice transactions will work.

Excise Groups - In this activity, you define excise groups. An excise group allows you to maintain a separate set of excise registers and excise accounts. The RG 23A, RG 23C and PLA serial numbers are created for an excise group. Recommendation - Under normal circumstances, excise authorities require every business to maintain only one set of excise registers and one set of accounts. But through exemption from the authorities, multiple books can be maintained. If your company has only one set of excise registers, then you need to maintain only one excise group. 1. Create one excise group for each set of registers that you need to keep. 2. Assign the excise groups to plants. 3. Maintain whether this Excise group is for a depot or not. If you receive only one consignment for an Excise challan then you can leave GR's per EI as blank. If you receive multiple GR's for a given Excise challan and would like to avail multiple credit mark the GRs per EI as 'Multiple GR's for one excise invoice, multiple credit'. Alternatively if you want to availa the credit only after all the goods receipts have been made mark it as ' Multiple GR for one excise invoice, single credit'. 4. If you want to automatically create Excise invoice during Sales cycle at the time of billing the tick the indicator 'Create EI' 5. During depot sales if you do not want to do RG23D selection and posting separately and would like to complete RG23D selection in one step mark the indicator 'RG23D Auto post'. This will post the selected records into RG23D automatically. You cannot cancel the selection later. 6. If the indicator 'Default GR qty' is marked system will default the Excise challan quantity on to the Goods receipt if the Excise invoice number is given in the pop-up. 7. If the indicator 'Folio no create' is marked system will generate Folio numbers for RG23D during receipt of excise invoice into depot. 8. 'Automatic posting' when ticked will post the Excise invoice other movements automatically along with creation in single step. 9. 'Create Part1 for Block Stock' when marked will create a Part1 during the receipt of material into Blocked stock . 10. 'Create Part1 for STO' when marked will create a Part1 during the receipt of material through inter plant transfers. 11. 'Create Part1 for consumption stock' when marked will create a Part1 during the receipt of material into consumption stock. Excise Group Governs which set of excise registers a business transaction will be included in. Following is the relation between excise group, plant and registration. - In define excise groups in Customizing. Then, in transactions involving excise duty, for example, when you post a vendor's

excise invoice, you specify which excise group you are using. This information tells the system which G/L accounts to post the excise to. At the end of the period, when you come to prepare your excise registers, you create different sets for each excise group. Indicates that the plant in question is a depot. - Depots are required to prepare register RG 23D, and follow different procedures for goods receipt and invoice generation. - GR Per Excise Invoice - Multiple GR for one excise invoice , Multiple credit - Multiple GR for one excise invoice , Single Credit Create Excise Invoice Automatically - Instructs the system to automatically create a Sales and Distribution (SD) excise invoice immediately you create a commercial invoice or a pro forma invoice. The excise invoice is created in the background. - If you want to make use of this function, you must also define the default plant, excise group, and series groups in Customizing for Sales and Distribution (SD), by choosing Excise Group - Series Group Determination. RG23D Sales Creation and posting option - RG23D Automatic Option if selected will create Depot excise invoice by posting the selection of excise invoices in single step. If this is not selected then you need to separately do RG23D selection followed by PGI and then RG23D verification and posting. If you need automatic posting of RG23D selection then the Post Goods Issue should have been completed before running RG23D selection. Default excise qty in GR - If this indicator is ticked then while doing Goods Receipt using 'MB01' system will default the excise invoice quantity on to the Goods receipt document. Folio number for depo Posting - If this indicator is marked then while creating Excise invoice for other movements system automatically does the Verify and Post. You need not separately Post the excise invoice Also we can set indicator for creation of part 1 for: - Blocked stock - Stock transport order - Consignment stock Maintain Series Group - In this IMG activity, you define the different excise series groups within your company. Series groups allow you to maintain multiple number ranges for the outgoing excise documents. Based on excise regulations and

exemptions from the authorities you can maintain multiple number series for outgoing documents. But each of these series has to be declared to the excise authorities. - Define excise series groups based on type of outgoing document - Assign series group to excise registration ID - If no financial postings are required for an Excise invoice in this seris group then you tick the 'No utilization' indicator. - If the CENVAT has to be paid immediately and you need not wait for the Fort nightly payment then mark the 'Immediate Utilization' Iindicator. Example - You could define two series groups, group 001 for excise invoices, and group 002 for 57 F4 documents. - No account postings for CENVAT in sales cycle - No utilization Flag If you do not need any CENVAT utilization for an excise invoice but would like to just generate an excise invoice then you need to mark this indicator. If the flag is checked then system will create an Excise invoice in the given Series group but there will not be any account postings or Part2 postings. Immediate Utilization of CENVAT - Specifies that when you create an excise invoice, the system immediately pays the amount from CENVAT and creates the Part II entry. Such invoices will not be listed for fortnightly utilization. If you have both fortnightly and immediate utilization for the same excise group, the account determination within CIN IMG should point to the ED interim account. Account determination for immediate payment will be done exactly the same as being done for fortnightly utilization program. Maintain Excise Duty Indicators - In this IMG activity, you maintain the excise duty indicators. IMG > Logistics - General > Tax On Goods Movement > India > Basic Settings > Determination of Excise Duty > Select Tax Calculation Procedure In this IMG activity, you specify which tax procedure you want to use for determining excise duties and sales taxes on input materials in India. - If you use condition-based excise determination, use a copy of the tax procedure TAXINN. - If you use formula-based excise determination, use a copy of the tax procedure TAXINJ. This tax procedure also supports condition-based excise determination, so that you can work with both concurrently.

We strongly recommend that new customers use condition-based excise determination. Note that once you have started using a tax procedure, you cannot switch to another one, otherwise you will not be able to display old documents. Maintain Excise Defaults - In this IMG activity, you define which tax procedure and pricing condition types are used in calculating excise taxes using formula-based excise determination. If you use condition-based excise determination, fill out the CVD cond. field and leave all the others blank. If you use formula-based excise determination, fill out all of the fields as follows: - Enter the tax procedure and the pricing conditions that are relevant for excise tax processing. - Specify the purchasing and sales conditions types used for basic excise duty, additional excise duty, special excise duty, and cess. - Specify the conditions in the sales order that are used for excise rates. - Specify the countervailing duty condition type used for import purchase orders. See also : SAP Library -> Logistics -> Country Versions -> Asia-Pacific -> India -> Materials Management (MM) -> Condition-Based Excise Determination and -> Formula-Based Excise Determination. IMG > Logistics - General > Tax On Goods Movement > India > Basic Settings > Determination of Excise Duty > Condition-Based Excise Determination When you enter a purchasing document, for example, a purchase order, the R/3 System automatically calculates the applicable excise duties using the condition technique. Features : The standard system comes with two tax calculation procedures. TAXINN is only supports condition-based excise determination, whereas TAXINJ supports condition-based excise determination and formula-based excise determination. Both tax procedures contain condition types that cover all of the excise duties and sales taxes applicable. Since the exact rates of excise duty can vary on a large number of factors, such as which vendor you purchase a material from, or which chapter ID the vendor stocks the material under, you create condition records for every sort of excise duty. When you come to enter a purchasing document, the system applies the excise duty at the rates you have entered in the condition records.

Customizing : Make the settings in Customizing Basic -> India -> for Logistics ± General, by choosing Taxes on Goods Movements Account -> Excise Duties Using Condition Technique and «-> Settings Determination. These activities include one activity where you define a tax code for condition-based excise determination. Master Data - Create condition records for all excise duties that apply, and enter the tax code for condition-based excise determination in each. Day-to-Day Activities - When you enter a purchase order or other purchasing document, enter the tax code for condition-based excise determination in each line item. The system then calculates the excise duties using the condition records you have created. When the ordered materials arrive, you post the goods receipt and the excise invoice. The system posts the excise duty to the appropriate accounts for deductible input taxes when you enter the excise invoice. Creating Condition Records for Excise Duty 1. In the command field, enter FV11 and choose . 2. Enter the condition type that you want to create a condition record for and choose . The Key Combination dialog box appears. 3. Select the combination of objects that you want to create the condition record for. On the dialog box, Control Code means "chapter ID." So, for example, to create a condition record for a tax that applies to a combination of country, plant, and chapter ID, select Country/Plant/Control Code. 4. Choose . 5. Enter data as required. - In the Tax Code field, enter the dummy tax code that you have defined. 6. Save the condition record. Formula-Based Excise Determination - When you execute a business transaction involving materials that are subject to excise duty, the system automatically calculates the duty for you. In order for the system to be able to determine which rate of excise duty to apply, you must have maintained all the data on the Excise Rate Maintenance screen, which you can Master Data®access from the SAP Easy Access screen by choosing Indirect Taxes Excise Rate Maintenance. You maintain the following types of data: - Plant master data

You assign each of your plants an excise duty indicator. You can use the same indicator for all the plants with the same excise status from a legal point of view, such as all those that are in an exempt zone. See also the information about manufacturers that are only entitled to deduct a certain portion of the duty (see Partial CENVAT Credit). - Vendor master data For each of your vendors with the same excise status from a legal perspective, you define an excise duty indicator. You must also specify the vendor type ± for example, whether the vendor is a manufacturer, a depot, or a first-stage dealer. You must also stipulate if the vendor qualifies as a small-scale industry. For each permutation of plant indicator and vendor indicator, you then create a final excise duty indicator. - Customer master data Similarly, you assign the same excise duty indicator to each of your customers that share the same legal excise status. Again, for each permutation of plant indicator and customer indicator, you then create a final excise duty indicator. - Material master data Each material is assigned a chapter ID. - Excise tax rate For every chapter ID and final excise duty indicator, you maintain the rate of excise duty. If your business only qualifies for partial CENVAT credit, you must customize your system accordingly. Let us consider an example to illustrate how the system determines which rate of excise duty to apply to a material. Assume you are posting a sale of ball bearings to a customer. The system automatically determines the rate of excise duty as follows: 1. Looks up the customer master data to see what status you have assigned the customer. Let's assume you've assigned the customer status 3. 2. Looks up the plant master data to see what status you have assigned the plant. Similarly, your plant has status 2. 3. The system looks up the table under Excise Indicator for Plant and Customer to see what the final excise duty indicator is for customer status 3 and plant status 2: It is 7. 4. The system determines the chapter ID of the ball bearing for the plant. Let¶s assume the chapter ID at plant for the ball bearings is 1000.01. 5. Finally, the system looks up the table under Excise Tax Rate to see what rate of duty applies to chapter ID 1000.01 under status 7.

Define Tax Code for Purchasing Documents - In this IMG activity, you define a tax code for the purposes of calculating excise duty when you enter purchasing documents. Only carry out this activity if you use condition-based excise determination. - Create a new tax code, and set the tax code type to V (input tax). Do not make any other settings for it. - Assign Tax Code to Company Codes In this IMG activity, assign the tax code for purchasing documents to the company codes where it will be used. Only carry out this activity if you use condition-based excise determination. Classify Condition Types - In this IMG activity, you specify which condition types you use for which sort of tax. Note that this only applies to condition types that you use with the new excise determination method. The system uses this information when you create a document from another one. For example, when you enter an incoming excise invoice from a purchase order, or when you create an outgoing excise invoice from a sales order, the system determines the various excise duties in the excise invoice using the information that you have entered here. In addition, when you create a purchasing document, the system only uses the condition types that you enter here. - For taxes on purchases, use the condition types contained in the tax procedure. - For taxes on sales, use the condition types contained in the pricing procedures. The standard system comes with sample settings for the tax calculation procedures and pricing procedures. Use these settings as a basis for your own. IMG > Logistics - General > Tax On Goods Movement > India > Account Determination Define G/L Accounts for Taxes - In this IMG activity, you specify which G/L accounts you will use to record which taxes. Requirements - You have set up G/L accounts for each of the processing keys listed below. - Assign an account to each of the following posting keys. The accounts for VS1, VS2, and VS3 are used as clearing accounts during excise invoice verification. - VS1 (basic excise duty) - VS2 (additional excise duty) - VS3 (special excise duty) - VS5 (sales tax setoff) - MWS (central sales tax) - MW3 (local sales tax)

- ESA (service tax) - ESE (service tax expense) Specify Excise Accounts per Excise Transaction - In this IMG activity, you specify which excise accounts (for excise duty and CENVAT) are to be posted to for the various transaction types. Enter all the accounts that are affected by each transaction type. If you use sub transaction types, enter the accounts for each sub transaction type as well. Transaction type UTLZ is used for determining accounts only while posting excise JVs and also if the payment of excise duty has to be done fortnightly. The fortnightly CENVAT payment utility picks up the credit side accounts from the transaction types of GRPO, EWPO, and TR6C for determining the CENVAT and PLA accounts. There is no separate transaction type for fortnightly payment. Example: - Excise TT DC ind Account name - GRPO CR CENVAT clearing account - GRPO CR RG 23 BED account - GRPO DR CENVAT on hld account Specify G/L Accounts per Excise Transaction - In this IMG activity, you assign the excise and CENVAT accounts to G/L accounts. When you come to execute the various transactions, the system determines which G/L accounts to post to by looking at the: - Excise group - Company code - Chart of accounts Furthermore, if you want separate account determination settings within an excise group, you can also use sub transaction types. Requirements You have already: - Defined the G/L accounts - Defined the excise groups - Maintained the transaction accounts Activities - For each excise group, assign the excise and CENVAT accounts to G/L accounts. For most businesses, one set of accounts will suffice for all transactions. Note : you need not remit the CENVAT to the excise department immediately, so maintain the credit account for transaction type DLFC as an excise duty interim account. This will be set off when you remit the duty. Config setting needed to be done in order to get the Excise Details Screen in Material Master.

Even though this functionality is available in enterprise version, a small configuration step has to be made in Screen Sequences for Material Master. Following document helps you to do this configuration. - Material Master à Logistics General 1. Go to IMG Define Structure of Data Screen for each Configuring the Material master Screen Sequence. 2. Select your screen sequence. Usually it would be 21. Select the same and click on Data Screen in the left frame. 3. Once the data screens are exhibited, select data screen no. 15, ie. SSq. 21and Scrn 15, which is ³Foreign Trade: Import Data´. Select the same and click on Sub screens in the left frame. 4. Go to the last sub screen i.e. 21-15-6 - SAPLMGD1- 0001 and select the same. Click on tab view sub screen and ensure that the sub screen is blank. 5. Now in the last sub screen i.e. no.6 you delete SAPLMGD1 ± 0001 and instead add SAPLJ1I_MATERIAL_MASTER and in the screen no. 2205. 6. Save the setting. 7. Create a Material Master and check whether in Screen Foreign Trade ± Import, Excise related sub screen appears.




 You need to receipt the rejected goods through SD Module (VA01 - Sales Order type RE). The steps are as follows : 1. Create a return request. (Using Sales Order in SD) 2. Create outbound delivery according to return request. 3. If the setting is correct in the outbound delivery screen SAP will automatically switch post goods issue button into post goods receipt. The setting is in sales order item category and delivery type. 4. In the standard system the movement type used is 651. 5. After post goods issues receipt is done using outbound delivery, the quantity is placed in blocked stock without value updating. 6. You will then decide if the return quantity are indeed bad stock or not.

7. Transfer Posting from block stock to unrestricted stock (mvt type 453), this will have accounting effect (Debit Inventory, Credit COGS) 8. Goods Issue to scrap account how to create new titles which can be used in creating the "address" view on the Vendor master.{T-Code: XK01} In config go to Basis Components --> basis services --> Address Management --> Maintain title texts Do you have a SAP SD Question? "$


 
"'

4


 
$


2""

$


4 A return is a sales document used in complaints processing for when a customer sends goods back. You enter a return in the system if the customer returns damaged goods, or goods that had been delivered for sale on approval. The return causes the system to: Register the receipt of goods using a returns delivery, and post the goods to stock (for example, blocked stock). Create a credit memo, once you have checked the goods and approved the complaint. A return is another type of sales document like a standard order. The return triggers the following functions: - Delivery (returns delivery) - Billing (for creating a credit memo) When you create a return based on a complaint, you: Post the goods to your warehouse for checking And then, implement one of the following activities: - Approve the complaint and create a credit memo - Approve the complaint, and implement a free of charge subsequent delivery based on the return - Reject the complaint PGI (Post Goods Issue) may be cancelled by Transaction code VL09. The accounting document is just the reverse of the original PGI document. In my company, we use project stock (movement type 601 Q for PGI). VL09 creates the movement type 602 Q. But rather than VL09, the generally accepted method in

my company for the reverse items is to use the movement type 653, "back to the to the storage location." The accounting document takes the cost "from" the project and moves it back "to" the storage location. The movement types are entered in the schedule lines in customizing, which are then assigned to the item categories. However, in this process, "no invoice" takes place. If you have a delivery related invoice, it should be cancelled beforehand. If you do not give replacement, the Customer Account needs to be credited. Please do not forget to create a Billing document (Formally Return Credit Memo) with reference to return delivery. It is very important in order to close the cycle. If you do not create a return credit memo, your delivery will keep appearing in the "Billing Due" list and with status "Being processed". When you create a return order type RE, the billing type is picked up as RE (Return Credit Memo) automatically. When you are creating a replacement, you can create a replacement order, delivery, and billing. To create the replacement order, you can define an order type by copying from order type OR. In the copy control, you can define the relevant item categories from RE to OR. You can make reference Mandatory for this order type. The delivery type for this replacement order type will be LF and billing type F2. "$


 
"'

4


 
$


2""

$


4 A return is a sales document used in complaints processing for when a customer sends goods back. You enter a return in the system if the customer returns damaged goods, or goods that had been delivered for sale on approval. The return causes the system to: Register the receipt of goods using a returns delivery, and post the goods to stock (for example, blocked stock). Create a credit memo, once you have checked the goods and approved the complaint. A return is another type of sales document like a standard order. The return triggers the following functions: - Delivery (returns delivery) - Billing (for creating a credit memo)

When you create a return based on a complaint, you: Post the goods to your warehouse for checking And then, implement one of the following activities: - Approve the complaint and create a credit memo - Approve the complaint, and implement a free of charge subsequent delivery based on the return - Reject the complaint PGI (Post Goods Issue) may be cancelled by Transaction code VL09. The accounting document is just the reverse of the original PGI document. In my company, we use project stock (movement type 601 Q for PGI). VL09 creates the movement type 602 Q. But rather than VL09, the generally accepted method in my company for the reverse items is to use the movement type 653, "back to the to the storage location." The accounting document takes the cost "from" the project and moves it back "to" the storage location. The movement types are entered in the schedule lines in customizing, which are then assigned to the item categories. However, in this process, "no invoice" takes place. If you have a delivery related invoice, it should be cancelled beforehand. If you do not give replacement, the Customer Account needs to be credited. Please do not forget to create a Billing document (Formally Return Credit Memo) with reference to return delivery. It is very important in order to close the cycle. If you do not create a return credit memo, your delivery will keep appearing in the "Billing Due" list and with status "Being processed". When you create a return order type RE, the billing type is picked up as RE (Return Credit Memo) automatically. When you are creating a replacement, you can create a replacement order, delivery, and billing. To create the replacement order, you can define an order type by copying from order type OR. In the copy control, you can define the relevant item categories from RE to OR. You can make reference Mandatory for this order type. The delivery type for this replacement order type will be LF and billing type F2. B
$
$

 Ä
 

. 

  
  % =
 
 
 
  

    
  
 
=


  )
  
 


 a 
  

  
   

 
  
     
 



: Generally the usage of customer group is to group the customers into One group so that whenever you want to give some additional discount to that customer group then you can give Example : Say you have 2 customers and 2 customers have 2 pricing groups. Customer A belongs to Wholesale Pricing grp and Customer B belongs to Retail Pricing grp. Maintain a condition record With the help of the Customer / Pricing grp key combination. Now for wholesale you give extra discount and for retail you give less discount. Now when you create the sales order with Customer A then he will be getting extra discount But if you create the sales order with Customer B then he will be getting normal discount


$
"

$



 !
0 Suppose if you have 3 price groups say price group1 price group2 and price group3. Say there are 10 customers A to J. - You are assigning customers A to D in price group 1. - You are assigning customers E to G in price group 2. - You are assigning customers H to J in price group 3 in their respective CMRs.


$!


$!
 
"
: In A7@@ the table with price group 1 is maintained discount of 5 % In A7@@ the table with price group 2 is maintained discount of 6 % In A7@@ the table with price group 3 is maintained discount of 7 % So in sales order the customers A to D will get 5 % discount and customers E to G will get 6 % discount and customers H to J will get 7 % discount.

%


$
$4

Please go through this IMG path then define the Customer pricing group. SPRO --> IMG --> Sales and Distribution --> Basic Functions ------> Pricing --> Maintain Price relevant master data fields ---> Define Pricing group for Customers. Transaction code --> cA

'5'

"/ 
"
/'

"4 All the customizing is in SD/Master Data/Bussiness Partner/Customers/Customers hierarchy 1) Define hierarchy type: just put and ID and a name to the new hierarchy. 2) Set partner determination: if you want to user the hierarchy in price determination, then, in the orders, at the header level, you have to have a Partner Procedure with a partner function for each level. In the partner procedure, in each partner function you must indicate the source partner function. With this informacition, in the order, you obtain the bussiness partner for each partner function. 3) Assign acount groups: you indicate which accounts groups are allowed for being part or your hierarchy. 4) Assign sales areas: symple you indicate wich sales areas are allowed in your hierarchy. (Here you can customize common sales areas, just for not having to build de hierarchy in all the different sales areas). 5) Assigning hierarchy type for pricing: you indicate which classes of documentos uses hierarchy in pricing determination. It is possible to maintain so called customer hierarchies. This might be useful when for example you create a condition discount for a customer that is part of such a hierarchy structure. All subnodes in the hierarchy below that customer, will thus receive the same discount. Customer hierarchy setup, firstly decide the hierarchy type to be used. The standard is type A.

You can also assign a partner function to the customer so that the higher level customer in the hierarchy is copied into a sales order as a partner function - but you don't need that right? Next assign your customer account group to the hierarchy type. And enter the combinations that will be allowed for creating the hierarchy. You want to assign a ship-to to a payer. So enter the ship to account group and enter the payer account group as the higher level. You must also make an entry for permitted sales area assignments. So if you want to a hierarchy for customers in the same sales area then enter the sales area and enter the same one as the higher level sales area. All these settings can be found in the IMG. Under SD - master data - business partners - customers - customer hierarchy You use for example customer hierarchy when you have an company like Unilever and you agree both on a discount. Unilever does have different locations / businesses and you have to maintain the discount for all customers. If you use a customer hierarchy you can maintain the discount for the partner in the top of the hierarchy and in this way it will be valid for all customers in the hierarchy.  /#$!:

/
c 
"
 ""

$"
"4 Alphanumeric character string for grouping materials by combining various characteristics. The product hierarchy is used for evaluation and pricing purposes. A product hierarchy is an alphanumeric character string which consists of 18 characters at the most. Product hierarchy thus define the product and its composition. To take an example, a product hierarchy could be 00010002000300040005. The first four characters 0001 could indicate that the product is a car. The next four characters could indicate 0002 the plant in which the car has been manufactured. The third set of characters could indicate the color of the car. The next set may determine its engine capacity and so on. Thus, the product hierarchy helps in defining the product composition.

Product hierarchy is defined in tcode v/76 according to levels. Then it is added as a user defined characteristic in tcode KES1. It is used for sales reporting functionality based on the product hierarchy. It is used for profitability analysis reporting. /



"

$"
",

 
! 
-0 When a sales cycle happen then after billing document a PA (profitability analysis) document is created in which product hierarchy is populated and used in CO-PA reporting. 3$"

$"
""

$!
$$



 
4 Product Hierarchy is used for Profitability analysis. You can have maximum of three level in SAP for a product. You have to give the product hierarchy in Material master Sales- Sales Org -2 view. You can define the product hierarchy in IMG settings from the following path Customizing is to be made in: IMG -- Logistics General --> Material Master --> Settings for Key Fields --> Data Relevant to Sales and Distribution --> Define Product Hierarchies --> Maintain Product Hierarchy Product hierarchies can be created using code OVSV. A product hierarchy is assigned to the material master record. The hierarchy is broken down into specific levels, each level containing its own characteristics. A product hierarchy is recorded by the sequence of digits within a hierarchy number. The hierarchy number can have a maximum of 18 digits with a maximum number of nine levels. Thus by assigning the hierarchy number to the material, one can determine a classification of the material. This hierarchy can be used in pricing with each level being used as field in the condition technique.

It¶s like if you are having category CAR. In that many cars come into picture. CAR>>MARUTI>>SX4, Swift, zen, alto. B>> 01 >>01 Then from above example B0101 is the hierarchy for SX4. So in that hierarchy many cars come, like variants and all the things. In this way you can take e.g. of wood products also. It shows the next level of the product. How many levels that product are having.

#'
 
"


": Product hierarchies are the domain of materials management. A product hierarchy is assigned to the material master record. This hierarchy is broken down into specific levels, each level containing its own characteristics. A product hierarchy is recorded by the sequence of digits within a hierarchy number. This hierarchy number may have a maximum of 18 digits with a maximum of 9 levels. The custom Product hierarchies can be maintained in V/76.


".!
"A

: In the standard system, the product hierarchy consists of up to 3 levels. The first and second levels have 5 digits and the third level has 8. The maximum number of digits is 18 and the maximum number of levels is 9. You can define hierarchy nodes at the individual levels of the product hierarchy. The product hierarchy can be structured via DDIC structure PRODHS. In the standard system, a product hierarchy can be created with up to three levels. The individual levels can contain the following number of digits: 

!

: 15 25 38

This can be changed as of Release 3.0, where it is possible to extend the maximum number of levels to 9. If you want to change the standard setting of PRODHS, e.g. you want to change the number of levels, proceed as follows: 1. Create an appropriate domain in the Data Dictionary (type CHAR with the required length). 2. Assign these domains to the standard data elements PRODH1, PRODH2, ..., PRODH9. Please note that you should use these standard data elements. 3. Change the structure PRODHS by creating or deleting fields with reference to the data elements. Choose ZZPRODHN as field name, where n is the position of the field in the structure PRODHS. You want to change the structure of the product hierarchy from 5/5/8 digits to 5/5/5/3. Proceed as follows: Create the following domains: ZPRODH3 with length 5, category CHAR, ZPRODH4 with length 3, category CHAR, '"

 c/: Structure PRODHS in the standard system: Structure Fields Data element Category Length PRODHS -> PRODH1 PRODH1 CHAR 5 PRODH2 PRODH2 CHAR 5 PRODH3 PRODH3 CHAR 8

'"

3$
: Structure Fields Data element Category Length PRODHS -> PRODH1 PRODH1 CHAR 5 PRODH2 PRODH2 CHAR 5 PRODH3 PRODH3 CHAR 5 ZZPRODH4 PRODH4 CHAR 3 Please take help of ABAPER in extending the levels of Product hierarchy. Configure for Product hierarchy at : SPRO-> IMG-> Logistics - General-> Material Master-> Settings for Key Fields-> Data Relevant to Sales and Distribution-> Define Product Hierarchies 


>
$

$  Y)Y 
7>Y2 3Y/ 45Y
Y YY4  )Y 4 -,,Y Y „„„„„„„„„„„„„„„„„„„„„„(  Y3Y„„„„„„„„„„„„„„„„„„„„„„„„„„Y Y &4)Y+2&) )/&Y> />YMY)YY  Y)Y#YYY 
 Y „YYYYYYYYYYYYYYYYYYYYYYYYYY)Y1#Y
'Y$Y Y /Y Y

)Y/&452 , YMY)Y3Y*
Y#Y "YY
 Y YY &4Y2
Y YYYY@ 4 Y>(&>Y YYYY#Y 3Y YYYYYY,Y YYYYYYYY54 Y-( 4Y Y+(4-Y% -/4Y2Y( ),Y$'*Y YYYYYYYY(+Y2
'Y 4Y;Y4=()Y4 (+Y YYYYYYYY(+Y$'*Y?Y>=>Y YYYYYYYYYY45+,5Y Y YYYYYYYYYY45+,5YY YYYYYYYY4 (+Y YYYYYYYY Y?Y Y0YY YYYYYY4 ,Y YYYYYY45+,5Y Y YY4  &4Y Y „„„„„„„„„„„„„„„„„„„„„„„„Y&/Y5,/)( 4Y YY „„„„„„„„„„„„„„„„„„„„„„„„„„„„„„Y „)YY&
'5
 Y3Y" YY1
Y#Y
 Y „YYY2(  )'YY YY() 3Y'YY3YY „YYYYYYYYY2YY'Y $*Y +,5YY YY-,,Y )YY@ 454YY?YY YYYY 32YYYY?Y>=>Y YYYY 321' Y?Y21' Y YYYY 32 3Y?Y2 3Y YYYY 32 Y?Y2 Y YYYY 323$Y?Y23$Y YYYY 32YYY?Y2Y YYYY 4 Y 3Y YY4 -,,Y 4 +,5YYYYYYYYYYYYYYYYYYYYMY Y „F222222222)Y3YYY1
Y#YYY#Y 3Y22„Y „222222222222222222222  Y)'Y 32222222222222222222222222„Y „FYYYYYY+YY&4-4 )(, Y „F22222222222222222222222222222222222222222222222222222222222222222222„Y „222222222222222222222222222222222222222222222222222222222222222222222„Y +,5Y Y YY/-( 4Y YY+,5 )Y ,-,5Y?YY YY@5()4721 >> )YY21 Y>,Y ,>Y )Y8HY21 Y >,Y>Y )YCY21 >,Y%
 )Y
 YY>Y YY+,5 )Y ,-,5Y,++Y YY/-( 4Y YY-,,Y )Y 3Y YYYY, Y 4Y,+Y 32Y YYYYYY(+Y2'*YNLYY YYYYYYYY@5()47.Y21 Y )YY21  )Y8HY21  )YCY21 Y YYYY@5()47.Y21  3221  )Y8HY21  )YCY21 Y YYYYYY4-&4Y YYYYY@5()47Y21  3221  )Y8HY21  )YCY21 Y YYYYYY4 (+Y YYYY4 , Y YYYY@5()47.Y21 Y )YY21  321' 21 Y YYYYYY 32 Y21 Y 32 3Y 323$Y Y

YYYY )Y- &)Y YYYYYY&/Y YYYYYY/-( 4YY+,5 )Y ,-,5Y?Y9Y YYYYYY@5()47.Y21 Y )Y!Y>)Y 
Y#YY 7>Y YYYYYYYYYYYYYYYYYYYY 32 3Y/ 45Y 32 3Y YYYYYY+,5 )Y ,-,5Y,++Y YYYYYY/-( 4Y YYYY4  )Y YY4 -,,Y YY Y?YY YY+544Y 3Y 4 +,5YYYYYYYYYYYYYYYYYYYYM&4-4 )(, Y Y „Y)YY 1 YY
Y#Y$YY
YY#YY „YYYY2Y Y YY3YY1 "YYY$YY ::::..Y „YY2'
YY $YY" YYY3Y YY"1Y Y1YY Y Y „F22222222222222222222222222222222222222222222222222222222222222222222„Y „FYYYYYY+YY )4 , Y „F22222222222222222222222222222222222222222222222222222222222222222222„Y „YYYYYYY*Y „222222222222222222222222222222222222222222222222222222222222222222222„Y +,5Y Y YY8Y?Y2HY YY& (+)Y8Y-4+)Y:YY- 4&Y YY@ (-4Y8YNLY>>Y YYYY& (+)Y8Y5( )Y YYYYY?Y80Y YYYY(+YYNLY>>Y YYYYYY , )4 )4YY9Y( ),Y9Y YYYY4 (+Y YY4 @ (-4Y YY!Y?Y98Y YYDY?Y908Y YY9Y?Y90Y YY , )4 )4Y9YDY!Y( ),Y9Y YYY?Y9Y „YY&,5)YY:YY „YY4-4)4Y E 4 )Y/-( )4&Y+5,YY , 5( YY 4 +,5YYYYYYYYYYYYYYYYYYYYM )4 , Y Y Y „Y Y3YY "Y## Y$ Y#Y Y'YY4 />YY

Y Y „F222222222@ Y
Y "Y Y&Y,"  22222222222222222„Y „FYYYYYY+YY,5 (& )(, Y „F22222222222222222222222222222222222222222222222222222222222222222222„Y „YYYYYYY*Y „222222222222222222222222222222222222222222222222222222222222222222222„Y +,5Y"  Y YY&4-4 )Y#O1' YO YO 3YO3$YO
Y( ),Y21' Y 2 Y2 323$Y2Y+5,YY1$Y &Y#Y( 45YE,( Y YYYYYY1'$Y &YY, Y#O1' Y?YO1' YY( 45YE,( Y1Y &YY, Y #O1' Y?YO1' Y@ 454YYO
Y( YY YO1$"Y?Y1$"Y

YYYY 4 YY YY4 &4-4 )Y 4 +,5YYYYYYYYYYYYYYYYYYYYM,5 (& )(, Y Y Y „F222222222@
Y&Y,"  YY Y,"  222222222222„Y „FYYYYYY+YY,5 (& )(, B4-&4Y „F22222222222222222222222222222222222222222222222222222222222222222222„Y „YYYYYYY*Y „222222222222222222222222222222222222222222222222222222222222222222222„Y +,5Y"  BY YY&4-4 )Y#O1' YO YO 3YO3$YO
Y( ),Y21' Y 2 Y2 323$Y2Y+5,YY1$Y &Y#Y( 45YE,( Y YYYY1'$Y &YY, Y#O1' Y?YO1' YY( 45YE,( Y1Y &YY, Y YYYY#O1' Y?YO1' Y@ 454YYO
Y( YY Y YYYY 4 YY YY4 &4-4 )Y 4 +,5YYYYYYYYYYYYYYYYYYYYM,5 (& )(, B4-&4Y Y „F222222222222@ Y& "Y
Y'Y "Y $*222222222222„Y „FYYYYYY+YY /&B,5 Y „F22222222222222222222222222222222222222222222222222222222222222222222„Y „YYYYYYY*Y „222222222222222222222222222222222222222222222222222222222222222222222„Y +,5Y
B"Y YY&4-4 )Y#O1' YO YO 3YO3$YO
Y( ),Y21' Y 2 Y2 323$Y2Y+5,YY1$Y &Y#Y( 45YE,( Y YYYYYYYY1'$Y &YY, Y#O1' Y?YO1' YY( 45YE,( Y1Y &YY, Y YYYYYYY#O1' Y?YO1' Y@ 454YO
Y( YY YO1$"Y?Y1$"Y Y YYYYYYYO$


Y?Y$


Y Y YYYY 4 YY YY4 &4-4 )Y 4 +,5YYYYYYYYYYYYYYYYYYYYM /&B,5 Y Y „F222222222222@
Y
Y'Y3
Y "Y $*22222222222„Y „FYYYYYY+YY /&B,5 B4-&4Y „F22222222222222222222222222222222222222222222222222222222222222222222„Y „YYYYYYY*Y „222222222222222222222222222222222222222222222222222222222222222222222„Y +,5Y
B"BY YY&4-4 )Y#O1' YO YO 3YO3$YO
Y( ),Y21' Y 2 Y2 323$Y2Y+5,YY1$Y &Y#Y( 45YE,( Y YYYY1'$Y &YY, Y#O1' Y?YO1' YY( 45YE,( Y1Y &YY, Y #O1' Y?YO1' Y@ 454YO
Y( YY YO$


Y?Y$


Y Y YYYY 4 YY YY4 &4-4 )Y

'"

0A("
0
90

#c$#$
/   OOH/

"
%
! "
 
$"
 "

$

2"



$0"% 
4"

"4 For getting any output either by print, Fax, or any media you have to do output determination. output determination is also carried by Condition techniques. The detail procedure for Output Determination is : OutPut Determintaion : Output is a form of media from your business to one of its business partners or it can be within the organization. The output can be sent to any of the partners defined in the document. Outputs are usually in the form of Order Confirmations, Freight List, Delivery Notes, Invoices & Shipping Notifications. Determining form of output is output determination. Types of Output: Print Output, Fax, Telex, E-Mail & EDI (Electronic Data Interchange) --> PRINT OUTPUT: Configuration path: ( following are the steps) 1) SPRO-> IMG-> Basic Functions-> Output Control-> Output Determination-> Output Determination using Condition Technique- >Output Determination for Sales Documents (or you can use output determination for billing documents depending on your requirement). 2) Create Condition Table: select the field Sales Doc Type from field catalog & Save 3) Maintain Access Sequence: 4-digits code & description. 4) Assign condition table to access sequence. Select Accesses line item and Go To Fields. Fields will display the fields we have selected in the condition table i.e. sales doc type. Maintain Output Types: AF00: Inquiry AN00: Quotation

BA00: Order Confirmation LD00: Delivery RD00: Invoice Select BA00 & Copy & Rename. Give the same 4-digit code as given to access sequence. You Can Maintain: Languages of Output Partners (to whom you need to send output) Print Program- print specification Sap Script- layout Assign Output Types to Partner Functions: go to new entries & assign your output type to partner functions. Maintain Output Determination Procedure: V10000 (Standard Procedure). Go to new entries and create your own 6-digit code with description. Select the procedure, go to Control Data. Here mention the output type i.e. condition type and leave requirement and manual only columns as blank. Determination Rule: link the 6-digit procedure code to doc types. Create Condition Records: VV11. Select document type and click on Communication. Mention partner function, medium, time. Output device: LP01, Spool request Name: SD_003, Suffix 2: order_confir & flag on print immediately. Once you press enter you will come across 2 key combinations: Sales organisation/ Customer Number: fill SO, Customer No, Partner Function Abbreviation, Partner to whom the output should be sent, time, medium, language. It contains: Sales Orgnisation, Customer, Partner Function (The abbreviated form of the name that identifies the Partner) (During output determination, the system determines the recipient of the output from the master record for the specified partner function. In this field, you can explicitly specify a recipient that will override the

standard partner. There must also be a master record for the partner that is specified explicitly.), Medium, Time & Language.} Order Type: Document Type, Partner Function (abbreviation), Partner, Medium, Time & Language. Path For Output Determination For Sales Documents: Logistics -> Sales/distribution > Master data -> Output -> Sales Document -> Create (t-code VV11) Path for Output Determination for Delivery Documents : Logistics -> Sales/distribution -> Master data -> Output -> shipping -> Create ( t-ode VV21) Path for Output Determination for Billing Documents : Logistics -> Sales/distribution -> Master data -> Output -> Billing Document -> Create ( t- code VV31) lease follow the below path: IMG - Logistics Execution - Shipping - Deliveries - Define Reasons for Blocking in Shipping - Execute - Define Reasons for Blocking in Shipping Here select the delivery block that is blocking your order/delivery, and uncheck if the option Print is checked. Display View "Deliveries: Blocking Reasons/Criteria": Overview DB Delivery block descr Order Conf. 01 Credit limit 02 Political reasons 03 Bottleneck material 04 Export papers missng 05 Check free of ch.dlv 06 No printing 07 Quantity Change

Print DDueList

SpK

SpW

08 Kanban Delivery

! 
: Indicates whether the system automatically blocks output for sales documents that are blocked for delivery. Example : In the case of sales orders that are blocked for delivery because of credit reasons, you may want to block the printing of order confirmations. .
: The particular output that is affected by a delivery block is determined in output control.

:If the document is exceeds by the credit limit output type will not determine and as well as we should not give the output type in sales order. We have to assign the routine 2 to sales order output types and 3 routine to delivery output types to restrict from output if the docuement exceeds by credit limit.

 
c
 
c
 
 SAP Sales Order Processing system allowed you to manage customer orders in a logical ways. This paper will introduce to you the various features of the Sales Order Processing under the SD modules. #!
'
 Purpose of SAP Sales Order Processing System Integrated Function Modules Business Flow of the SAP Sales Process SAP Sales Organisation Key Fields In Sales Order Transaction Codes In Sales Order Processing Important Master Record Material Master Record Sales Views In Material Master Customer Master Record Sales Unit of Measure Delivery Plant Pricing Master Record

Sales Document Flow Goods Movement In SD Stock Overview Availability Checks For Customer Order Credit Management In SD Sales Information System Report Sample : List of Sales Orders Change Logging In SD Similar Interface Output Determination Delivery To Customer Customer Invoice Automatic Accounting Posting Appendix A: SAP User Menu Appendix B: Short Cut Keys In SAP Menu


$!
$ 
"
 /
c
 
' This paper will provide you with a step by step guide to the configuration of the Sales Order Processing under the SD modules. #!
'
 IMG Menu ± The Starting Point Start of the SAP Sales and Distribution Configurations The Structure Configuration : Define Sales Organization Where does you maintain the Standard Text? The Structure Configuration : Define Distribution Channel The Structure Configuration : Define Division Where is the Division Used? The Structure Configuration : Define Sales Office The Structure Configuration : Define Sales Group Where are the Sales Org, Dist Chl, Div, Sales Off and Sales Grp Used? Configuring The Link : Sales Organization Assignment Configuring The Link : Distribution Channel Assignment Configuring The Link : Division Assignment Configuring The Link : Sales Area Assignment Configuring The Link : Sales Office to Sales Area Assignment Configuring The Link : Sales Group to Sales Office Assignment Configuring The Link : Sales Org., Dist. Ch. and Plant Assignment Configuring The Link : Sales Area to Credit Control Area Assignment Configuring The Link : Business Area Account Assignment Setup Partner Determination Where will the Partner Fuctions be used? Log of Incomplete Items ± Define Incompleteness Procedures Assign Incompleteness Procedures Define Status Groups Configuring SD : Common Distribution Channels

Where the Common Distriution Channel was used? Configuring SD : Common Division Where the Common Divisions was used? Pricing : Define Condition Table Where are the Pricing Condition Keys used? Pricing : Define Condition Type Pricing : Define Access Sequences Pricing : Define and Assign Pricing Procedures Customer Pricing Procedure - CuPP Where will the Customer Pricing Procedure be used? Document Pricing Procedure Assign Document Pricing Procedures To Order Types Assign document pricing procedures to billing types Define Pricing Procedure Determination Where are the Sales Order Pricing Procedure used? Pricing : Define Pricing By Item Category Activate pricing for item categories Activate cost determination for item categories Where does VPRS determine the price from? Availability Check and Transfer of Requirements Define Checking Group Where are the Availability Checks used? Define Material Block For Other Users Where is Checking Groups Default used? Carry Out Control For Availability Check Define Procedure By Requirements Class Define Procedure For Each Schedule Line Category Checking Rule For Updating Backorders Define Default Settings Delivery Scheduling and Transportation Scheduling Output Control ± Output Determination Maintain Output Determination for Sales Documents Maintain Output Types Maintain Access Sequences Assign Output Types To Partner Functions Maintain Output Determination Procedure Assign Output Determination Procedures Assign sales document items Define Print Parameters Where is Output Type used? Double click on the Output type line item to see the details. Sales Documents ± Sales Document Header Define Sales Document Types Define Number Ranges For Sales Documents Define Order Reasons Where is the Sales Order Reasons used?

Sales Documents ± Sales Document Item Define Item Categories Double click the Item Category to check the settings. Where is the Sales Order Item Category used? Define Item Category Groups Where is the Item Category Groups used? Define Default Values For Material Type Define Item Category Usage Assign Item Categories Define Reasons For Rejection Where is the Reason For Rejection used? Schedule Lines Define Schedule Line Categories Assign Schedule Line Categories Where is the Schedule Line Category used? Sales and Distribution Transaction Code Flow


$!
$ 
"
 /
c
 
' This paper will provide you with a step by step guide to the configuration of the Sales Order Processing under the SD modules. #!
'
 IMG Menu ± The Starting Point Start of the SAP Sales and Distribution Configurations The Structure Configuration : Define Sales Organization Where does you maintain the Standard Text? The Structure Configuration : Define Distribution Channel The Structure Configuration : Define Division Where is the Division Used? The Structure Configuration : Define Sales Office The Structure Configuration : Define Sales Group Where are the Sales Org, Dist Chl, Div, Sales Off and Sales Grp Used? Configuring The Link : Sales Organization Assignment Configuring The Link : Distribution Channel Assignment Configuring The Link : Division Assignment Configuring The Link : Sales Area Assignment Configuring The Link : Sales Office to Sales Area Assignment Configuring The Link : Sales Group to Sales Office Assignment Configuring The Link : Sales Org., Dist. Ch. and Plant Assignment Configuring The Link : Sales Area to Credit Control Area Assignment Configuring The Link : Business Area Account Assignment Setup Partner Determination Where will the Partner Fuctions be used? Log of Incomplete Items ± Define Incompleteness Procedures Assign Incompleteness Procedures Define Status Groups

Configuring SD : Common Distribution Channels Where the Common Distriution Channel was used? Configuring SD : Common Division Where the Common Divisions was used? Pricing : Define Condition Table Where are the Pricing Condition Keys used? Pricing : Define Condition Type Pricing : Define Access Sequences Pricing : Define and Assign Pricing Procedures Customer Pricing Procedure - CuPP Where will the Customer Pricing Procedure be used? Document Pricing Procedure Assign Document Pricing Procedures To Order Types Assign document pricing procedures to billing types Define Pricing Procedure Determination Where are the Sales Order Pricing Procedure used? Pricing : Define Pricing By Item Category Activate pricing for item categories Activate cost determination for item categories Where does VPRS determine the price from? Availability Check and Transfer of Requirements Define Checking Group Where are the Availability Checks used? Define Material Block For Other Users Where is Checking Groups Default used? Carry Out Control For Availability Check Define Procedure By Requirements Class Define Procedure For Each Schedule Line Category Checking Rule For Updating Backorders Define Default Settings Delivery Scheduling and Transportation Scheduling Output Control ± Output Determination Maintain Output Determination for Sales Documents Maintain Output Types Maintain Access Sequences Assign Output Types To Partner Functions Maintain Output Determination Procedure Assign Output Determination Procedures Assign sales document items Define Print Parameters Where is Output Type used? Double click on the Output type line item to see the details. Sales Documents ± Sales Document Header Define Sales Document Types Define Number Ranges For Sales Documents Define Order Reasons

Where is the Sales Order Reasons used? Sales Documents ± Sales Document Item Define Item Categories Double click the Item Category to check the settings. Where is the Sales Order Item Category used? Define Item Category Groups Where is the Item Category Groups used? Define Default Values For Material Type Define Item Category Usage Assign Item Categories Define Reasons For Rejection Where is the Reason For Rejection used? Schedule Lines Define Schedule Line Categories Assign Schedule Line Categories Where is the Schedule Line Category used? Sales and Distribution Transaction Code Flow

 #
("%#"4 Handling tickets is called Issue Tracking system. The errors or bugs forwarded by the end user to the support team are prioritized under three seviority High, Medium and Low. Each and every seviority as got its time limits before that we have to fix the error. The main job of the supporting consultant is to provide assistance on line to the customer or the organisation where SAP is already implemented for which the person should be very strong in the subject and the process which are implemented in SAP at the client side to understand,to analyse,to actuate and to give the right solution in right time.This is the job of the support consultant. The issues or the tickets(problems) which are arised is taken care of on priority basis by the support team consultants. The work process in support projects are given below for your reference. 1. The customer or the end user logs a call through any tool or by mail (RADIX). 2. Each one of the support team is a part of support group. 3. Whenever a customer logs a call he /she has to mention to which work group (by name).

4. Once the calls came to the work group the support consultant or the team need to send an IR (Initial Response) to the user depending upon the priority of the calls. (Top,High,Med,Low,None) 5. Then the error is fixed, debugged by the support consultant or the team. Then after testing properly by generating TR(Transport Request through the basis admin) 6. Then it is informed to the end user/customer/super user about the changes which have moved to the production server by CTS process. These are the process. In summary, what I understand is that if any configuration or customization is required to solve the issue, then the consultant have to work on DEV Client, then the end user will test it in the QA client and after approval the BASIS consultant has to transport it to the PRODUCTION client. An example: Tickets in SD can be considered as the problems which the end user or the employee in the company face while working on R/3. Tickets usually occur during the implementation or after theimplementation of the project. There can be numerous problem which can occur in the production support and a person who is working in the support has to resolve those tickets in the limited duration, every ticket has the particular deadline alert so your responsibility is to finish it before that deadline. To begin with , we should give "TICKET" to you for not knowing it. Here is an eg of a ticket raise: End user is not able to 1. Create Sales order for a customer from a New plant , since shipping point determination is not happened . ( Without Shipping point the document becomes INCOMPLETE and he will not be able to proceed further like DELIVERY, BILLING). He raises a ticket and the priority is set in one of the below: 1. Low 2. Medium 3. High. Now you need to solve this ticket. You would analyze the problem and identify that the SP configuration has to be done for the new plant. You would request a transport for DEV CLIENT to BASIS. You do the change and Request one more Transport to BASIS for QA client. The End user will test the same by creating a sales order for the new plant and approve it.

Finally, you request a transport to move the changes to PRODUCTION. Once the change is deployed in production the TICKET is closed. What I have given is a small example. You would get some real issues with severity HIGH in your day-day support. #$!: 2c  "2 !!"2M

"% (
 


 


 " $$$4 SLA is an abbreviation for "Service Level Agreement". It means to have guaranteed reaction or resolving times for incidents (= trouble tickets). For instance you could have defined the following SLA levels For example: Gold: Reaction time = 30 minutes, resolving time = 4 hours Silver: Reaction time = 4 hours, resolving time = 24 hours SLAs normally are part of a contract between a customer and a service provider. *Or in details description:* SLA are Service Level Agreements to resolve the tickets by the market. SLA means Service Level agreement. It is the service agreement between a Company and a service provider. For example an IT Organization providing support of SAP / other software / hardware has a agreement. This can be for example categorized based on criticality of the incident. High priority incident has to be resolved on 10 hours. Medium priority incident has a 3 days time to resolve etc *-- Anu radha SLA's are nothing but Service level agreements. These are defined in project preparation phase and client would have made an agreement with the company for the level of service. The SLA's are applicable in Production as well as maintanence support projects. For example: if your company follows a ticketing process(a ticket is nothing but an environment contains complete description of the problem which contains Short description, problem, customer contact details, sreen shots of the error etxc.,) and for each ticket there will be a severity for example business critical issues or problems may be treated as high or top

severitie's. In those case your company or your team has to deliver the solution to the customer in agreed time limit or otherwise you might end up missing SLA's. SLA's has two important time specifications 1. IPRT --- initial problem response time --- this is nothing but time taken to respond to the problem. 2. PRT --- Problem response time ----- this is nothing but time taken to solve the issue or problem. Both IPRT and PRT will be different for different severitie's.

" 
$
 4 To speak at macro level that is at projet manager or at senior levels. The Functional Spec (Specification) which is a comprehensive document is created after the (SRS) Software Requirements Document. It provides more details on selected items originally described in the Software Requirements Template. Elsewhre organizations combine these two documents into a single document. The Functional Specification describes the features of the desired functinality.. It describes the product's features as seen by the stake holders,and contains the technical information and the data needed for the design and developement. The Functional Specification defines what the functionality will be of a particulat area that is to be precise a transaction in SAP terminology. The Functional Specification document to create a detailed design document that explains in detail how the software will be designed and developed. The functional specification translates the Software Requirements template into a technical description which a) Ensures that the product feature requirements are correctly understood before moving into the next step, that is detchnical developement process. b) Clearly and unambiguously provides all the information necessary for the technical consultants to develop the objects. At the consultant level the functional spects are preapred by functinal consultants on any functionality for the purpose of getting the same functinality designed by the technical pepole as most of the times the functionalities according to the requirements of the clients are not available on ready made basis.

Let me throw some light on documentation which is prepared before and in a project: 1) Templates 2) Heat Analysis 3) Fit Gap or Gap Analysis 4) Business Process Design 5) Business Process Model 6) Business Change & Impact 7) Configuration Design, which is just 5 % of Total SAP- have different names 8) Future Impact & Change Assessement 9) Functional Design (Module Wise) 10) Risk Assessement 11) Process Metrics and Many More-- Which has impact on Business and its work flow Note * This documents are preapared in Vanilla SAP Standards -- Things differ from one implementation to another, and it always depends on the type of business which is opting for SAP. #$!:"2"


 ' "
"



!


!
4 The difference between Functional consultant and Business consultant are as follows: 1) A funcitonal consultant is able to configure the system unlike business consultant. 2) Functional consultant know more about business process unlike Business consultant. 3) A business consultant will bring business process knowledge and provide it to functional consultant who in turn used this knowledge to configure the system. 4) Functional consultant has more configuration knolwledge then Business consultant. 6((   #"

$!
$$
: - Primarily responsible for Handling tickets and application support to the endusers - When an issue comes diagnose, analyse and solve the issue - Responsible for any enhancements - Writing functional specs and interacting with Abapers to develop any user exits

- Training the end users and preparing end user training material 

6((

"
""
 "

0 Below is one view: A functional consultant evaluates the demands in talking with the customer's representatives, transforms the essence into an abstract and algorithmic business model. Hence, he identifies the use cases and transforms them into logical and technical views. Then the main task starts: customizing the respective business area and making sure the system reacts in the manner according to the constraints of the requested use case. The consultant documents the settings and prepares proper guidelines that allow other consultants to do further changes or repairs with due efforts. The consultant takes care that proper training is given to the users and that the system is usable, performing appropriately and the business flow is complete and correct. During go live he assists the technical staff by testing the behaviour of the system. After go live he guarantees that the procedures remain usable and consistent in real live situation and proposes enhancements. The main duty of a consultant is to transfer external know-how to the client. It is not manpower that counts but intelligence, understanding of processes, a feeling for defects and general a common sense. 
'#%$

 When you talk about the role of a Functional consultant in an end to end implementation, I think it won't be possible for me or anybody to define everything but I will try to summarize it: 1. Functional consultant is expected to generate knowledge about the current business process, design current business flows, study current business processes and its complication, in all we can say getting through with current business setup. Flow diagrams and DFD are prepared, most of the time in Vision format, all this forms the part of AS IS document.

2. Everything configured has to be documented as per their categories in the form of predefined templates, these have to be then approved by the team leads or who ever the consultant is reporting to. 3. Mapping and GAP analysis is done for each module, I have seen people defining integration after mapping, gap analysis and configuration is done, but as per my experience in implementation, it is a simultaneous process. 4. Before starting configuring future business processes in SAP, the DFD/ERD are prepared, this documentation is called TO BE, which can be also siad as the result of mapping and gap analysis. 5. Sometimes Functional consultants are also expected to prepare test scripts for testing the configured scenarios. 6. End user manual and user training is also expected from F.Consultants. The project normally starts off with a Kick off meeting in which the team size, team members, reporting system, responsibilities, duties, methodlogy, dates and schedules, working hours which have been predicided are formally defined. ASAP, it won't be possible for me to explain it here, but all I can tell you about it is that it is SAP standard implementation methodology, which SAP prescribes but is not mandatory for any company to follow, such as IBM follow some blue Methodlogy, some companies follow typical SDLC steps, ASAP stands for Accerlated SAP, you can find all the steps on SAP site, through google, reading it from there won't give you a great knowledge about ASAP but will obviously get you to know the definitions of various term.


 '%#
 @0""

/'#
"
$

"
$M
4 *0"B
%
#
4 Testing : the core team members along with endusers will test whether the postings done in SAP is resulting as per the requirements of the organisation. They will test whether the output documents such as purchase order, invoice document are printed in the required format and showing the correct data. Unit testing is refer to the module which are going to implement. SD, MM, FICO etc. there will be test script based on that testing will be performed.

Integration testing will be cross the modules. MM-SD-FICO for example. Integration testing is also called SIT ( System integration testing) Testing mathologies and types: there are 6 types of testings: 1. Unit Testing 2. System Testing 3. System Integration security Testing 4. Performance Testing 5. User Acceptance testing 6. Regression Testing Unit testing is done in bit and pieces. Like e.g. in SD standard order cycle; we do have 1-create order, then 2-delivery, then 3-transfer order, then 4-PGI and then 5-Invoice. So we will be testing 1,2,3,4 and 5 seperately alone one by one using test cases and test data. We will not be looking and checking/testing any integration between order and delivery; delivery and TO; TO and PGI and then invoice. Whrereas System testing you will be testing the full cycle with it's integration, and you will be testing using test cases which give a full cyclic test from order to invoice. Security testing you will be testing different roles and functionalities and will check and signoff. Performance testing is refered to as how much time / second will take to perform some actions, like e.g. PGI. If BPP defination says 5 seconds for PGI then it should be 5 and not 6 second. Usually it is done using software. Regression testing is reffered to a test which verfies that some new configuration doesnot adversly impact existing functionality. This will be done on each phase of testing. User Acceptance Testing: Refers to Customer testing. The UAT will be performed through the execution of predefined business scenarios, which combine various business processes. The user test model is comprised of a sub-set of system integration test cases. We use different software during testing. Most commonly use are Test Director: which is used to record requirement, preparing test plan and then recording the progress. We will be incorporating defects that are coming during these testings using different test cases.

Mercury Load Runner: is used for performance testing. This is an automatic tool. "
"


: (#
"B#
 (B#
 (%
#
 (A
#
 ( 
#
4 Technical Unit Testing= Test of some technical development such as a user exit, custom program, or interface. the test usually consists of a test data set that is processed according to the new program. A successful test only proves the developed code works and that it performed the process as as designed. Functional Unit Testing= Test of configuration, system settings or a custom development (it may follow the technical unit testing) These usually use actual data or data that is masked but essentially the same as a real data set. A successful test shows that the development or configuration works as designed and the data is accurate as a result. IntegrationTesting= Testing a process, development or configuration within the context of any other functions that the process, development or functionality will touch or integrate . The test should examine all data involved across all modules and any data indirectly affected. A successful test indicates that the processes work as designed and integrate with other functions without causing any problems in any integrated areas. Volume Testing= testing a full data set that is either actual or masked to insure that the entire volume does cause system problems such as network transmission problems, system resources issues, or any systemic problem, A successful test indicates that the processes will not slow or crash the system due to a full data set being utilized. Parallel Testing= Testing the new system or processes with a complete data set while running the same processes in the legacy system. A successful test will show identical results when both the legacy system and new system results are compared. I would also note that when a new implementation is being done you will want to conduct at least one cut over test from the old system to the new and you should probably do several. " 
"




4

1. Individual Testing ( Individually which we've created) 2. Regressive Testing ( Entire Process) 3. Integration Testing ( Along with other integrated modules) The 3 types of testing is as follows:1. Unit testing (where an individual process relevant to a SD or MM etc is tested) 2. Integration testing (where a process is tested that cuts across all areas of SAP). 3. Stress testing (where lots of transactions are run to see if the system can handle the data) #$!:#

 2 
!

""
/


!


'?
4 SAP consultant role is to build the system, changes & modification/updation in currently installed SAP system for the end users. SAP End user only use the SAP system just to fetch some info, or to create new thing. So a end user is just using the final product which it is meant for and consultnat design the product/updation and modification. The roles and responsibilities of end users is working in easy access menu they will not have authorizations of using img settings if they get doubt they will send query to the implemented company and just entering day to day transactions. 

$!
B
: Using the software at the end or after the implementation is an End User. In sap HR , we do come across entire Org Management creation by an end user after the Personnel strucutre is created. OM objects like creation of Org Unit means functional area or dpt , creation Job and Position and its occupancy is with in the limits of an enduser. Initiallly the OM is created by sap consultant . In course of time a new department has appeared in the company of the client .. this has to be created by the enduser rather than depending up on the implementor... similarly new job and position..like this small things are always done by the enduser. The entire work of OM is purely depends upon the enduser.

After from this running periodical payroll and Ensuring of the Time schedules ( Work Schedules) of each employee is done from sap easy access by an enduser and the show run of payroll everymonth is by the enduser only. Like this lot of roles are there for an end user. Whatever the problems come across during the enduser utilisation of sap ...that will reach as ticket to the support team #$!: 2.2" 
2
" 3$"
"
M!
$!
./
? c 
0 One would need user id and password to access SAP be it a developer, consultant, administrator, or end user. End user is the one who performs transactions in SAP after it goes live. Such as posting an invoice, goods receipt, creating purchase orders, sales orders etc. Power Users are users with advanced knowledge in certain applications and with special permissions or roles. They work in the specialist departments in the company and are available to other users as contact persons. /"
 %$

 M
2""
 
'
#
 
!

?'4 The main responsibility of the core team member will to impart knowledge about the companies processes to the SAP Consultants. The consultants will be providing the core team members with templets, that will describe the format of the AS-IS documentation wherein the core team members will write the different processes of the company into these documents and submit it to the SAP Consultants. The SAP consultants will then start mapping this into the system and provide the best possible solution that can be incorporated using the TO-BE documents. The main aim is to map the companies processes into the system. The SAP consultants will then train the core team members for how to use the SAP system.

" 
 B
 It is the same for every other modules although here I reference it mainly for SAP HR.

1) You should understand which targeted group for the end-user training is for. Do they have any computer background or not. 2) In what way they are going to make use of the manuals supplied to them during the course of training. Let us focus on how to prepare manuals: In the client side , End Users are not permanent. If they get any better job outside they will resign and go out. Even if you train them well, again the end-user team disappears after some time. That is why implementing company( Client ) expects SAP Consultants to prepare documents which are self explanatory (even to a layman in SAP) and study themselves and use the sap easy access very comfortably. Hence we should prepare a document which explains the following things comfortably: A) All the buttons and Screens we have in sap and its importance for an end-user. B) All the transaction codes used by end user. C) The STEP by STEP usage methodology with screen shots and explanatory foot notes for each Transaction code. D) Prepare a book a table and columns which should have the following information: - Sl.NO. - Transaction Code - Navigation path - Use of the Code - Expected Result - Achieved Result - Remarks/Any Comment E) Highlight the common troubles during the usage of SAP by an end- user and give the solutions (ready to use) These problems you can come across while giving the in house training for the endusers. You just place them at one place and publish it for their usage in future for any of their new joinees as an end-user. F) Every consultant is aware that the entire Organsiational Management is with end user only. Means consultant should train the end user in entire OM.

G) We should inform the importance of info types and usage for our purposes at expert mode, PA30, PA40 etc., H) Each field in the international infotypes should be explained very clearly and ensure that they are comfortable with the fields of infotypes which have been configured for their company. For example : info type 0001 Org Assignment insists about the three structures of the HR. We should explain each sub field like Emp Group, Emp Sub Group, Personnel Area and Sub Area and its importance and relevance to their company so as to understand while processing them from the end- user point of view . When an employee is hired into the company , now the end-user in a position to understand which employee group and subgroup, Personnel Area And Sub Area etc., should allotted.. Like this whatever comes across in SAP Easy Access should be insisted through the training of end users. I) Demo, exercises and solutions should be provided in the manuals. J) Glossary of terms and expansion of Acronyms, Abbreviations should be given. Like this each consultant should focus on end user training and prepare the documents. 6((
"

#"
$
%# "
"

3

 This is not a scientific survey, but merely the opinions of a few agents that we asked. If you have a highly valued skill that isn't on here, don't worry, this is not definitive, but merely the opinions of a few agents. I'm sure if we'd polled others the list might have been slightly different.  "
B$ We polled a number of agents and other sources of information and came up with the following skills that are likely to be on the up over the next few years. Anyone with these skills is likely to be employed, at good rates, even taking into account offshore outsourcing and Fast Track Visa Workers. 1. J2EE 2. .Net 3. C# 4. Project Management

5. Oracle 8 and 9i 6. SAP 7. Business Analysis 8. VB.net 9. NT Novell 10. Java .
  The top three are definitely becoming very hot skills. It's good to see Project Management up there. It is a much underrated skill. Business Analysts are also less immune to offshore outsourcing, as they have to remain reasonably close to the business users.  

 
"
 0 Siebel also gained an honourable mention. Oracle continues to be very strong, and is also expected to gain even more market share in the coming years. !

 Other skills that also received honourable mention for the future are some of those from before the downturn such as:SQL Unix C++ VB Access ASP In fact SQL, Unix and C++ are still the most sought after skills currently, and anyone who has them should stand in good stead. Those where you might find it a bit of a struggle in the next few years are the skills from before the previous downturn like Cobol, CICS, DB2 etc. There is still quite a lively market for PL/I though.

As I said at the start, this is not a definitive list, but we thought it would be worthwhile to pass on what agents believe to be the skills that they think they will be looking for more and more in the next few years.

 

>


  

>

 The system Requirements are : General Requirements Operating System: Windows 2000 (Service Pack2 or higher); Windows XP (Home or Professional); Windows NT Linux Internet Explorer 5.01 or higher At least 192 MB RAM (recommended to have 256 MB of RAM) At least 512 MB paging file At least 3.2 GB disk space (recommended to have 6 GB hard disk drive space) (120 MB DB software, 2.9 GB SAP data, 100 MB SAP GUI + temporary free space for the installation) The file C:\WINNT\system32\drivers\etc\services (Windows 2000) or C:\Windows\system\32\drivers\etc\services (Windows XP) must not include an entry for port 3600. A possible entry can be excluded by using the symbol '#'. No SAPDB must be installed on your PC. The hostname of the PC must not be longer than 13 characters. The Network must be configured for installation and the MS Loopback Adapter must be configured when you start the system without a network connection! Special Requirements for Installations on Windows XP In the file C:\Windows\system\32\drivers\etc\hosts the current IP address and the host name must be defined as Open the network connectivity definition with start->control panel->network connections for defining the network connection. Select ->extended-> allow other users in network. Activate new configurations. Select remote desktop within extended configuration menu. *********

What is MiniSAP? 
 4 In order to get the free Mini SAP, you need to buy the following book where in you will get two CD's of SAP WAS (Web Application Server) which can be installed in your system and practice ABAP programming etc... ******* You can get your MiniSAP with the book :  c!M
:    $$ by Horst Keller, Sascha Kruger. SAP Press. ISBN 0-201-75080-5. It comes with 2 cds (Mini Basis SAP kernel + database). It also includes the SQL server. or  c!M




 H. Keller, J. Jacobitz The first complete language reference book for ABAP! This book represents the first complete and systematic language reference book for ABAP Objects. Based on ABAP Objects, this 1000+ page book describes all concepts of modern ABAP up to Release 7.0 (including a "sneak preview" of Release 7.10). Brand new topics found in the new edition include SAP NetWeaver Application Server ABAP, Regular Expressions, Shared Objects, class-based exception handling, assertions, Web Dynpro for ABAP, Object Services, dynamic programming, interface technologies (RFC, ICF, XML), and test tools, among others. Procedural techniques are also covered where necessary. Highlights: ˜Y ˜Y ˜Y ˜Y ˜Y ˜Y ˜Y ˜Y ˜Y

SAP NetWeaver Application Server ABAP Development basics: ABAP Workbench, Object Navigator, Class Builder, etc. Basic elements of ABAP Objects Classic modularisation and program execution Avoiding erros and error handling GUI programming: dynpros, lists, selection screens, controls and Web Dynpro Persistent data: DB access, Object Services, file interface, data clusters Dynamic programming: field symbols, RTTS, dynamic tokens and procedure calls Data und communication interfaces: RFC, ICF, web services, XML

The book also includes two CDs carrying a fully operational SAP Basis System, and containing all the example programs from the book. ************** Alternatively, if you are a customer of SAP and have an OSS user-id, then you can also buy the Minisap software directly from the Sap service market. https://www010.sap-ag.de/knowledgecat Search for "MiniSAP Basis 4.6D November 2000 (English)" (Item nbr. : 50043446). Minisap contains only SAP BASIS where you can do your ABAP. It will costs you *GB c.

"%B
$
 

 3$"
$
$

0 User parameter: You can fill fields on screens with default values from SAP memory using parameter IDs. For example, a user only has authorization for company code 0001. By entering the value '0001' in field COCD in the Parameter register in this user¶s master record (SU01), the system automatically fills the field Company code with the value µ001¶ on all screens he or she calls. If this company code is not predetermined using a parameter ID in the user master record, the system automatically adopts the first value entered by the user at the beginning of the transaction for the rest of the current terminal session. However, this value has to be re-entered the next time the user logs on to the system Fields on screens are only ever automatically filled with the value saved under the parameter ID of a data element if the Set Parameter/Get Parameter attributes for the corresponding fields have been explicitly set in the Screen Painter. Choose Tools -> Administration, then User maintenance -> Users. Enter the IDs you want in the Parameter register during user maintenance 



$

2""

B=@4 You can do in SE80, choose Other Objects, Enter name and Create. If you want create paramenter id 'TEST' means:

STEP 1: First add value 'TEST' in TPARA Table. STEP 2 : Assign value to paremeter id DATA : LV_TEST TYPE CHAR10. LV_TEST = 'TEST'. SET PARAMETER ID 'TEST' FIELD LV_TEST. To create a Parameter Id for a Data Element. In se11 --> Data element name --> Futher Charactersitics --> Parameter Id --> Type name example ZPARA --> Dbl click in it and create. "
"
B
$

?Ac4 ""
"4 "

4 Parameter IDs are used to ease the daily activities of a user. For example: If the user is responsible with one Purchasing grp/Pur Org/Plant then they adds WERKS/EKGRP parameter here, to have this Plant/Pur Group id filled when they calls the related transaction. Parameter IDs are usually only used to memorize certain user-specific settings. They can be included in the T code SU3 in the parameter tab. EFB - This parameter id will define certain Purchasing authorizations For one or more users. Here you can display certain user can display the conditions. EVO - You assign default values that you have maintained in the Customizing to a particualt user by entering the key of the default value in the user master record under the parameter ID "EVO".


%$



Implementing a package can be a traumatic affair for both the customer and the vendor. Get it wrong and the vendor may get paid late or have to resort to lawyers to get paid and tarnish their reputation. For the company the new package may not work the way they expected, be late or cost a more than budgeted for and take management will take their eye off running their business.

Recently a client asked me what I would consider to be the five most important things one should consider before embarking on an implementation. This isn't a simple question, although there are many factors to think about after some consideration for me the top five are way ahead of the others. My top five factors to consider would be: 1. Set up a Project Board, 2. Secure the resources, 3. Complete the GAP Analysis, 4. Have detailed Cut Over Plans, 5. Train the users. Taking each one in turn: #"
 M
 The correct set up and operation of the Project Board in my view is major factor in the success failure of the project. The Project Board will consist of the stakeholders, key users and the vendor. The Project Board is part of the governance of the project. The Project Board will meet regularly to ensure that the project plans are created and being executed as planned, moves from stage to stage with all the deliverables being signed off is resourced properly. #"


 Three types of resources are absolutely necessary -- end users, change team and technicians. Early involvement by the end users is absolutely necessary, as they will be the ones living with the system for hopefully many years to come. They will want to feel involved in its implementation. Buy in from the end users of the system is absolutely essential if the system is to have a long and stable life in any organisation. The Change Team will identify the gaps between the package and the business requirements, re-engineer some of the businesses process to cope with the package, train the users to ensure implementations is smooth as possible into the business. The Technical Team will prepare the systems environment for the package, apply any software fixes from the vendor, implement the software in the best way possible for the organisation set up and tune the software for the particular technical environment.

  A through gap analysis will identify the gaps between how the business operates ad 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 actioned, GAP must be closed and customised software can be developed close the gap, GAP must be closed but software cannot be written therefore a workaround is required, GAP does not need to be closed. In simple terms: Gap means small cracks. In SAP world. In information technology, 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 blue print stage. 'c
  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. #B
 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. 3$'
  
<

 %0 Cutover Activities or Master Data Uploading Strategies Depending upon the when we are going live. As per that, you have to give the information to your core team. If you goling live at the middle you have to upload the all P&L Account items and B/S Items. If you going live at the financial year start, you have to only Upload the B/S Items. Activities for Golive: 1. G/L Master Upload Thru BDC or LSMW (TC-Fs00 and extended one co code to another company code Fs01) 2. Vendor Master Upload Thru BDC Or LSMW (Will be Taken Care By MM) 3. Customer Master Upload Thru BDC or LSMW (Will be Taken Care By SD) 4. Asset Master Upload(Thru As90) 5. Cost Element Master Upload 6. Cost Center Master Upload 7. Profit Center Master Upload 8. G/L Balances Thru F-02 10. Vendor Balances thru F-43 11. Customer Balances thru F-22

12. Customer Advances thru f-29 13. Vendor Advances thryu F-48 Before uploading Vendor Balances you have to take care of WHT(TDS) Information. 6(( /


!


"
B
3? $0 Both are quiet a different and has a small relation. User exits are standard gate ways provided by SAP to exit the standard code and we can write our own code with the help of ABAP workbench. its not new functionality which we are trying to build in sap but its slight enhancement within the same code. Gap analysis is start point of Realization and once blue print is finished we have to find the realization of sap system for client requirment and there will be certain gaps when compared to system fit. Those gaps can be closed either by re-engineering of business process to fit with SAP or we have to use USER exits in case of small deviations or complete enhancements with the help of ABAP to fit with the SAP system. 6((A0" "  M
4 As per dictionary, Rollout means ³Inauguration or initial exhibition of a new product´. As per SAP specific definition, rollout is the strategy for international SAP implementation. Rollout strategy normally include the following - Whether to implement SAP simultaneously (also known as big-bang) in all the countries, or - Go live in sequence of phased manner - Or to go for the combination of both (phased manner implementation for some of the countries and big-bang for others). Rollout strategy is the most important decision that a client can make during SAP implementation. Normally, steering committee decides the rollout strategy.

'"
  
>$

,%=@2


. 

  
   &  
   ) 
. 
 
 #a
+$= 
 
    Ä

 



. 

      
 


   
 a
Ä

 
)  )

  
 
 
 ) a
+ a
 a


  ) )      
&
 2
  
&
 a
*/

        
 

. 
  
Ä

  
&
  
0 


  
  a 

) 

&
   

' 
: You could check to see if you could read the partner from the memory within the FM. However you could potentially accomplish the same using the following steps without programming. You could use the View profile settings in configuration and transaction variant functionality (/=) to accomplish this. -> As a first step Make sure to add the Partner view as a sub screen to the very first screen using View profile settings for the equipment category in  c. (This will force the partner field to be available directly on the initial screen when a piece of equipment is created). ---> Now create a Transaction variant for the standard transaction %=@ and here select the sold to partner custom type and leave the value field blank. - Now on the configuration for the Transaction set the Partner type to be imported with value "SP" and mark the content field to be mandatory. -- Leave all other settings to default and save and exit. ---> Now set this Transaction variant as a standard variant for this transaction. This should do the trick. The user will be forced to enter the sold to party on the screen. - However for change transaction (%=*) the user can delete this partner type without any issues.

3$c "%


B
: „ a 1
   
      
 

  
   
   
  
  It includes : 1. Pricing conditions that you can store for relevant Purchasing Organization or Plant. 2. Reminders 3. Number of last Purchase Order 4. Planned Delivery Time ( Lead time required by the vendor to deliver the material ) 5. Tolerance Limits for Over Deliveries & Under deliveries 6. Availability Period during which the Vendor can supply the material. '
: We can create info record by: +*    If you create info record manually and then create PO manually, the price will be picked from the info record. If info record does not exists and you create PO manually with info record update indicator set, the info record will be created automatically without price updation, and the last PO number will be updated. Again if you create a PO for the same material the Price will be picked from the last PO which is updated in info record. For creation auto PO , you have to create info record manually first and then maintain the source list. Then only you will be able to create auto PO. You cannot create auto PO without info record, : If info update indicator is ticked in PO, it will update the order price history in inforecord ( Env.tab) & not the price in condition record. It will update 'Order price history'----path is 'environment' and 'order price history' in tcode ME13

: Is there a way where you can get to know who create a Purchase Info record? In transaction ME13, please go to Extras -> Administrative Data. You will see who created on what date. 
: What ME18 (send purchase info record ) does?

  
    %   )    ) 
( )   Networks and network activities are more suitable for planning resources and scheduling than WBS's and WBS elements. For Networks, Scheduling calculates the earliest and latest dates for the execution of the activities, and the capacity requirements and floats "
$

: 1. Forward scheduling: scheduling starting from the start date. 2. Backward scheduling: scheduling starting from the finish date. 3. Scheduling to current date: scheduling starting from the current date. 4. "Today" scheduling: a scheduling type for rescheduling an order if the start date is in the past. )



"
$

'50 Check img path: SPRO -> Project System -> Dates -> Scheduling -> Specify parameters for Network Scheduling Secondly, WBS can be assigned as Account Assignment in Sales order. Check Account assignment tab of sales order. #"!$

2

When procuring services externally (outsourcing), you can create services or externally-processed activities. Example: You commission a freelance engineer to design and build a machine. When you create such an activity, a purchase requisition is also created, and processed further in Purchasing. You can access data from Purchasing for external processing (a purchasing info record, for example, which contains prices and delivery times for external processing). Externally-processed activities give rise to planned costs equivalent to the prices from the purchasing info record or the price in the activity. The valuation variant for the network costing variant determines which price is used for the valuation. When the purchase requisition is activated and converted to a purchase order, the activity is also shown as a purchase requisition commitment or purchase order commitment. The account assignment category in the purchase order determines whether the goods/invoice receipt is valued - that is, whether it gives rise to actual costs. If the goods receipt is valuated, actual costs are posted to the activity and the commitment is reduced by the amount of the purchase order. This means that the invoice receipt may correct the actual costs. Service activities are maintained for the purchase of services. Creating such an activity establishes the link to MM Services (MM-SRV). Unlike externally-processed activities, service activities contain a service specification containing planned activities and value limits for unplanned activities. This service specification is copied to the purchase order where Purchasing can then modify it. Service activities also give rise to planned costs or purchase requisition/order commitments. Instead of goods receipts, services are later entered and accepted.