SAP SD Configuration

SAP SD configuration: February 2008
http://sdconfiguration.blogspot.com/2008_02_01_archive.html
ERROR
SAP SD configuration
SAP SD configuration, customization , cross-functional integration ,HR & General Interview tips.
Showing newest 37 of 43 posts from February 2008. Show older posts Showing newest 37 of 43 posts from February 2008. Show older posts
ERROR
The requested URL could not be retrieved
Configuration For Credit Management

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. Tips 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 OB38 Check which credit control area is assigned to the company code. Company code: Credit control area: 2. Transaction OVFL Check which credit control area is assigned to the sales area. Sales area:
1 of 43
9/14/2011 1:57 PM
Credit control area: 3. Transaction XD02 or VD02 Check which credit control area is assigned to the payer. Payer: Credit control area: 4. Transaction SE37 Is user exit EXIT_SAPV45K_001 being used? 5. Transaction OBZK For the settings under items 2 - 4, field "All company codes" must be marked in Transaction OB45, 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 OVAK Which settings do exist for the sales document type used? Sales document: Check credit: Credit group: 8. Transaction OVAD Which settings do exist for the delivery type used? Delivery type: Credit group for delivery: Credit group for goods issue: 9. Transaction OB01 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 FD32. 10. Transaction OVA8 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 FD32 Credit master data for the payer of the relevant document. Credit account:
ERROR
While trying to retrieve the URL: http://172.16.1.48 The following error was encountered: Connection Failed The system returned: (111) Connection refused
SAP SD Interview Questions. www.techinterviews.com www.geekinterview.com www.sap-img.com www.allinterview.com
SAP SD Help www.erpgenie.com SAP E book download help.sap.com
2 of 43
9/14/2011 1:57 PM
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 OVA7 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 VOV7. Item type: Active receivable: 14. Transaction V/08, Pricing In the pricing procedure used for pricing, subtotal "A" must be entered in a line for determining the credit value (mark the pricing procedure and doubleclick on "Control"). Usually, the net value plus taxes is used. This way the system is determined to use this subtotal for credit pricing. The credit price is stored in field VBAP-CMPRE and used for update and credit check. You can find the used pricing procedure of the order under "Item -> Condition -> Analysis". Pricing procedure: Line with subtotal = 'A': 15. Transaction OB45 Which update group (field "Update") do you use in the relevant credit control area? The default setting is "12". If you use another update group, check whether this is fine with you. If you open an OSS message, please tell us the alternative update group. Credit control area: Update: 16. Transaction OMO1 Which kind of update did you choose for structure S066? In any case, "Synchronous update (1)" has to be chosen as the kind of update. All other settings will lead to errors.
www.sap-basis-abap.com www.saptechies.com www.sapbrainsonline.com www.sap-img.com
job Loading...
Powered By Blogger
Loading...
SAP implementation Loading...
SAP implementation Video Loading...
About Me
S A P S A L ES A ND DIS TR IBUTIO N
D.P.L Township, Durgapur-2, Dist-Burdwan,(WB) Phone (+91)-0343-2552826 Mobile 9474546803 aniruddha.sapsd@gmail.com View my complete profile
Blog Archive 2008 (73)
Posted by SAP Sales and Distribution at 8:17 PM 0 comments
June (11) Evolution of ERP: ERP Vendors:
SD Variant Configuration
Variant configuration is used where you have a configurable material like computer (made up of components like processor, monitor, keyboard,
Implementing ERP Business Process Re-engineering...
3 of 43
9/14/2011 1:57 PM
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 What What What is is is is characteristic? value? class? configuration profile?
Post Implementation Activities: ERP and Change Management: Technical Architecture Implementation Approaches requirements for implementation of SAP at site. Basis ABAP/4 SMARTFORMS May (4)
- What is dependency and what are the types? - What is a variant table? - And the transaction codes for the above.
The procedure is as follows: .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 .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 the sales order.
for On-line Service System Application Link Enabling Change and Transport System Relationship Matrix March (15) Basic Concept of Global ASAP Global Roadmap Program Management Phase 5: Go Live and Support Phase 4: Final Preparation Phase 3: Realization Phase 2: Business Blueprint Project Preparation Accelerated SAP ii Accelerated SAP Introduction Dunning Process In Credit Management The "Packing Process"
4 of 43
9/14/2011 1:57 PM
with an Example
Basic Process of how Packing Works
Customer hierarchy
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
Issue free goods to selected Customers Sales and Distribution Upload Condition Pricing February (43) Configuration For Credit Management SD Variant Configuration Customer hierarchy TESTING in SAP Availability check Order to Cash Cycle Multi-level Packaging in Delivery Sales Order Management Transactions What is purpose of maintaining common distribution... M/SD: automatic transfer of cancellation billing d... What is the difference between inbound and outboun... What are the Steps for the End-user Training in SA... What is the difference between ERB and ERU account... What r the 5 imp fields to be maintained in a/c de... User-Exits in the In-
5 of 43
9/14/2011 1:57 PM
and Outbound
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
Processing of I... How sales document is structured? FREE GOODS Deleted deliveries Shipping Unit Tables in
Implement the Product Allocation Functionality Configuration Overview; Allocation Specific Usage 1.Allocation Procedure (OV1Z) The product allocation procedure is the parent of the entire allocation process. All materials that are to be included in the allocation scheme are required to have an allocation procedure assigned to it in the material master. In addition, as of release 4.0, it is in the procedure that the method of allocation is defined. The user has the opportunity to set an indicator to identify their choice of two different methods (discrete and cumulative allocation) to evaluate the quantities to be considered for product allocation. 2.Allocation Object (OV2Z) The allocation object is the root level of the allocation process where actual data is entered and planned in LIS. The object allows the user to further break down a procedure into smaller parts for future validation of components comprising a specific material 3.Allocation Hierarchy Mapping (OV3Z) Primarily, this transaction permits the assignment of an allocation procedure to an LIS information structure. Secondly, a character is assigned to the information structure to permit collective planning. Finally, the user can assign a step level to the procedure and information structure to sequence the order in which allocation quantities are checked. This functionality allows the user the opportunity to check product allocation against several product allocation scenarios, before the required quantity is confirmed 4.Define Consumption Periods (OV5Z) The allocation consumption periods functionality is only valid if the allocation method flag has been set (OV1Z). If you have de-selected the method field, this functionality is not available. The consumption window indicates the number of past and future periods to be used in the allocation check. 5.Control Product Allocation (OV4Z) In order for the allocation process to function properly, allocation control records are created primarily to map allocation procedure steps to their corresponding objects so that the allocation data records can be located for validation. Secondly, validity periods must be established to indicate when the allocation control records are active. Finally, the user has the option of establishing a conversion factor per allocation control record to accommodate BOM listings of constrained materials 6.Activate Allocation for Requirement Class (OVZ0) In order to turn on allocation in the standard order processing functionality, the requirements class must have a flag indicating that allocation is relevant.
SD Supplementary Invoice in SD SAP SD Intercompany Sales Processing & Billing SAP SD Customer Groups Picking of Goods The Delivery Process Creating a Sales Document in SAP R/3 Shipping Point What and where types of copy controls we change Avaialbility check 01 (Daily requirement) and 02 (... If we dont give the horizan period in dynamic cred... Consolidation route and delivery routes Display/change data in credit management Line item: Header information is missing Line item: incorrect account information in header... Line item: branch items missing What is meant by transfer of data from
6 of 43
9/14/2011 1:57 PM
legacy code...
7.Activate Allocation for Schedule Line Category (OVZ8) In order to turn on allocation in the standard order processing functionality, the schedule line must have a flag indicating that allocation is relevant 8.Create Planning Hierarchy (MC61) In order to adequately establish allocation quantities, the user must initially determine the level at which the allocation is to take place and the aggregation factor of the allocation quantities. In this step, the levels for the collective allocation search procedure are also identified. 9.Generate Masking Character (OV7Z) Upon completion of the level determination for the planning hierarchy, the collective allocation masking character must be generated to allow aggregation indicators to be established. This transaction simply reads the hierarchy established in the planning table and then generates a collective mask character for each level of the hierarchy 10.Modify Planning Hierarchy (MC62) This step is a repeat of MC61 where the initial hierarchy was established. In order to complete the hierarchical set up, the collective allocation (mask character) hierarchy must now be maintained with the appropriate aggregation factors 11.Allocation Procedure Assignment to Material Master (MM02) At the root level of the allocation process are the materials. Each material that is to be considered in allocation scenario must be mapped to an allocation procedure. In order entry, then, when a material is entered with a valid allocation procedure in the material master, the allocation data is verified prior to confirming the line item ordered 12.List of Suitable Structures (OV9Z) This report is used to identify potential LIS information structures that can be used in the product allocation process. This report simply reads through the data dictionary and selects all the active information structures that contain the field product allocation object (KONOB) as the first field. This data can then be utilized in the mapping transaction (OV3Z) to link the allocation procedure step to an information structure (previous step).
What is the purpose of text determination,a/c dete... Cin /excise invoice in sales and distribution What do u do really in pricing determination, Explain about sales order cycle? what is functional specs? Basic SAP R3 Tables for the SD Module Sales Order Management Transactions What is ERP? 2007 (28) December (28)
TESTING in SAP
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.
7 of 43
9/14/2011 1:57 PM
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. What does the following terms means : - Technical Unit Testing - Functional Unit Testing - IntegrationTesting - Volume Testing - Parallel Testing? Technical Unit Testing= Test of some technical development such as a
8 of 43
9/14/2011 1:57 PM
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. What kind of testings that are carried out in testing server? 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
9 of 43
9/14/2011 1:57 PM
Availability check
1. Availability check is an integral part of the business process that determines if the required delivery quantity can be met on a required delivery date. For this purpose the system takes into account pre-delivery activities such as scheduling for picking or packing times and the time taken to produce or obtain the material. It also performs several background functions such as 2. Backorder processing, rescheduling and ATP quantities. Backorder processing: processing of a sales order that has not been fully confirmed or not confirmed at a certain delivery date. 3. Rescheduling: is a proposal of how confirmed quantities already assigned to a sales order can be reassigned to other sales orders that have a higher priority. 4. Available to promise (ATP): is a process of checking the available quantities of a material. The ATP quantity consists of warehouse stock + planned receipts (incoming stock) planned issues (outgoing stock). to examine stock on hand (CO09) proceed to logistics sales & distribution sales environment availability overview. 5. Replenishment lead time (RLT): is the time taken for the material to become available either internally (in house production) or externally (from a vendor). The most important things to consider during an external procurement are purchasing and MRP2 (procurement) views of MMR where the processing time for purchasing, planned delivery time and goods receipt processing time are taken into account. On the other hand internal procurement is based on in house production time (MRP 2 view) goods receipt processing time or alternatively RLT time, which is found on MRP 3 view. 6. RLT (Replenishment Lead Time) is the time taken for the material to become available. RLT is only used when doing an ATP check (Available To Promise). The value of RLT for a material is specified on material master record. 7. There are three types of availability checks Check on basis of ATP quantities. Check against product allocation. Check against planning.
Configuring Availability check through Checking Groups 1. The checking group + checking rule determine how the availability check is to be performed.
10 of 43
9/14/2011 1:57 PM
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.
11 of 43
9/14/2011 1:57 PM
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.
12 of 43
9/14/2011 1:57 PM
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.
Order to Cash Cycle

A customer orders some items from your company by creating a sales order (Tcodes: VA01, VA02, VA03, Tables: VBAK, VBAP etc). Your company decides to deliver the items ordered by the customer. This is recorded by creating a outbound delivery document (TCodes:VL01N, VL02N, VL03N, Tables: LIKP, LIPS etc). Once the items are available for sending to the customer, you post goods issue which reduces your inventory and puts the delivery in transit. This will create a material document. You will post goods issue using VL02N but the material document created will be stored in tables MKPF, MSEG. You will then create shipment document to actually ship the items. (Tcodes: VT01N, VT02N, VT03N, Tables: VTTK, VTTP etc). You finally create a sales billing document. (TCodes: VF01, VF02, VF03, Tables: VBRK, VBRP etc). This will have a corresponding accounting document created that will be in BKPF, BSEG tables. When customer pays to your invoice, it will directly hit your AR account in FI. You will have to remember that these are not a required sequence. Some times, you may configure your system to create a SD invoice as soon as you create a sales order or you may not create a shipping document at all. This is the position where Functional Consultant would come into picture and study the company's order to cash process and configure the SAP system to do so.
Multi-level Packaging in Delivery

Before creating the packaging material you have to go to: IMG-Logistics Execution-Shipping -Packing.
13 of 43
9/14/2011 1:57 PM
Define packaging material types- it can be anything like boxes crates, etc. in this you have to maintain the output determination procedure, output type, plant determination, packaging material category, generate delivery items, number assignment. you can copy from standard also. Then go to define material group for packaging materials - here you maintain the four digit code and the description. Actually, this group is nothing but similar products which require similar packing products. For Ex. Nokia Phones all types they are basically packed first into a polythene bag. So here nokia phones can become a material group for packaging materials and polythene bag can become the packaging material type which can include different sizes and types of polythene bags. Define Allowed Packaging Materials - Here you assign the shipping group for packaging materials to the packaging material type. This is related to your material master data of the packaging material which you create. Now go to MM01 to create a packaging material. use material type as Packaging material then inside the system will take the item category group as VERP. Then in the Basic Data1 screen you have the material group for packaging material (MGPM). Select the proper one. Now in the Sales:General/ Plant screen you have to maintain data regarding the packaging. you select the MGPM same as the basic data 1 screen, then select the packaging material type, the allowed pkh weight, allowed pkg volume. This is important because if the weight of your finished item is 2 KG and in the allowed pkg weight you enter only 1.5 KG, then while you carry out the packing process in delivery, the system will give you error," packaging weight exceeded." The assignment in the IMG creen for Define allowed packaging materials should be same as u mention in the material master. Then save your material master for packaging material. VA01 create the order, save it. VL01N enter shipping point, go to edit - pack- you will face a screen with 2 parts. In the top part you select your packaging material in which you want to pack your finished item, enter the system will assign a number to that material. Now select the Material in the top part and the finished one in the lower part and click on the Icon Pack. Here one thing has to be taken care of. Suppose if you want to pack only one finished item in one packaging material, then in the lower part of the screen you have a field for partial quantity here you change it to 1. system will prompt quantity changed. now you select the material in the top part and the one in the lower part and click on the PER PART. QTY ICON. In this way the system will pack only one finished item in a
14 of 43
9/14/2011 1:57 PM
single packaging material. Packing is done go back, select the picking and do the PGI. save the delivery and create the invoice.
HANDLING UNITS. (Used for Multi level packing) Basically handling units come into picture when you want to carry out multi level packing. suppose you want to pack Nokia phone first into a polythene bag, then this polythene bag is again packed in to box. like that. then this box will become a handling unit. For this go to : IMG - Logistics General - Handling Unit Management - Basics. First create all your packing materials using MM01 and type as packaging material. Maintain all the assignments in IMG in Logistics General. In basics you do the same thing as you did in the packing in logistics execution. like you create the packaging material type, then MGPM and their assignment. Then go to External Identification - and maintain the number ranges for the handling units that you want and assign the same to your packaging material type. Now that you have done everything, create the order, save it, in VL01N, enter shipping point, go to edit - pack - do the same thing as i have told you in the step no. 6 (above). now after doing select the PACK HUs TAB . NOW IN THIS SCREEN IN THE TOP PART YOU WILL SEE THE ALREADY PACKED MATERIAL. In that same part again select your next packaging material that is BOX. enter the system will assign the number to the BOX. Now select the material which you have just entered and the materials which were already packed in the lower part of the screen and click on the ICON PACK. In the same way again in the top part of the screen you select your next level packaging material and press enter. the system will assign a number to it. now select the material you have just entered and the previously packed material in the lower part of the screen and click on the icon PACK. In this way you can carry out multilevel packing. just take care of the allowed packing weight and the number of units you have to pack in the next packaging material.
Sales Order Management Transactions

GENERAL ORDER MANAGEMENT Reviewing Document Flow VA03
15 of 43
9/14/2011 1:57 PM
Searching for a Customer Sales Order by Serial Number ZV11 Order Inquiry ZV33 SALES ORDER PROCESSING Creating Sales Order VA01 Maintaining a Sales Order VA02 Displaying a Sales Order VA03 Releasing an Order or Delivery from Credit Hold: Non-Flooring VKM1 Releasing an Order or Delivery from Flooring Hold ZKM1 Manually Pre-authorizing Blocked Credit Card Orders Z.14 Display List of RMAs by Customer VA05 Confirm RMA Goods Receipt VL02 Generate list of open return orders for deletion VA05 Display Customer returns eligibility MCSI Removing a Billing Block (Approving Credit/Debit Requests) V.23
Posted by SAP Sales and Distribution at 5:19 AM 0 comments
What is purpose of maintaining common distribution channels and common divisions?

Common Distribution Channel and Common Divison are maintained so that if any master data like customer or material maintained with respect to one distribution channel can be used in other DCh. It prevents the multiplication of master records. Eg: A customer is created for say sales area 1000/20/00 then the same customer can be used in sales area 1000/30/00 if we maintain 20 as common distribution channel. Hence no need for extending the customersthe same for materials also.
M/SD: automatic transfer of cancellation billing document

In a subscription with amortization (delivery subscription or renewal subscription), posting occurs automatically when you cancel a billing procedure using the function Function backdated. In the case of a collective transfer, separate intermediate payment data is created for the individual cancellation billing document, which is not desirable in FI. Subsequent to this note, see Note 794764. Solution The constraint is removed so that a cancellation billing document is no longer posted automatically. The program change is available with the next Support Package. A manual advance correction is attached to this note.
16 of 43
9/14/2011 1:57 PM
What is the difference between inbound and outbound delivery?

Inboundmaterial entered into plant (for stock purpose) planned order 2- purchase order 3- production order outbounddelivered from plant like all types of delivery process(through PGI)
What are the Steps for the End-user Training in SAP-sd module?
1. We will decide who the team members of end users are 2. Arrange one comman place for training 3. In a day with pre planned material and using development system with some hard copies of various transaction codes which will use by end users will distribute to them and ask them to practice 4. It is generally like an in house training which may remains for 2 daisies 5. After the training we will give them hard copies of list of transaction codes with narration which are relevant to their modules like SD related and PM related etc
What is the difference between ERB and ERU account keys?

ERB is the account key used for rebate processing and it is a sales deduction.ERU is the accurual key used in pricing for rebate processing it is used for difference in sales revenues. Or ERB is sales deduction and ERU is the accrual amount. Both amts are same but posted to diff GL a/cs
What r the 5 imp fields to be maintained in a/c determination

Account Determination: Sales View, Sales Organization, Distribution Channel, Chart of Accounts, Account Assignment Group for Customer and Material and Account Keys.
17 of 43
9/14/2011 1:57 PM
User-Exits in the In- and Outbound Processing of IDocs

This document includes a list of user-exits, sorted by message type, which can be used in the in- and outbound processing of the corresponding IDoc. You can download this document from the attachments section below.
How sales document is structured?

Sales Document is structured as three levels 1. Header Level 2. Item Level 3. Schedule line Level
FREE GOODS
Free goods are configured by condition technique and pricing procedure. A small note on this will help you. Maintaining records for inclusive free goods Logistics Sales and distribution Master data Conditions Free goods VBN1 create Specify the free goods discount type NA00 Select the required key combination Material: Specifies the material for which free goods are given. Minimum quantity: Specifies the minimum quantity of the material that has to be ordered in order to get free goods. From: Specifies the quantity from which free goods starts.
18 of 43
9/14/2011 1:57 PM
Unit of measure: Unit of measure of material. Are free goods: Specifies the quantity of free goods given to the customer. Calculation rule: Specifies the rule for calculating the quantity of free goods. Free goods: Specifies whether the records are maintained for inclusive or exclusive free goods. Free goods delivery control: Specifies whether free goods are to be delivered regardless of the main item or in conjunction with the main item. Save the condition record. Maintaining records for exclusive free goods: Logistics Sales and distribution Master data Conditions Free goods VBN1 create Specify the discount type for free goods NA00 Select the required key combination Select the button exclusive. Additional free goods: Equal to "are free goods" in inclusive For: Equal to "From" in inclusive. Free goods: inclusive/exclusive. Additional material free goods: Specify the material which is given as free of charge item. Free goods delivery control: Note: 1. Inclusive free goods take 10 as 9+1. Exclusive free goods take 10 as 10+1. 2 In exclusive free goods if required we can give the same material as free of charge item. 3 *Free goods concept is based on condition technique. SPRO Sales and distribution Basic functions
19 of 43
9/14/2011 1:57 PM
Free goods Condition technique for free goods Maintain condition tables (After defining condition tables you have to place in Access sequence) Maintain Access sequence Maintain condition type. Go to New entries and define the condition type to which assign the access sequence. Maintain Pricing procedure Activate free goods determination. We need to assign the free goods procedure to the combination of sales area, doc pri pro, and cust pri pro. To make the value of free of charge item as '0', in the main pricing procedure, we have to take the condition type R100.
Deleted deliveries
When you delete a document - It gets deleted from document flow also. An easy way of finding it is go into va03 and enter any document which hasn't been deleted. Go in to Environment - Changes. Here, you change the document number that has been deleted. When you click execute button, you will be able to see all the changes and deletions as well.
Shipping Unit Tables in SD

Shipping Unit Tables in SD VEKP - Shipping Unit Item (Content) VEPO - Shipping Unit Header
20 of 43
9/14/2011 1:57 PM
Supplementary Invoice in SD
Have created one proforma invoice & transferred stock to my branch / depot at Delhi. This is my mother invoice with MRP, say, Rs. 100/-. Now the MRP is increased from date: 01.08.2007 with Rs. 107/-. I need to pass on the additional Excise duty for difference amount Rs. 7/-. Is it possible to generate supplementary invoice in SAP SD module? If yes, then how to create it? Please help me how could I resolve the problem. To the best of my knowledge you cannot generate an excise invoice without reference to goods movement. If you want to ensure the customer is debited for the relevant amount, please generate a credit memo and an excise JV to ensure that the relevant accounting entries are passed. However tracking is possible only through text fields.
SAP SD Intercompany Sales Processing & Billing

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 customers 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.
21 of 43
9/14/2011 1:57 PM
SAP SD Customer Groups

SAP's Sales and Distribution module is quite comprehensive and contains various features for analysis. One such feature within SAP SD is the creation of Customer Groups. Simply speaking, customer groups are part of the customer master data in SAP IMG. Customers are assigned to a particular customer group by assigning a two digit alphanumeric key. Such customer group key needs to be assigned to each and every customer master records. The main benefit of customer groups is that it can be used in generating statistics and ceating condition records such as records for pricing. One example which I can give is suppose you create two sets of customer groups, say Customer group A1 for domestic sales and Customer group A2 for international sales. You can choose to give discount to customer group A1 which arecustomers in the domestic market by creating a pricing condition for group A1. Customer groups can be created in SAP SD usign the following menu path: IMG >> Sales & Distribution >> Master Data >> Business Partners >> Customers >> Sales >> Define Customer Groups Alternatively, one can use the transaction code OVS9. One needs to simply define a two digit alphanumeric customer group key. Once defined, the same can be assigned to a customer master record using the transaction code VD02. Such custoomer master key can be made mandatory for all customer master records
Picking of Goods
"Picking" in SAP. Before goods are actually shipped to a customer, it is neccesary to prepare the correct quantity and quality of goods as specified in the sales order. Picking in SAP sales and distribution can be defined as Picking refers to preparing the right quantity and quality of goods for shipping on schedule as required by the customer. Once picking is configured, SAP Sd automatically generates picking lists and picking labels which can be tagged to the relevant goods. SAP can be configured to ensure that picked quantity is confirmed before goods are issued. This can be done using transaction code VSTK. In T-code VSTK, picking confirmations can be set, which ensure that goods picked for delivery are in accordance with picking slips. Picking thus helps in monitoring each item using the picking status. Picking is normally done in
22 of 43
9/14/2011 1:57 PM
SAP SD by a shipping clerk. But, picking can be done in the following three ways in SAP. - SAP SD can be configured to execute picking automatically. - Picking can be scheduled to run at pre-defined intervals. - Picking can be triggered manually by an shipping clerk.
The Delivery Process

SAP SD Sales & Distribution Concepts - The Delivery Process / Delivery Creation Process VL01 VL04 In SAP SD, one can create delivery either individually from a sales document or individually via the menu path or via the delivery due list. I am discussing each of these different types of deliveries in brief below. Creating an Individual Delivery Document - User can use the following menu path: Sales & Distribution >> Shipping >> Delivery >> Create. Otherwise this can be reached directly via Transaction Code VL01. At the time of delivery document creation, SAP SD will ask for shipping point, selection date, and sales document number in case delivery is to be created with reference to a sales order. Creating a Delivery via the Delivery Due List - The following menu path can be used: Sales and Distribution >> Shipping >> Delivery >> Create Collective Processing Transaction Short Path is VL04. Delivery due list can be processed using either the stock transport orders or the sales orders. SAP SD automatically creates deliveries for selected sales orders. Some of the fields which can be selected include Distribution Channel, Division, Sales Office, Forwarding agent, Route, Sold to Party, Ship to Party, Delivery priority, delivery block, and Complete delivery
Creating a Sales Document in SAP R/3

Various modules in SAP are based on the document concept. Every transaction in SAP can be traced back to a unique document number. While creating a sales document in SAP R/3, a user has to enter the following information in SAP: - Document Type i.e. whether it is a quotation, sales order etc. - Customer Details. This contains details such as sold-to-party, customer number etc. - Sales Area. This includes Sales Organization, Sales Channel and Sales Division Once all this information is entered in SAP, price is decided for the
23 of 43
9/14/2011 1:57 PM
sales document depending upon the pricing determination procedure. In SAP, the steps which determine data appearing on the screen for e.g. price while document creation is called a determination procedure in SAP IMG. In SAP, one can choose from around 30 different types of price determination procedures defined. SAP also comes with over 100 standard condition types. Thus, creating a sales document is very easy provided it is done in a step by step manner
Shipping Point
Shipping points in SD represent an independent organizational unit that are linked to a plant. Shipping points show the point of departure or receipt of materials. In SAP, a plant may have many shipping points. However, delivery is created from one shipping point only. The shipping point is the basic requirement for a delivery to happen in SAP SD. No delivery can be made without a shipping point. The shipping point is determined by the system based on the shipping conditions.
What and where types of copy controls we change

Copy Control: is basically meant so that Data is copied from preceding Document to subsequent one. What subsequent Document is required is to some extent determined by Customer Requirements as well as Document Types. e.g. In general case of Standard Order, it will be Copy Control (Order to Delivery) from OR to LF .
Avaialbility check 01 (Daily requirement) and 02 (Individual Requirement) in material master

01 and 02 are the checking group. Availability check is carried out with the help of these checking group and checking rule. Checking group 01 and 02 are maintained on the material master. 01 - Individual requirement -For this system generates transfers the requirement for each order to the MRP .So that MM can either produce or procure. 02- Collective requirement.-In this all the requirements in aday or in a wek are processed at a time. System stores all req and passes on to the MRP in MRP run.In this system performance is high however you can not do the backorder processing whereas in
24 of 43
9/14/2011 1:57 PM
other you can do.

If we dont give the horizan period in dynamic credit check

It will become Static Credit Check. Simple Credit Check means the Risk category of the customer is not considered. In Static and Dynamic, risk category is considered, only difference between them being that Dynamic has a time horizon, meaning that it does not consider open sales orders and open deliveries intended to be delivered beyond this horizon date for calculating the customer's credit exposure.
Consolidation route and delivery routes

consolidation route : consolidation route is defined between the development sytem (consolidated system ) and the quality system (integration system ) Delivery route : Delivery route is the transport route that connects the integration system and the Delivery system ( Production system ) Defining Logon Groups : we can do this though our GUI and allways make sure that saplogon.ini is backed up , that consists of all the logon data Logon Load balancing : It is used to identify the least loaded application server Domain controller : it is the central admin of the system transport domain : it is the place the transport layer and routes can be configured to access this transaction use stms
25 of 43
9/14/2011 1:57 PM
Display/change data in credit management

When you process blocked Sales & Distribution (SD) documents (VKM1), the accounting clerk has only the authorization for displaying (and not for changing) certain FI credit management data (authorization objects F_KNKA_MAN, F_KNKA_KKB). However, the Transaction 'Customer Credit Management Change' (FD32) is always called up via the menu option 'Environment'. Since the accounting clerk only has the authorization for displaying certain data, the corresponding error message is also generated correctly. For the display of data only, you must therefore always use a new mode for calling up the Transaction 'Customer Credit Management Display' (FD33). Solution If an accounting clerk has only the authorization for displaying credit management data (authorization objects F_KNKA_MAN, F_KNKA_KKB), after calling Transaction FD32 the system changes automatically from 'Blocked Sales & Distribution (SD) documents list' to the display Transaction FD33. As a result, a new mode becomes unnecessary. This solution only makes sense if the authorizations in the credit management Transactions (FD32, FD33) were restricted by the mentioned authorization objects. If a user has no authorization for Transaction FD32 the source code changes will not be successful, because the authorization check for a certain transaction (authorization object S_TCODE) is not performed in the called transaction, and therefore no reaction from the called transaction (like automatic calling up of the display transaction) can be expected. We recommend to solve the problem as follows: You should not remove the authorization for Transaction FD32 from users, but restrict the authorizations in Transaction FD32 through usage of the mentioned authorization objects.
Line item: Header information is missing

The system does not display any header information on the line item list for the general ledger, vendors or customers.Data is missing which identify the account in particular, as well as the account number and name. SAP delivers standard layout variants for line item displays (including a header layout).The names of the variants delivered begin with a number. For example, the standard variant '1SAP' is always used for list view if you leave the field 'Display variant' blank on the selection screen.In the header area of the display, the account number and the account name then should be displayed. However, there may be an error in the delivery causing the header layout to be missing for standard variants.
Solution
26 of 43
9/14/2011 1:57 PM
Transfer the files as specified in Note 13719 which you can find in directory /general/R3server/abap/note.0181697 of SAP servers SAPSERV3, SAPSERV4, SAPSERV5 and SAPSERV6 into your system. With this transport, the current standard variants are copied together with the headers for the line item into your system. Bear in mind that a corresponding target client is specified. Otherwise they would have to be imported manually: Call Transactions: FBL1N, FBL3N and FBL5N: 1. Line items display 2. Menu: Settings -> Display variant -> Administration 3. Menu: Environment -> Import layout
Line item: incorrect account information in header

You are in the line item display for vendors or customers. On the selection screen, you have selected field "Vendor items" or "Customer items". In the headers for these items, information is either missing for the account or does not apply. The corresponding vendor or customer account for the vendor or customer is defined in fields LFA1-KUNNR or KNA1-LIFNR. Starting from this account number, the system reads the master data for the incorrect account type. If the vendor and the customer account are identified with the same account number, then the system displays the master data of the vendor in the header for the customer account and vice versa. Otherwise, the fields usually remain blank in the header.
Solution This error is corrected in Release 5.0. You can also implement the attached advance corrections.
Line item: branch items missing

You are using the line item display for customers or vendors with dynamic selections for master data fields (tables KNA1, KNB1 or LFA1, LFB1). The system incorrectly does not display the branch items managed at the head office. The error may also lead to the system incorrectly not displaying the items of the vendor clearing account for the customer the items of the customer clearing account for the vendor This is caused by a program error: the system incorrectly also considers the master record field dynamic selections for the head
27 of 43
9/14/2011 1:57 PM
office as well as for the clearing account. Solution This error is corrected in Release 4.70. Import the Support Package specified in the attachment for your release or implement the attached advance corrections.
What is meant by transfer of data from legacy code

Answer1: It should be legacy data to SAP. What it means is you want to transfer all the customer and materials and all other information from Older (legacy system) to new SAP system. You can do it using many tools, most noticeably MDMs. Answer2: Before installation of SAP, Data maintained by Company is called Legacy Data. At the time of instalation, it is required to transfer Data from Legacy to SAP like Masters (Material/Customer, etc). It can be done in various ways like BDC, LSMW, etc.
What is the purpose of text determination,a/c determination

Answer1: Text determination: For transferring information from material or customer to order/delvery or invoice (and anything inbetween) Account determination: For transferring financial and costing information to proper financial docs Partner determination: For determing who is is legally resposible for A/r, who the goods are going to and whatever else you waana drive through this functionality. Output determination: What kinda output does a sales/delivery /billing document create and who gets it, where?. For example A partner might get an EDI notification for a sales order just confirmed, whereas a financial/leasing company gets the invoice! Answer2: (a) Text Determination: Any Texts in Masterial Master/Material Determination/Order/Delivery , etc is meant to convey messages to the subsequent documents for compliance. e.g. "Give Top Priority" message mentioned in Order is meant for Production Dept. (b) Account Determination:is integration between Finance and SD. The A/P along with Account Keys need to be allocated
28 of 43
9/14/2011 1:57 PM
accordingly with combination of Account Determination Group for Customer and Material if required. (c) Partner Determination:To identify which type of Partner it is so that if required for same Customer different Partner Functions may be required e.g Only One Sold To Party per Customer. More than One Ship to Party/ Bill to Party/ Payer possible. Accordingly different Masters will have to be created. Useful for despatch of Material in casae of Ship to Party, sending Bill in case of Bill to Party and payment followup/Dunning in case of Payer. (d) Output Determination: What type of Output (Fax/Mail, etc) is required, where and in what Format(ABAP Customisation may be required in some cases especially Invoices). (e) Storage Location Determination: depends on Plant, Shipping Point and Storage Conditions
Cin /excise invoice in sales and distribution

excise registers ETC 1. In Indian Taxing procedure, Excise Duty plays a vital role in manufacturing cenarios. 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 Use In this IMG activity, you maintain the data relating to your excise registrations. Activities 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. Activities For each excise registration in your business create a
29 of 43
9/14/2011 1:57 PM
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 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. 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 leviable 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 leviable 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
30 of 43
9/14/2011 1:57 PM
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 Use 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 Use 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.
31 of 43
9/14/2011 1:57 PM
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. Use 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
32 of 43
9/14/2011 1:57 PM
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 Use 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. Activities 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. Dependencies 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 Use 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. Activities 1. Create one excise group for each set of registers that you need to keep. 1. Assign the excise groups to plants. 2. Maintain whether this Excise group is for a depot or not. 3. If you receive only one consignment for an Excise challan then you can leave GR's per EI as blank. If you
33 of 43
9/14/2011 1:57 PM
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. Dependencies 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. Dependencies 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
34 of 43
9/14/2011 1:57 PM
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. Dependencies 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 Groups Use 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. Activities 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
35 of 43
9/14/2011 1:57 PM
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' indicator. 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 Use 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 Use 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 Use In this IMG activity, you define which tax procedure and
36 of 43
9/14/2011 1:57 PM
pricing condition types are used in calculating excise taxes using formula-based excise determination. Activities 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 Use 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. Activities Customizing for Logistics IndiaMake the settings in Customizing Basic Excise Duties Using General, by choosing Taxes on Goods Movements Account Settings Determination.Condition Technique and 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.
37 of 43
9/14/2011 1:57 PM
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 Use When you execute a business transaction involving materials that are subject to excise duty, the system automatically calculates the duty for you. Prerequisites In order for the system to be able to determine which rate of excise duty to apply, you must have maintained all the accessdata on the Excise Rate Maintenance screen, which you can Master Data 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
38 of 43
9/14/2011 1:57 PM
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. Activities 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 indictor 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. Lets 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 Use : 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. Activities: 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 Use 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 Use 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
39 of 43
9/14/2011 1:57 PM
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. Standard settings 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 Use 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. Activities 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 Use 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 subtransaction types, enter the accounts for each subtransaction type as well. Activities 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
40 of 43
9/14/2011 1:57 PM
Excise TT GRPO CR GRPO CR GRPO DR
DC ind Account name CENVAT clearing account RG 23 BED account CENVAT on hld account
Specify G/L Accounts per Excise Transaction Use 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 alltransactions. 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 config step has to be made in Screen Sequences for Material Master. Following document helps you to do this configuration. 1. Logistics General Material Master Configuring the MaterialGo to IMG Define Structure of Data Screen for each 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 Subscreens in the left frame. 4. Go to the last sub screen i.e. 21-15-6 - SAPLMGD10001 and select the same. Click on tab view subscreen and ensure that the subscreen 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.
41 of 43
9/14/2011 1:57 PM
6. Save the setting. 7. Create a Material Master and check whether in Screen Foreign Trade Import, Excise related subscreen appears.
Newer Posts Subscribe to: Posts (Atom)
Home
Older Posts
ERROR
While trying to retrieve the URL: http://172.16.1.48 The following error was encountered: Connection Failed
ERROR
The requested URL could
42 of 43
9/14/2011 1:57 PM
ERROR
While trying to retrieve the URL: http://172.16.1.48
ERROR
While trying to retrieve the URL: http://172.16.1.48 The following error was encountered: Connection Failed
43 of 43
9/14/2011 1:57 PM

SAP SD Configuration

Încărcat de

Informații document

Descriere originală:

Drepturi de autor

Formate disponibile

Partajați acest document

Partajați sau inserați document

Opțiuni de partajare

Vi se pare util acest document?

Este necorespunzător acest conținut?

Drepturi de autor:

Formate disponibile

SAP SD Configuration

Încărcat de

Drepturi de autor:

Formate disponibile

SAP SD configuration: February 2008

Configuration For Credit Management