SAP SD (Sales and Distribution) is one of the significant modules of SAP ERP. All the content and graphics published in this e-book are the property of. SAP ERP. Unit Overview. ▫ SD Organizational Structure. ▫ SD Master Data. ▫ SD Processes Smallest org unit for which you can maintain a legal set of books. quollevcomeedart.cf Page: 3 of SAP. SALES AND DISTRIBUTION. COURSE . The purpose of this book is to learn step-by-step general configuration methods for the SD SAP Sales and Distribution module is commonly termed as SD.
|Language:||English, Dutch, French|
|ePub File Size:||25.77 MB|
|PDF File Size:||16.71 MB|
|Distribution:||Free* [*Sign up for free]|
Sales and Distribution in SAP ERP (which, in this book, we'll refer to as group for this book includes members of the end-user SD community who are executing PDF, recover, Invoice list, type, Invoice Verification, Here one can read and download complete PDF Book, PDF guide on SAP SD ( Sales and Distribution) Configuration which explains Item. What is SAP SD means, full form or SD stands for (Sales and Distribution), a comprehensive sales management solution impacting a broad range of verticals, .
To control the amount of time required to read time infotypes, MODE N is assigned to the infotypes in the declaration. If you want to evaluate absence data according to organizational units, it is a good idea to use an internal table to group together the information from different database tables PA and PA AT NEW bukrs. IF pnp-sw-found EQ 0.
IF dtype-dar IN datetype. IF sy-subrc NE 0.
CLEAR tt. Reporting in HR Organizational Management is based on the idea of representing each element within an organization as a separate object with its own characteristics.
These objects are created and maintained separately. Relationships are used to link one to the other see graphic. This gives rise to a network that is flexible enough to facilitate personnel planning, projections, and evaluations. The cost center is an external object type because it is not maintained in Organizational Management.
Customizing enables you to enhance the existing data model by defining new object types, for example, and establishing new relationships between the various object types. Each standard object type consists of two letters, whereas the customer namespace is 00 to This data model object types and relationships also constitutes the basis of other applications within Personnel Planning, such as Training and Event Management business event hierarchies and Personnel Development for example, qualification catalog.
Reporting in HR "Job" is used as a general classification, such as secretary or head of department. More than one employee can have the same job. For example, twenty employees can have the job of secretary. A position is the assignment of an individual employee in your enterprise, for example, sales manager, secretary in the marketing department. You form the structure of your enterprise by creating positions and linking them to each other. Active means that an object or infotype record can be used at this time.
Planned means that an object or infotype record has been proposed but is not yet active, which means it cannot be used. Submitted means that an object or infotype record is currently being checked by a person or group of persons before it is approved or rejected. You can create objects with the status "planned" or "active". Reporting in HR An evaluation path describes a set of relationships between objects in a hierarchical structure. Evaluation path O-S-P, for example, describes the set of relationships found between organizational units, positions, and persons.
Evaluation paths are used to select objects for structural evaluations. You choose an evaluation path, and the system evaluates the structure along the evaluation path. The report only evaluates objects that it finds in the specified evaluation path. Every standard report has a defined standard evaluation path.
They are predetermined in the system and must not be changed. The standard selection screen enables you to choose evaluation paths. You can also create new evaluation paths to meet the particular requirements of your enterprise. With this macro, you can import the data for an infotype with a repetitive structure. See also Table Infotypes. Parameter 1: Infotype Parameter 2: Reference field Parameter 3: CLEAR stabs.
If the export is successful, the return code is 0. Reporting in HR If data is exported using macros, the data records are not written directly to the database.
Instead, they are written to a main memory buffer. At the end of the program, the buffered records must be saved on a PCLn database.
Reporting in HR The data definitions of a work area are stored in separate programs using a fixed naming convention. Their names follow convention RPCnxyz0, where. In this cluster, the database table PCL1 contains the texts stored for infotypes.
The key structure of the cluster is stored in a field string xyKEY where the personnel number is the first element.
The data objects field strings and tables are named individually per cluster. If a record is read successfully, the return code is 0. If a record is not read successfully, the return code is 4. It is possible to import only a portion of the data objects in a cluster.
These include programs are generated and must not be changed manually. The macros use routines that carry out two tasks: Data buffering 2. Cluster authorization check. Reporting in HR To minimize the number of times that the database is accessed, import and export data is buffered in the main memory.
If a test run is performed, the database is not updated. However, the payroll results of the previous period form the basis of the calculation used to determine the results of the subsequent period. For this reason, a difference arises between the results of a live payroll run and the results of a test run if test runs are performed for several periods.
Using the buffer enables you to access the required results from the previous period.
Sales and Distribution with SAP®
Instead, the buffer directory is checked to determine whether the main memory already contains a record with the same key. If this is not the case, the record is read from PCLn to the buffer, and retrieved from the buffer by the report. If data is read using a buffer, the system checks the cluster authorization. WRITE ptext-line. We are having customized payroll driver programs for most of the countries viz: Reporting in HR With this report, you can display the payroll results for any country.
The indicator behind each name shows whether results exist in the selected period. Results exist Red: No results exist Gray: No authorization for displaying personnel numbers Payroll results are stored as structures and internal tables on the database.
Each payroll result has a status indicator: The schema contains functions that call the subroutines contained in the payroll driver. In many cases, the function is enhanced by rules for specific control of the subroutines. The payroll result generated by the payroll driver is stored in cluster xy of the database table PCL2. The report is used in all country versions and the overview of payroll results is automatically displayed according to the particular country.
A directory entry with the payroll area, forperiod, in-period, status indicator, and the five-digit sequence number is required, together with the personnel number, to construct the key for each payroll result for an employee.
The personnel number whose payroll directory is to be read is transferred to the function module. To determine the correct start date and end date of the for-period, you specify the period by entering the payroll period in the selection screen. You can also use the following function modules: Anonymous evaluations can then be carried out by users without cluster authorizations.
Here, the component NAT contains the substructures for the country-specific results. SKIP 1.
SAP solutions Ebooks Free Download
IF pnp-sw-found NE '1'. S ', 30 'Name', 60 'Company Code'. AT NEW pernr. SKIP 2. Activate Compensation Adjustments. User Exits and BAdIs 1. Default values and checks. This is mainly used for validation of infotype entries when maintaining data through PA40 or PA30 transactions. The following are available for determining these default values: Error messages or exceptions are not provided for in this function exit.
Note the following: Error messages can be returned. You can still change the created infotype record in function exit. Whoever is responsible for the enhancement project must make sure that the field contents are consistent! As soon as the enhancement is active, the function exit will be called up for each infotype.
The following steps are required in order to do this: Reporting in HR Business Add-Ins BAdI Business add-ins are programmer-defined places in source code where software customers industry sectors, partners, customers, and so on can add their own code, without modifying the original object. A user who wants to use a business add-in can create their own during implementation, or use one of the delivered standard solutions.
The interface of a business add-in is forward compatible, thus ensuring that these add-ins and their interface still function after a release upgrade. They do not need to be registered in SSCR. Business add-ins can be created at any level of the system landscape.
In addition, business add-ins can be created and delivered at all software levels. Enhancements created using business add-ins can be implemented either exactly once, or for an infinite number of customers simultaneously.
Business add-ins can also be defined according to a filter for example, an add-in could be implemented according to "country" or other criteria. Customers can then add their own enhancements to the standard system. Interfaces are required to execute a task are combined in one business add-in. Go to Transaction: Reporting in HR By seeing the attributes we can make out that this is a Multiple use BAdI which means there can be more than one active implementation at a time.
Choose the menu Implementation Overview. The following screen will appear. Click on the create button The following popup appears. Reporting in HR Here we are having three methods viz: For Example, let us take a scenario; In Info Type if the employee subgroup is 1A then the payroll area entered should be only Let us how can we implement this using BADI. Reporting in HR The code is as follows: WHEN ''.
Reporting in HR For viewing the parameters which can be accessed inside the method, we can use the Signature button in the application toolbar. Screen with signature option. So far we have identified the BAdI definition created our own implementation and written our own code.
Now the final step is activating the BAdI. As discussed earlier, ours is a multiple use BAdI that means the activation of our implementation will not affect the existing active implementations. If we do not want the existing active implementation, we can deactivate it. If the active implementation is of standard SAP, then we can deactivate it easily, but if we want to activate it again we need the access key.
Now let us see how this is affected in PA30 transaction for Info Type Go to Transaction PA Enter the Personnel Number as Example. Reporting in HR Click on change icon and goto the next screen. Enter the payroll area as W0. Goto SU21 transaction select the authorization class HR Human Resources and it will list all the authorization objects associated with it. The present object is used by the authorization check for PD data. Relationships are special subtypes for infotype Consequently, the relationships for which a user should have access authorization can also be limited in this field.
The possible values are defined in table T77FC. This protection against unauthorized access is extended by the structural authorization check.
Two types of function codes are distinguished in HR management. By marking the processing method Maintenance in table T77FC the function codes are indicated, with which objects may be maintained within the structure; Otherwise, only Display is allowed. The function code has effects in connection with the structural authorization.
Introduction to Sap - SAP SD
In table T77PR, authorization profiles can be indicated which are to have maintenance authorization for the structure. Without this authorization, you can only display structures. Consequently, the overall authorization results from the intersection between basis authorization and structural authorization. Authorization Objects in HR Object: Reporting Fields: In this way, you can carry out a fine-tuned control on reports for infotype authorization.
This can be useful for functional reasons or to improve performance at runtime of the corresponding reports. For this object, specify the report name s and the degree of simplification to be used for the authorization check. Authorization Objects in HR Note: Reporting , however, overrides the HR infotype authorization check for selected reports, with the result that the authorization checks are weakened or completely switched off.
Object HR: Master Data - Extended Check Fields: The object HR: The program switch HR: The main switch settings can be processed using transaction HR: Authorization switch OOAC.
Clusters Fields: Field Details: Project Preparation Phase: User Licenses: This is not one time payment to SAP. Based on number of end users they decide on how many user licenses to be downloadd from SAP. Hard disk. Quality server will be used by consultant and core user. RAM etc. After deciding how many servers to download. Development server will be used by consultant.
Quality Server:. Server room security Temperature requirement C. Out of Server Environment: It is live server where end user will do day to day transaction in SAP.
Popular Manufacturers of servers in the market are HP. Consultant does not have excess to production server. SAP Suggest to go for 3 Servers: Production Server:. User does not have excess to development server. For foreign project 18 months 6. Team of Galaxy Pharma will list out all the core users. Go-Live Date: If its domestic project and all consultants are moving to clients place for implementing SAP. They will pick one core user from each module.
Implementation Partner: Consultant Facilities: If it is foreign project. If it is domestic project all the consultants will go to client place for implementing SAP. The Average project tenure for domestic project is 9 months.
Which is not possible in standard SAP. The team size for implementation of SAP to foreign client or known client is Scope for the project: Technical man days — 30 days After preparing BBP document.
Is there any alternate solution or not? If yes. Estimated efforts. Gap analysis document consist of Clear description of client process. For client business process. Functional man days — 35 days. Customizing request Client Dependent: Workbench request A. After transporting the request from development server to quality server then we do internal testing in quality server.
Functional consultant role in transporting request 1. We need to release the entire request. Transport request is of two types: Workbench request Client In-Dependent: Whatever configurations functional consultant will do.
Customizing request B. Whatever developments technical consultant will do. This document will be given to core users. Configuration document will be used for KT knowledge Transfer purpose. Configuration document: After completion of testing. Functional Specification document FS:. After preparing user manual document. User Manual document: Open Order The order which created but yet not delivered or pending b We do recording and send this recording to ABAPER while doing recording simultaneously prepare excel sheet with the same sequence of recording and send this excel sheet to core user.
Consultant role in cutover activities a We list out what master data and what open transaction data should be uploaded from legacy to SAP Master data consist: After getting UAT sign-off we transport all the requests configurations from quality to production Server.
Legacy means Non-SAP. Core user has to 10 days test all the scenarios. It is the planning for uploading data from legacy to SAP. Uploading of master data and open transactions data from legacy to SAP. After training we will ask core user to test the scenarios and confirm. V Cutover Strategy: Whenever we plan to upload the data from legacy to SAP. Final Preparation Activities: After that core user will give training to 15 days their end User.
Core user will fill all the excel sheet and give it to consultant.
During this strategy we decide when exactly to upload the data from legacy to SAP. As consultant we first go to quality server and do MOCK run testing if everything is fine then we go to production server and upload the data from legacy or excel sheet.
The reason is to avoid data inconsistency. We give training to core user for 15 days. What is the difference between developer user id's and normal user id's? What happens if you get an error while uploading the data? In which server we do cutover activities? How many end users? Whenever a support partner get a new project.
Support is solving the issues raised by the clients who already implemented SAP. Ticket description. Solution description. Escalation in support: Levels of consultant in support: Consultant description Consultant role in weekly meeting in support: Level 3 — work only in change request. If core user is assigning wrong priority to the ticket. Issues resolution document consist of: Ticket Date Issue resolution document will be used for future reference. Every client may not have a ticketing tool.
List out all the issues which are in pending and discuss on each and every issue in Weekly meeting. Core user description. IF The issue is not properly solved or addressed by the consultant then core user will send escalation mail to superior. Login into SAP: Up gradation is upgrading the SAP system from one version to another version. If the client is starting their business in another country then they extend SAP configuration from one company code to another company code.
If the client is introducing new plant into the business then we have to do configuration for that plant in SAP. Double click on SAP logon pad on desk top. Select IDES client name. End user will work in easy access screen. Roll Out Project 1 Company code roll out: If we want to log off from SAP.
At a time maximum we can have 6 sessions. FI consultant is responsible to define company code in SAP. SD consultant is responsible to define sales organisation in SAP. Sales Organisation: Or It is an organizational unit where strategic decisions related to sales will be taken.
Example — Tata group. ZALK the company code can be numeric or alpha numeric or character. Company code is a physical entity.
Group of company or sister concern. What scenarios a client will have multiple company codes? Reliance group. Z A L k In our project we have one company code and the name of company code is Galaxy Pharmaceuticals Address of company: Corporate office. Sales organisation is of 4 digit code. Having operations in multiple countries. Company code is an organizational unit which is responsible for all the external financial transactions which happens in the company.
Or It is organisation unit where we find director sales and VP sales. Branch office. A company code is 4 digit codes. Company code: This field is pre requites to process rebate in an organisation i. SPRO SAP Net weaver General setting maintain calendar public holiday click on change button Pencil ICON go to create floating public holiday year — month — day mention sort criteria IN religious 22 Hindu Short holiday — long holiday Gudipadwa Enter Go Back Click on holiday calendar in holiday calendar we list out all public holidays — in real time HR consultant create calendar click on change go to create calendar ID P1 Galaxy Calender click on assign holiday go to short key and select all IN India holiday assign holiday then select all public holiday save it.
Address text in sales organisation will help to determine the address of the sales organisation to print it in relevant output. The calendar specifies all holidays and working days. Shipping point. We use this only for third party process and individual downloads order process. Define Factory calendar: The rebate scheme if any customer downloads nos. Rebate Proc Active: downloads Organisation: MM consultant is responsible to define downloads organisation. The output can be printout or email or fax.
Sales organisation 2.
Plant and 3. We assign factory calendar for three organizational units 1. It is an organizational unit which is responsible for all downloads happening in the company. After creating the factory calendar we assign the factory calendar to sales organisation. Rebate is a special kind of discount which is a conditional discount and will be valid for specific period of time Example: Specification of products.
Master data will avoid manual mistake. The advantages of Master data: It is the details of the products which we store centrally and use in day to day transactions.
SAP SD (Sales and Distribution)
By using CMIR we assign customer material number with our material number then while creating sales order if user enter customer material number and system automatically determine our material number. No need to enter the details of the customer every time. It is the details of the customer which is stored centrally and used in day to day transaction. Master data is a data which is not changed frequently. We use CMIR if customer is placing order with their own material code.
In this master data we maintain pricing data for all the products. Condition master is nothing but pricing master. Price group field will help to simplify the maintenance of discount condition records. PP customer procedure: The purpose of this field is to maintain discounts. The T-code to maintain exchange rate is T. For cross selling maintain B For Product proposal maintain A Product proposal is automatic determination of item proposal in sales document. Price group: The end user will select the items from the list and copied into sales order which will save the time of end users.
Description and save it. After placing the order what is the chance that the customer will not cancel the order. Grouping of customers who will share the same pricing attributes. Go to the item proposal to customer master and assign the number and save it.
Item Proposal: Switch off rounding: This field will be used for cross selling concept or product proposal concept. If we check this.
If customer is regularly placing order for similar items then instead of entering the items manually into sales document every time. Define Price group: Order probability: Exchange Rate type: Code OC Quantity Decimals h.
The T-code for creating item proposal is T.
Mention the item proposal as PV Maintain sales area enter description mention material and Tgt quantity. Cross selling is selling additional products along with the main product. Customer pricing procedure: This field is one of parameter to determine pricing procedure into sales document. Tax Classification: Customer is liable for payment guarantee procedure. The payment guarantee can be bank guarantee or letter of credit.
Account assignment group: Payment guarantee procedure: Sold to party SP — He is the customer who will place an order to company. Shift to party SH — He is the customer to whom we deliver the goods. Without configuring credit management system is blocking the order for credit. Payer PY — He is the customer who will make the payment..
XD01 Apollo as customer no. Extending the customer from one sales area to another sales area Ex. If the customer is liable for payment guarantee.
XD04 — Tracking the change log in customer master This field controls whether customer is liable for TAX or not. Bill to party BP — He is the customer who will receive the bill Generally Overseas Customers are liable for payment guarantee. Material Code Logic: The purpose of material code logic is it will save the time of end-user to identify two products. The T-code to create material Master are: Material Master The Specifications of the product which is stored centrally and used in day to day transactions.
We give training to core user. The Consultant role in material master Define new entries in the field. In real time End-user will create material master. The Length of material master is 18 characters.
Material master will be further classified into multiple views: Accounting 1 view Valuation class: It is one of the parameter to determine storage location into delivery document.
This field will help to calculate the shelf life of the product. Your account Help. Browse the Book Browse the Book. Business User Guide. Print edition. Creating a sales order? Inquiries and quotations? Outbound deliveries? Find the step-by-step instructions you need for sales, shipping, transportation, and billing with this business user guide to SAP ERP. Master the key sales and distribution functions and tasks.
About the Book About the E-book pages, hardcover, 1. Reference book format 6. Printed black and white on 60 offset paper from sustainable sources. Notch adhesive casebound for durability. Reader-friendly serif font TheAntiquaB 9. One-column layout.Enhancement and Creation of Infotypes 5. However, the payroll results of the previous period form the basis of the calculation used to determine the results of the subsequent period.
Inventory accounting document generates at the time of PGI Post goods issue and accounting entry is. During this strategy we decide when exactly to upload the data from legacy to SAP.
Payer PY — He is the customer who will make the payment.. While creating invoice in background system generates accounting document and the accounting entry is: Z A L k In our project we have one company code and the name of company code is Galaxy Pharmaceuticals Address of company: