SDreview

Availaility Check and Requirements

Stategy Group: MRP Group: Requirement type: MRP Type The requirement type referes to the requirement class and its control features. Requirement class: Consists all the control featurs like Relevence for requirement, requirement MRP Type in MRP view in MM. planning strategy and requirement consumption strategy. Checking Group Checking Rule: Sales/Plant data in MM.

:- IMG; PS; Material; Control of Sales related material.

Available to Promise (ATP) : Material available on hand. = Ware house stock + planned inwads stock – Planned goods IssueSap menu; Logistics; Sales and distribution; Sales; Environment; Availability view.

Checking group + Checking rule determines how the availability check is going to be done.e.g. Daily/weekly requirement or individual requirement for sales order.

* Checking group : In MM; MRP3 screen.

* Defining Requirement Type and requirement class Menu path:

IMG; Basic functions; Availability check and transfer of requirements; Transfer of requirements; Define requirement classes.

For costing: Sales and distribution; Basic functions; Account assignment/costing; Maintain requirements classes for costing; Account assignment.

Checking group and rule definition, assignment: OVZ2, OVZ3, OVZ9.

_____________________________________________________________----Back order processing________________________________________________________________

@ Define and assigne; 1. Checking group, Checking rule: Also its in Material Master data.

Define and assign Strategy group, MRP group, / Requirement type, Requirement class…….

ATP

ATP is simply Available to promise...quantity which we can promise to the current object. Object may be a sales order/delivery or production order. Here I would like to give simple steps to understand the availability checking in SAP. I would like to give a general guide lines to availability checkAvailability check is carried out in different transactions like Sales order creation, delivery creation, Purchase order creation, goods issue and also in production order.The point to be noted here is every where the availability check is carried out using two basic elements.


1. Checking rule

2. Checking group

ww let us understand these two important elements.

Checking Rule

Checking rule is transaction based, i.e. In STD SAP system, if you are creating the sales order, then it is A, if delivery then it is B, if you are creating/releasing production order, then it is PP. This is almost fixed. What is the use of this...as a single element it does not have any meaning, but with checking group.

Checking group

Checking group is the one what you assign in material master at plant level, i.e. for different plant and for the same material or for same plant different material there can be a different checking group. This is assigned in material master in MRP3 view, as a signal element it may not have much meaning except that it may be used for checking at which level - group level or individual level and quantities confirmed in the availability check are to be locked or not.

Combination of Checking rule and checking group will define the scope of check

Scope of check -

what is scope of check? here we define what type of stock, which receipt element and issue element has to be taken to decide the quantity to be declared as available for use.

Type of check - There are many types of stocks available in SAP and to be considered/not to be considered in availability check.Safety stock, stock in transfer, Quality inspection stock, blocked stock, restricted stock, w/o subcontract stock. - activate check box if you want to consider the any of the stock

Replenishment lead time - Check without RTL = Replenishment lead time is the time taken to receive the stock once order is placed with vendor. Here you are informing the system whether you want to consider the date in future(after RTL) if the any of the above stock is not available...Don't activate the check box if you want the system to check RTL time so that qty is confirmed after RTL date.

Storage location check - No storage location inspection - Here if you activate the check box, then system will check the stock at plant level instead of storage location level. Hence if you want the system is to check stock at storage location level, then don't activate this check box. The determination of stock is a another loop which depends on storage condition loading group or simply at the storage location maintained in the transaction concerned.


Missing parts processing - Checking period GR - Here we maintain a period so that missing parts MRP controller will be notified if GR is done till the period you mentioned here and the material is considered as a missing parts.

Receipt/issues - Here we informing the system which receipt and which issue elements to be considered for calculating ATP. Let us check one by one in more detail. Depending on the situation the elements can be receipt and/or issue.

Include purchase order - This is a receipt element if the you consider a raw material, i.e. it is confirmed receipt element. It can be a STO PO. Hence system will consider this receipt to calculate the ATP qty.

Include PR - Same as the above, difference is, this may not be a confirmed receipt/issue.

Include dependent requirement - Dependent requirement is the requirement from a confirmed planned order/sub contract PR, created automatically in MRP, hence it is a planned issue. If you activate this check box, system will consider all the dependent requirement which are already planned before giving you the ATP qty.

Include reservations - These are can be the materials reservations(not dependent on any other elements like production order) which are created manually in the system using a movements, hence this can be a issue or receipt depending on which movement type is used to create a reservation.

Include sales requirement /Include deliveries- If you activate this check box, system will consider the sales orders/deliveries which already committed, hence it is a confirmed issue.

Include shipping notification - Shipping notification is the information of arrival of material, hence like PO in a receiving plant and is a confirmed receipt

Include dependent reservation - Dependent reservation is the requirement from a production order/process order/sub contract PO, created automatically during order creation, hence it is a confirmed issue. If you activate this check box, system will consider all the dependent reservations which are already confirmed before giving you the ATP qty. Some more functionality given here is which reservation is to be checked Do not check i.e. system will not consider this as requirement while confirming the ATP qty

Do not check - donot take this requirement.X Include all reservations - include all the reservation from production order(created/released)A Only include withdraw able reservations - Include only reservation from a production order that is released.

Include released order requirement - Specifies whether the system takes requirements resulting from stock transport orders and stock transport requisitions into account during the availability check. It is a confirmed (from STO-PO) or planned requirement (from PR) Do not check - requirements from STO not to be considered as a requirement in supplying plant


Do not check - donot check it as a requirementX Check releases for stock transport orders and requisitions-Check all the requirement from STO-PR, STO-PO in supplying plantA Check releases for stock transport orders only - Check all the requirement from only STO-PR in supplying plant.

Include Planned order -Indicates whether the system takes planned into account during the availability check as a receipt. It can be confirmed or planned issue depending on planned order is firmed or not firmed.

Do not check - don't check any planned order as a receiptX Check all planned orders - take all the planned orders in to accountA Check firmed planned orders only- take only firmed planned orders in to accountB Only check planned orders that are completely confirmed- I have not seen any difference between A and B.

Include Production order - Include production orders as a receipt element for calculation of ATP, which are the status to be considered is given below

Do not take into account - Don't take Production order as a receipt elementX Take all production orders into account - take all the production ordersF Only take released production orders into account - take only the released production orders as receipt.

Include receipt from past and future - When confirming sales order which are the receipt to be considered is discussed above but whether to take future and / or past receipt...option is given below

Include receipts from past and futureA Include receipts from past and future, with messagesB Include future receipts onlyC Include future receipts only, with a message

One short note before we start off the subject: Availability refers to the projections of future material stock availability based on the rules we define. It is not directly related to the actual stock. I have seen people confusing availablity with stock situation in MMBE. These are different things. As we will see, it is seen from CO09 according to the applicable Checking Rule. Also it is not directly related to Material Reservations, though we can see reserved materials in CO09.

What do we need to know?

Dates:-

Order Date - Date on which the sales order is entered. System proposes the current date by default.


Material Availability Date - The date on which the material must be available. On the material availability date, the vendor must start the activities relevant for delivery, such as picking and packing the goods. The material availability date must be sufficiently early enough so that the goods are prepared by the loading date.

Transportation Planning Date - We must arrange transportation by this date, so that the delivery can be sent to the customer. The date from which the organization of goods transport must begin. The transportation planning date must be selected early enough so that the transport is available on the loading date to load the goods.

Loading Date - Picking and packing must be completed by this date so that the goods are ready for loading.

Goods Issue Date - Goods must physically leave the shipping point by this date. The date on which the goods must leave the company to arrive at the customer location in time.

Delivery Date - Customer should receive delivery of the goods by this date. The date on which goods are to arrive at the customer's premises. Example: The delivery date can be the delivery date requested by the customer (desired delivery date) or the date confirmed in the vendor's order acknowledgment or shipping confirmation (confirmed or acknowledged delivery date).

Times:-

Pick/Pack Time - Difference between the material availability date and loading date.

Transportation Lead Time - Number of days required for organizing a shipment for an item to be delivered.

Loading Time - Difference between loading date and goods issue date.

Transit Time - Number of days required for delivering an item from your company to the customer via a certain route.

How do we View Availability Situation?

Run Transaction: CO09 Enter Plant & Checking Rule, against which the Availability is to be checked. Checking Rule for Sales Order = A, Delivery = B, Back Order = BO


"

In this screen, we can see:

> Availability Checking Group (Avail Check): 02 > Check Rule : A > End Lead Time Refers to the end of Replenishment Lead Time. If that is not included in the Configuration, then this field is not visible. > Totals Display: > Receipts = Sum of all +ve Quantities in Rec./Reqd qty Column (Leave out the last row, MRP Element 001, since it is a total) These are all the Planned Incoming Movements > Issues = Sum of all -ve Quantities in Rec./Reqd qty Column These are all the Planned Outgoing Movements


> Confirmed issues = Sum of all (+ve) Quantities in Confirmed Column These are the confirmations against ATP.

When is Availability Check Triggered?

While creating a Sales Order, Production Order, Delivery, etc. Below is a screen from Sales Order. At the bottom is a button for Check Material Availability. Also while creating the order, if the Availability situation cannot meet the requested delivery date, the system goes to Availability screen automatically.

How we arrive at a Confirmed Delivery Date?

Below is the logic the system uses to check availability:

> Using the Scheduling data from Delivery & Transportation Scheduling, the system does the backward calculation from the Requested Delivery Date. This is used to arrive at Material Availability Date.> On the Material Availability Date, system checks the Available Qty, as seen in CO09 in column Cum. ATP Qty. If the Available Qty is > than Required Qty, Requested Delivery Date is confirmed. Otherwise,> System moves into the future till it finds the required Available Qty. The new date is then the new Material Availability Date.> On getting the confirmed Material Availability Date, system does the Forward Scheduling to arrive at a Confirmed Delivery date.

Result of Availability Check


"

Above is the Availability Screen as seen in Sales Order. It has following Buttons:

One-time delivery - In the results of Availability, we have 3 options to choose from. This is Case 1, when we can confirm the Customer's Requested delivery Date. The details of this are visible in the first sub screen below.

Complete dlv. - This is Case 2, when we can confirm the Customer's Requested complete delivery at a future Date. The details of this are visible in the second sub screen below.

Delivery proposal - This is Case 3, when we can confirm the Customer's Requested delivery in partial quantities at future dates. The details of this are visible in the third sub screen below.

Continue - If we select one of the above options, the same gets saved in the ATP results. Otherwise, we can select this button. In that case, system leaves the ATP screen without saving the ATP results.

Control of Availability Check


"


"

Scope of Check - This shows the Stocks & Movements that system considers for availability.

What Configuration & Data do we need?

Controlling Elements:-

Requirements Type - Strategy to Determine Requirements Type:

· Using Strategy Group from Material Master (IMG Guide > Production > PP > DM > PIR > Planning Strategy > Define Strategy Group > Define Strategy)

· Else, Determine Strategy Group using MRP Group (IMG Guide > Production > MRP > MRP Groups > Overall Maintenance > Strategy Group; IMG Guide > Production > PP > DM > PIR > Planning Strategy > Assign MRP Group to Strategy Group)

· Else, In place of MRP Group, Material Type is used (IMG Guide > Production > MRP > Define MRP Groups for each Material Type)


· Else, Item Category + MRP Type > (determines) > Req. Type (OR) Item Category > (determines)> Req. Type (IMG Guide > SD > BF > AC & TOR > TOR > Determination of Requirements Type using Transaction)

· Then, Transaction not relevant for Availability Check.

Requirements Class - Requirements Type > (determines) > Requirements Class

(IMG Guide > Sales & Distribution > Basic Functions > Transfer of Requirements > Define Requirements Type)

Schedule Line Category

(IMG Guide > SD > BF > AC & TOR > AC > AC with ATP > Define Procedure for each Schedule Line Category)

Delivery Item Category

(IMG Guide > SD > BF > AC & TOR > AC > AC with ATP > Define Procedure for each Delivery Item Category)

Checking Group - Material type + Plant > (determines) > Checking Group

Checking Rule - For Sales Orders : A; For Deliveries : B; For Back Orders, we can define from: (IMG Guide > SD > BF > AC & TOR > AC > AC with ATP > Checking rule for Updating Back Orders)

Scope of Check - Checking Group + Checking Rule > (determines) > Scope of Check

Strategy Group - Used in the determination of Requirements Type

Partial Delivery Agreement - From customer master

Replenishment Lead Time - From material master

Material Master Data:-

MRP 1 > MRP Group

MRP 2 > Planned Delivery Time

MRP 2 > GR Processing Time

MRP 3 > Checking Group for Availability Check

MRP 3 > Strategy Group

MRP 3 > Total Replenishment Lead Time

Scheduling Data:- (IMG Guide > Sales & Distribution > Basic Functions > Delivery Scheduling & Transportation Scheduling > Maintain Duration)


Transit Time

Loading Time

Pick/Pack Time

Transportation Planning Lead Time

Re: How to find Path from T-code in SPRO

Goto T code SE93 - Enter OPJH & click on display,it gives you the Transaction

Text

Now using this,you can futher explore in SPRO settings.

I hope you can explore more by yourself.

.use search_sap_menu as tcode in the initial screen.2. enter the text for ex as order type.3. the system will display the path for that tcode.

Material: R-B299

________ How to use User exits? User exit USEREXIT_PLANT_SELECTION in Include LV03VFZZ……………………………………………………………

*Customer: 1002

Material: R-1160

Standard order: 13428 Created.

Functions of Requirement class:-


CREDIT MANAGEMENT : FI/SD

How To Do 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 by : Kapilaa

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


You need to be implemented Account Receivables and SD component. _________________________________________________ Accounts Receivables in

finance………………………………………… Credit Control Area definition and assigned to CoC. At which point the credit check should be done…………………….. E.g. at company code level or User exits: LVKMPTZZ, LVKMPFZ1 _______________________________________________Dunning

Procedure__________________________________

Automatic Credit check determination- Credit Control AREA, Risk Category and Credit group determines the action. (TC: OVA8) Img; S &

D; BF; Credit Management; Define automatic Credit Control.- Credit groups are assigned to Sales Document type., Control Area comes from Coc, or Sales area,

or Customer Master, or User exit.

____________________________________________________________ALE: Information is sent from centralized finance system to distributed SD systems____________

______________________________--Special G/L transactions_____________________________________________________________

____________________________Reconcilliation Account______________________________________________________________

Special GL transactions: Down Payments and Bill of Exchange. _________________________ Maintaining Authorizations for credit check / approval _________________ What is payment cards? Export credit insurance? Documentary payments?

Payment Guarentee procedure = Customer payment guarantee procedure + Document Payment guarantee procedure.

Partner functions==---1. Credit representative = KB2. Credit Manager = KM

REPORTING AND ANALYSIS…….


Lists are managed with special Tool called “ABAP list viewer”.

Sales order 13443 created.

Report RVV05IVV: Report;;; How to run?

Displaying additional column in the list.In SU3 enter the parameter: SD_VARIANT_MAINTAIN; A in the Value column

_______________________________________________Back order processing: What is it exactly___________________________________

OUTPUT DETERMINATION:………………..

BA00 = Output confirmation

VBDKA – SALES DOC HEADERVBDPA- Sales doc Item

VBDKL – Delevery note headerVBDPL – Delivery note item

VBDKR – Billing headerVBDPR- Billing item

BA00 – ORDER CONFIRMATIONBA01- EDI ORDER CONFIRATIONLD00 – ORDER NOTERD00 – INVOICERD03 – CASH INVOICE


KO00 – SALES ACTIVITYKRML – MAIL CREDIT PROCESSINGLP00 – SHEDULING AGREEMENTAN00 – ORDER CONFIRMATIONMAIL – INTERNAL OUTPUTZWWW – MAIL INTERNAL ORDER

SALES DOC. HEADER –> OUTPUT DETERMINATION PROCEDURE-> OUTPUT TYPE-> ACCESS SEQUENCE->ACCESSES->CONDITION RECORDS

MEDIUM, TIME AND PARTNER FUNCTION IN CONDITION RECORD.

Quotation 20000048 saved………….

Order: 13456 saved.

Report: RSNAST00

Running Reports related to SD- Tools; ABAP workbench; ABAP Editor = Reports used for output begins with SD70A- Report RSNAST00 = Tools; ABAP Wrokbench; ABAP Editor- Billing output: Report : SD70AV3A

Shipping:-………………………………………………………………………………………..Delivery split profile? Assigned to Delivery___________________________________________________

SAP Implementation Process

What is ASAP Methodology ASAP: Accelerated Systems Application and Products in Data Processing


All implementation projects have the following phases: Scoping - What is to be implemented i.e. which submodules are to be implemented some clients may not require credit management for example. Look at the project scope document carefully it will tell you what SAP sub-modules in SAP you should be prepared for. Usually the sales people along with project manager do it. As is - Here you understand the existing business processes of the client . Your BPOcollect all the ISO-documentation (if client is ISO certified), reports and forms at this stage and you analyse how and when the reports/forms are generated, where the data is coming from. You also do a Level -2 training for your BPO so he is made aware of all the required transactions in SAP. Once this is over BPO can start learning with the consultants help more about SAP. This is crucial because if you miss out any transactions the BPO may forget about some of his Business processes which may come up later. It is a good practice to ask the BPO to make flow charts to explain business processes.

To-Be - Parallely you map these processes to SAP. Processes that you are not sure of as to whether they are present in SAP or not you try to do a configuration of those processes, and along with the BPO(Business process owner he is the clients employee who knows about the clients business processes probably a middle management guy, ther can more than one), BPO involvement is required as he may be able to tell you his requirements better. Once you do the business modeling you will also be made aware of the gaps between as-is and to-be , here decisons have to be made as to whether a ABAP development/system modification is required or not and so on. Involve the BPO as much as possible and document everything it is good practice do not be lazy about it.

Business blueprint: Here the as-is and to-be and gap analysis is explained. This is the document that you will be using to do your configuration in the realization phase. Realization phase: Here you do the configuration in the development server (there are three clients -development,quality, production). You also decide on the master data format, so that BPO can go collect the master data. You also gove ABAP specifications for forms, reports etc, system modifications etc. Unit testing: Your BPOs and a few key users sit down and test your configuration in your module only. It is good to test the BDCs that you need for uploading data at this stage so you have more realistic data and your BDCs are tested. Integration testing:

Once all modules unit testing is over then the configuration is trasported to the Quality server, where testing for all the modules is done by BPOs and end user, this is to check if any problems are there in integration between various modules. Once all is okay from the QA server config is transported to the production server.

Go live preparation


Data uploading: The collected master data is checked and the uploaded into production server(sever and client I have used interchangeably). Now you are ready for go live i.e. users can now use the production server.

ASAP methodoligy means nothing but standard process for implementation of SAP, It consists of 5 phases. 1. Project preperation - consists of identifying team members and developing strategy as how to go. 2. Business Blue print - consists of identifying the client current process, reqeirement and how SAP provides solution. Consists of detailed documentaion 3. Realization -The purpose of this phase is to implement all the business and process requirements based on the Business Blueprint. 4. Final Preparation - The purpose of this phase is to complete testing, end-user training, 5. Go Live and Support All the functinal consultatns need good rapo with Abapers. right from uploading of legacy data, devoloping customised reports, BDC's, Forms etc, here functinal consultatns need to give guidence as to get the requried data for reports and all.. like the table name, fields etc

What is baseline configuration in sap? Base line and Final config is the third phase in ASAP methadology. The purpose of this phase is to implement all the business & process requirements based on business blue print. You customize the system step by step in 2 work packages: Base Line Configuration & Final Configuration. - Base Line Configuration: this phase comprises the priority requirements of the enterprise, ensuring that they can be implemented quickly. This phase can be completed without programming or enhancements to SAP systems. - Final Configuration: in this phase you confirm that all your requirements are met in the R/3 system. Final configuration is a transportation process that expands that base line solution

Documentation which is prepared before and in a project:

1) Templates 3) Fit Gap or Gap Analysis 4) Business Process Design 5) Business Process Model 6) Business Change & Impact 7) Configuration Design, which is just 5 % of Total SAP- have different names - 8) Future Impact & Change Assessment 9) Functional Design (Module Wise)


10) Risk Assessment 11) Process Metrics and Many More-- Which has impact on Business and its work flow

Note * This documents are prepared in Vanilla SAP Standards -- Things differ from one implementation to another, and it always depends on the type of business which is opting for SAP. What Are SAP End User Manual It is the same for every other modules although here I reference it mainly for SAP HR. 1) You should understand which targeted group for the end-user training is for. Do they have any computer background or not. 2) In what way they are going to make use of the manuals supplied to them during the course of training.

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


H) Each field in the international infotypes should be explained very clearly and ensure that they are comfortable with the fields of infotypes which have been configured for their company.

For example : info type 0001 Org Assignment insists about the three structures of the HR. We should explain each sub field like Emp Group, Emp Sub Group, Personnel Area and Sub Area and its importance and relevance to their company so as to understand while processing them from the end- user point of view . When an employee is hired into the company , now the end-user in a position to understand which employee group and subgroup, Personnel Area And Sub Area etc., should allotted.. Like this whatever comes across in SAP Easy Access should be insisted through the training of end users. I) Demo, exercises and solutions should be provided in the manuals. J) Glossary of terms and expansion of Acronyms, Abbreviations should be given. Like this each consultant should focus on end user training and prepare the documents. As is document: How to start doing the project in 'AS IS' ? Are you working as a technical person or functional person? This work is of a functional consultant. It involves understanding the complete functionality of the system. It involves detailed understanding of how the HR department is functioning because based on that only you would provide a solution to them. Like suppose you are implementing SAP HR module for them then in the AS-IS and TO-BE phase, you need to prepare all the documents of the process flow (you can prepare them in word). Like suppose you are implementing for PA then you need to identify how many personnel areas you need to make, how many subareas you will make, employee groups, subgroups, based on what you are classifying them? This all will come in the master data document which has to be approved from the client whoever he is .

Like if the current system is on mainframe or for some specific applications like for recruitment the system is on mainframes and the client wants to keep that system as well then interfaces need to be identified which will be there because you will have to upload the data to sap system using bdc. Like this for every process there will be a document. Even for actions like: - Hiring - Newly Hire - Termination -Transfer - Layoff etc You will have to see what all actions your client wants, like if there is an action transfer which is run for employee what all will be the reasons you will be configuring for that action. This will be told by the client which can come out after a series of meetings and after discussions you will have to come out with the document that these will be action types. These will be the action


reasons, these will be the action codes for that. This will be in the TO BE process document. After this phase is over complete configuration can be done. Actually AS-IS process in summary involves a : 1) Series of meeting with the client. 2) Gathering complete information about the existing system. 3) Preparation of the blue print documents describing the complete AS-IS process ,i mean the existing system. 4) Flow charts should be included in the as-is blue print process flow document describing the complete process. 5) After this is finished u have to give the TO-BE process structure that will be implemented in SAP. 6) After that there will be some things which cannot be implemented in SAP so the gaps are to be identified. 7) These gaps are to be documented in white paper for the client. It is a lengthy process but not so difficult only the thing is that the functionality is to be understood properly.

SAP BLUEPRINTING Defining the Business Processes After you have defined your organizational structure for R/3, the definition of the business process for your Business Blueprint is the next step. You now map the enterprise requirements onto R/3 business processes, in order to create the conceptual design for your R/3 implementation. For this, the following activities need to be carried out: • Conducting business process workshops • Completing the Business Blueprint, reviewing it and obtaining management signoff • Setting up an end user training schedule Besides determining the R/3 functionality to be implemented, the following types of requirements should be identified in the business process workshops: • Reporting requirements • Interface requirements • Conversion requirements • Enhancement requirements • Authorization requirements Since all the results gathered during the workshops will subsequently create the Business Blueprint, the importance of this step cannot be underestimated. The main tool used to define the business processes is the AcceleratedSAP Question & Answer Database in conjunction with the R/3 Reference Model. In the process, information is gathered using the following tools: • Business Process Questions (via R/3 Reference Model) • Customer Input (CI) Template • Business Process Master List • Knowledge Corner


A functional spec should theoretically mean that the ABAPer should be able to take the design document you have prepared, go and sit in a dark corner of the office and build the whole report..... this rarely if ever happens, but I think that the theory.

When you write a functional spec, you are meant to be turning the clients requirements into a design document that a techno can then build from.

Some of the things you may want to think about are: Report logic - What information is the report trying to get, what logical links are required to link the data together - like master data and payroll data, and org mgt data, and how should this be linked, an imp

how should this be linked, an important bit to remember here is the time selection, do you want all the data in the system, or only the data relevant on the day, or over a month etc.

Selection screen - What fields are required as selection options

Authorisations - Should the report check the 'runners' authorisations and tailor the output accordingly

Output - What fields are required to be output, in what order, in what file type, for example this could be a text file, or just out to the screen of the runner.

Error handling - What should the report do when it encounters a problem eg what scenarios would constitute errors - what should happen etc.

Test mode - does the report require running in test mode prior to a file being produced?

What are the roles & responsibilities as a sap hr functional consultant As a Functional Consultant, one needs to first understand the business process of the client and then map it in SAP to accommodate those business processes.

In the Business Blueprint stage, you need to prepare AS-IS (which is a detailed list of the current business practices of the client) and then , you need to prepare a QADB (Questions and Answer Data Base) questionnaire and send it to the client.

Then, based on client's answers, you need to prepare TO-BE list ( procedure in SAP to match the client's business process).

You need to map AS-IS process and TO_BE process.


What are the differences between a functional and business consultant? The difference between Functional consultant and Business consultant are as follows: 1) A funcitonal consultant is able to configure the system unlike business consultant. 2) Functional consultant know more about business process unlike Business consultant. 3) A business consultant will bring business process knowledge and provide it to functional consultant who in turn used this knowledge to configure the system. 4) Functional consultant has more configuration knolwledge then Business consultant The responsibilities of a support consultant are: - Primarily responsible for Handling tickets and application support to the endusers - When an issue comes diagnose, analyse and solve the issue - Responsible for any enhancements - Writing functional specs and interacting with Abapers to develop any user exits - Training the end users and preparing end user training material For those who wished to know the role of a functional consultant. Below is one view: A functional consultant evaluates the demands in talking with the customer\'s representatives, transforms the essence into an abstract and algorithmic business model. Hence, he identifies the use cases and transforms them into logical and technical views. Then the main task starts: customizing the respective business area and making sure the system reacts in the manner according to the constraints of the requested use case. The consultant documents the settings and prepares proper guidelines that allow other consultants to do further changes or repairs with due efforts. The consultant takes care that proper training is given to the users and that the system is usable, performing appropriately and the business flow is complete and correct. During go live he assists the technical staff by testing the behaviour of the system. After go live he guarantees that the procedures remain usable and consistent in real live situation and proposes enh

The consultant takes care that proper training is given to the users and that the system is usable, performing appropriately and the business flow is complete and correct. During go live he assists the technical staff by testing the behaviour of the system. After go live he guarantees that the procedures remain usable and consistent in real live situation and proposes enhancements. The main duty of a consultant is to transfer external know-how to the client. It is not manpower that counts but intelligence, understanding of processes, a feeling for defects and general a common sense. Role of a Functional Consultant in an End To End Implementation 1. Functional consultant is expected to generate knowledge about the current business process,


design current business flows, study current business processes and its complication, in all we can say getting through with current business setup. Flow diagrams and DFD are prepared, most of the time in Vision format, all this forms the part of AS IS document. 2. Everything configured has to be documented as per their categories in the form of predefined templates, these have to be then approved by the team leads or who ever the consultant is reporting to. 3. Mapping and GAP analysis is done for each module, I have seen people defining integration after mapping, gap analysis and configuration is done, but as per my experience in implementation, it is a simultaneous process. 4. Before starting configuring future business processes in SAP, the DFD/ERD are prepared, this documentation is called TO BE, which can be also siad as the result of mapping and gap analysis. 5. Sometimes Functional consultants are also expected to prepare test scripts for testing the configured scenarios. 6. End user manual and user training is also expected from F.Consultants. The project normally starts off with a Kick off meeting in which the team size, team members, reporting system, responsibilities, duties, methodlogy, dates and schedules, working hours which have been predicided are

working hours which have been predicided are formally defined.

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


corrected in Golden (may again as well be practised in the sandbox prior to Golden) and accordingly transported back to 180 (Unit Test) until the unit test affected

by that particular config is satisfactory.

The Golden client remains the 'database' (if you wanna call it that) or you may rather call it the 'ultimate' reference client for all the good, complete and final configuration that is being used in the implementation.

In summary: Landscape : is the arrangement for the servers IDES : is purely for education purpose and is NOT INCLUDED in the landscape. DEVELOPMENT ---> QUALITY ----> PRODUCTION DEVELOPMENT : is where the the consultants do the customization as per the company's requirement. QUALITY : is where the core team members and other members test the customization. PRODUCTION : is where the live data of the company is recorded. A request will flow from Dev->Qual->Prod and not backwards. These three are landscape of any Company. They organised their office in these three way. Developer develop their program in Development server and then transport it to test server. In testing server tester check/test the program and then transport it to Production Server. Later it will deploy to client from production server. Presentaion Server- Where SAP GUI have. Application Server - Where SAP Installed. Database Server - Where Database installed

Taxation:Running program / SE38/ SA38__________________________________-How to copy tables from 000 TO 800_______________________--------

Account key: NVV, VS1, VS2, VS3, VS4, MW1, MW2, MW3, MW4,

Intra state: Sales tax – saler collects and remits the tax on salesInter state: Use tax – user remits the tax on sales


Self assessment: Instead intrastate sales and purchases company remits the sales tax instead of seller.

Sells tax: sellers bookCompany 1 Dr. 100Sales tax accrual Dr. 10 To sales revene 110

Sells tax: Purchasere’s book:Cost account Dr. 110 To Company 3 110

Self Assessment: Either it is a inter state and intra state sales or purchase, company itself pays the tax to the government and not to the seller. – Direct pay permit or exemption certificate.

Sales tax calculation procedure : TAXUS (tad code), TAXUSJ (tad code and jurisdiction code), TAXUSX(third party package like taxware)

Caluculation procedure is assigned to a specific country.

Tax codes for TAXUSJ (Default samples)S0 – A/R Sales tax exemptS1 – A/R Sales tax taxable

I0 – A/P sales tax exemptI1 – A/P Sales tax taxable

U0 – A/P Use tax exemptU1 – A/P Use tax taxable

Tax jurisdiction code:Maximum four levels in TAXUSJ and six levels in TAXUSX

To calculate tax price you use jurisdiction code with tax code. Jurisdiction code determines how the tax amount is divided among different tax authorities. E.g. Country, State, county, city

Tax jurisdiction code: Total 9 characters – first 2 denote state, next 3 denote county and last four denote city


Tax determinationInfluencing factors – Origin and destination country and material / customer taxability.

Three methods:1. Non jurisdiction method2. Jurisdictin method3. External system with jurisdiction method

The calculation procedure for USA is TAXUSJ.Financial accounting:

- Check calculation procedure:

IMG; Financial accounting; Financial accounting global settings; Tax on sales / purchases; Basic settings; check calculation procedure.

- Condition types: FI AND SD SAME VIEW FOR SAME CONDITIONIMG; Financial accounting; Financial accounting global settings; tax on sales / purchases; Basic settings; Check calculation procedure; condition typeCondition typesJP1E, JP1I, JP1U JP2E, JP2I, JP2U - Access sequence in all 9 TAXJJP3E, JP3I, JP3U

- Access sequence – TAXJ – IMG; Financial accounting; financial accounting global settings; tax on sales / purchases; Basic settings; check calculationAn access sequence should be there in table T682

- Check calculation procedure: Sample condition types and their use- Condition Type Description Account Key- Distributed to G/L - JP1I A/P Sales Tax 1 Inv. NVV- JP2I A/P Sales Tax 2 Inv. NVV- JP3I A/P Sales Tax 3 Inv. NVV- JP4I A/P Sales Tax 4 Inv. NVV- Expensed - JP1E A/P Sales Tax 1 Exp. VS1- JP2E A/P Sales Tax 2 Exp. VS2 Account key- JP3E A/P Sales Tax 3 Exp. VS3- JP4E A/P Sales Tax 4 Exp. VS4- Self-Assessment


- JP1U A/P Sales Tax 1 Use MW1- JP2U A/P Sales Tax 2 Use MW2 -------Negative entry in condition type definition- JP3U A/P Sales Tax 3 Use MW3- JP4U A/P Sales Tax 4 Use MW4- Accrued - JR1 A/R Sales Tax 1 MW1- JR2 A/R Sales Tax 2 MW2- JR3 A/R Sales Tax 3 MW3- JR4 A/R Sales Tax 4 MW4

In all above conditions Access sequence used is TAXJ – Access : USA TAXES with jurisdictin – Fields (keys) : Country, tax code, tax jurisdiction code

MWAS – Output tax – access sequence : MWST - ACCESS: Tax classification – Fields: Country , Tax code

BASB – Base amout – no access sequence

Note account keys are default in the system and cant be changed.

Distributed to G/L is a tax type in which the total payable(invoice+tax) is costed i.e is included in either an expense account or in a material account. In expensed, the total payable is splitted;into a tax account receivable and a The journal entries would be somewhat like this:

For a 10% tax on an invoice of $2000.

For Distributed G/L:

Vendor 2200 DrMaterial(or expense) 2200 cr

For expensed:

Vendor 2200 DrMaterial(or expense) 2000 CrTax expenese 200 expense or material account. Cr

In FTXP tax procedures TAXUSJ or TAXUSX have three sections for vendorinput taxes and one section for customer output taxes.

If you activate the levels (steps) in the first section 'DistributedG/L', the ones with account key 'NVV', then you do not get a postingseparate tax line items. You can see this in transaction OBCN, NVV hasposting indicator '3', Distribute to relevant expense/revenue items.


Do NOT change this posting indicator.

If you want the tax amounts to be posted to tax accounts, then youuse the second section 'Expensed', with posting keys VS1,2,3,4'.These account keys have posting indicator '2', Separate line item.Then in transaction OB40, the accounts are broken down by chart ofaccounts, process key (account key), and optionally by tax codeif selected under 'rules'.

Section one and section two are alternative methods of handling thetax. Do not combine active lines in section one (NVV lines) withactive lines in section two (VS1,2,3,4) in the same tax code. Thiswould be a configuration mistake.

To sum up:You configue one vendor tax code with NVV lines active to distributethe tax to existing line items, and a different vendor tax code withVS1,2,3,4 lines active to post the tax to a separate line item, andthen you have to use the tax code that makes the posting you want.

I hope this information clarifies your customizing issue .

When you start using jurisdiction codes you will need these levels for that purpose. For example if you have State Tax of 6%, County tax of 2%, and City tax .25%, you will enter 6% in MW1, 2% in MW2 and .25% in MW3.

- Assign country to calculation procedureIMG; Financial accounting; financial accounting global settings; tax on sales / purchases; basic settings; assign country to calculation procedure.

- Chack and change settings for tax processing – posing in accounts – account keys are assigned or not?

IMG; Financial accounting; Financial accounting global settings; tax on sales / purchases; basic settings; check and change settings for tax processing


- Specify structure for tax jurisdiction code – i.e. 2, 3, 4

IMG; Financial accounting; Financial accounting global settings; tax on sales / purchases; basic settings; specify structure for tax jurisdiction code.

- Define Tax Jurisdiction codesYou define jurisdiction codes for each jurisdictionIMG; Financial accounting; Financial accounting global settings; tax on sales purchases; Basic settings; Define tax jurisdiction codes

- Define tax codes for sales and purchasesIn this activity you define allowable tax code and tax types used in TAXUSJ.In this you allocate percentage to each jurisdiction code level out of total amount. Four levels - 1. Distributed to GL 2. Expensed 3.Self assessment 4. AccruedHere also you define whether output tax or input taxIMG; Financial accounting; Financial accounting global settings; tax on sales / purchases; calculations; define tax codes for sales and purchases.

Distributed to G/L is a tax type in which the total payable(invoice+tax) is costed i.e is included in either an expense account or in a material account. In expensed, the total payable is splitted;into a tax account receivable and a The journal entries would be somewhat like this:

For a 10% tax on an invoice of $2000.

For Distributed G/L:

Vendor 2200 DrMaterial(or expense) 2200 cr

For expensed:

Vendor 2200 DrMaterial(or expense) 2000 CrTax expenese 200 expense or material account. Cr

In FTXP tax procedures TAXUSJ or TAXUSX have three sections for vendorinput taxes and one section for customer output taxes.

If you activate the levels (steps) in the first section 'Distributed


G/L', the ones with account key 'NVV', then you do not get a postingseparate tax line items. You can see this in transaction OBCN, NVV hasposting indicator '3', Distribute to relevant expense/revenue items.Do NOT change this posting indicator.

If you want the tax amounts to be posted to tax accounts, then youuse the second section 'Expensed', with posting keys VS1,2,3,4'.Tax 1, Tax 2, Tax3, Tax4 are the levels of jurisdiction code and you need to specify % tax on each level

- Define tax accounts

Specify the tax accounts to which the sales and use tax is posted automatically.

IMG; Financial accounting; Financial accounting global settings; Tax on sales / purchases; Posting; Define tax accounts.

Chart of accounts CANA

- Maintaining Tax category in GL master records.SAP Menu; Accounting; Financial accounting; general ledger; Master records; Individual processing; In company codeEnter general account and specify tax category; e.g. out put tax allowed, or output and input tax allowed etc.

SALES AND DISTRIBUTION:- Maintain condition type:

Img; Sales and distribution; Basic functions; Pricing; Pricing control; Define condition types; Maintain condition types.Condition type: UTXJ; Access sequence: UTX1 – Sales Tax SD interface

- Define Access sequence: UTX1IMG; Sales and distribution; Basic functions; Pricing; Pricing control; Define access sequenceFields in Access: Departure country / Destination contryCountry / State/ Customer classification / Material classificationDomestic taxes

- Define and assigne pricing procedure


1. Maintain pricing procedure and 2. Define pricing procedure determinationIMG; Sales and distribution; Basic functions; Pricing; Pricing Control; Define and assign pricing procedure.Pricing procedure: RVAJUSCondition type UTXJ is included in the pricing procedure RVAJUS.

- Define tax determination ruleIn this step you assign condition type UTXJ to country USA which is used in sales tax calculation, to country US. You can assign more than one condition type to a country.Note: You have already assigned calculation procedure for tax TAXUSJ to country USA. This way UTXJ and TAXUSJ are linked. From UTXJ the country is decided and from country the tax calculation procedure is decided.IMG; Sales and distribution; Basic functions; Taxes; Define tax determination rule. Transaction code: OVK1

- Define tax relevancy of master record.IMG; Sales and distribution; basic functions; taxes; Define tax relevancy of master record.

Customer master records (Transaction OVK3/Table TSKD)Tax category Name Tax classification DescriptionUTXJ Tax Jurisdiction Code 0 ExemptUTXJ Tax Jurisdiction Code 1 Taxable

Material master records (Transaction OVK4/Table TSKM)Tax category Name Tax classification DescriptionUTXJ Tax Jurisdiction Code 0 ExemptUTXJ Tax Jurisdiction Code 1 Taxable(Here Tax category = condition type for specific country)

- Maintaining material master record.

Maintain tax classification in material master – sales org. 1

- Maintain customer master.Maintain tax classification in Customer master – Sales screen – Billing.


- Condition recordsTwo types of condition records you need to maintain.1. Tax jurisdiction code condition record2. Tax code condition record.

1. Tax jurisdiction code condition record.You maintain this condition record for the condition type UTXJ – Keys : Region, Tax classification of customer; tax classification of material; Tax code.ExampleFor country US and condition type UTXJ, you maintain the following entries:Region Tax classification for customer Tax classification for material Tax codePA 0 0 S0PA 1 0 S0PA 0 1 S0PA 1 1 S1

2. Tax code condition record. Which we already defined.. It specifies the rate of tax for each jurisdiction level and jurisdiction code for that tax code.

First it decides whether it is taxable or not from customer classification.

It it is taxable than,from Tax jurisdiction code condition record tax code is determined for customer and material and tax code contains the details of jurisdiction levels and % tax for each condition level and jurisdiction level for sales tax calculation (TAXUSJ – Condition - Access sequence used is TAXJ – Access : USA TAXES with jurisdictin – Fields (keys) : Country, tax code, tax jurisdiction code ).

Materials:

- Define tax jurisdictionAssign jurisdiction code to plant so when entering a purchase order, the purchasing plant’s jurisdiction code is automatically used to calculate sales tax that must be paid to the seller.

IMG; Materials management; purchasing; Environment data; Define tax jurisdictions. Choose the plant for which you want to assign jurisdiction.


Customizing for Non-Jurisdiction MethodPurpose

In this process, you configure your R/3 System to calculate sales and use tax without using tax

jurisdiction codes.

Process Flow

Step 1:

Assign the calculation procedure TAXUS to the country US.

To assign TAXUS to US, in Customizing for Financial Accounting, choose Financial Accounting

Global Settings _ Tax on Sales/Purchases _ Basic Settings _ Assign Country to Calculation

Procedure. You can also access this activity in Customizing for General Settings by choosing Set

countries _ Define countries.

See also: Assign Country to Calculation Procedure [Ext.]

Step 2:

Create the tax rates according by country and tax code.

To define the tax codes, in Customizing for Financial Accounting, choose Financial Accounting

Global Settings _ Tax on Sales/Purchases _ Calculation _ Define Tax Codes for Sales and

Purchases.

See also: Define Tax Codes for Sales and Purchases [Ext.]

Step 3:

Verify tax by country configuration and that US is assigned to tax categories UTX1, UTX2, UTX3,

and UTX4.

To check the tax determination rules, in Customizing for Sales and Distribution, choose Sales _

Pricing _ Taxes _ Define Tax Determination Rules. You can also use transaction OVK1 to


maintain table TSTL.

See also: Define Tax Determination Rules [Ext.]

Step 4:

Verify customer tax category by checking that UTX1, UTX2, UTX3, and UTX4 are assigned tax

classifications (1 for taxable and 0 for exempt).

To check the tax classification in the customer and material master records, in Customizing for

Sales and Distribution, choose Sales _ Pricing _ Taxes _ Define Tax Relevancy of Master

Records. Choose Customer Taxes.

See also: Define Tax Relevancy Of Master Records [Ext.]

Step 5:

Verify customer tax category by checking that UTX1, UTX2, UTX3, and UTX4 are assigned tax

classifications (1 for taxable and 0 for exempt).

To check the tax classification in the customer and material master records, in Customizing for

Sales and Distribution, choose Sales _ Pricing _ Taxes _ Define Tax Relevancy of Master

Records. Choose Material Taxes.

Documents

SDreview