It is used for different functions. In Pricing the condition types leads you to differentiate different types of discounts, in output determination, batch determination, difference between two output types, such as delivery note or order confirmation, between different strategy types
Access Sequence
It specifies the order in which system searches or access the condition records from condition table
Difference between PB00 & PBXX
1. Condition maintained in PB00 is time dependent whereas PBXX is time independent.
2. Condition type PB00 – used for IR, RFQ, Contract, Schedule Agreement Condition type PBXX – used for PO.
Calculation Schema
The main function of calculation schema is to provide framework of steps for the price determination process to specify the discounts, surcharge, freight rebate etc.
It also determines the sequence of conditions that are to be followed and in which sequence.
Schema Group Vendor
The main function of it is to identify or to pick the right process and conditions for a particular vendor.
Schema Group Purchasing Organization
Key that determines which calculation schema (pricing procedure) is to be used in purchasing documents assigned to the relevant purchasing organization.
Schema Group
It allows to group together the purchasing organizations, which uses the same calculation schema.
Steps:
-1. Create Access sequence 2. Create condition types
3. Create pricing procedure or calculation schema
4. Link pricing procedure & access sequence to condition type 5. Create schema group for vendor
6. Create schema group for purchase organization
7. Assign schema group vendor-to-vendor master record in purchasing data view 8. Assign schema group purchase organization to our purchase organization 9. In info record purchase organization data enter condition types and pricing or calculation procedure
CUSTOMIZE SETTINGS:
-SPRO --> IMG-->MM-->PUR-->Conditions -->Define price determination Process 1. Define access sequence
5. Assignment of schema group to PUR org
6. Define schema determination à determine cal schema for standard PO.
You can start with the following sequence.
a) Definition of Condition tables ( in case standard condition tables does not suffice the requirement ) - M/03
b) Creation of Access sequence to include the condition types created in step a - M/07 c) Creation of condition types with Access sequence created in step b - M/06
d) Setting up of calculation schema with the sequence of condition types created in step c - M/08 e) Creation of Vendor schema - OMFN
f) Assignment of Vendor schema to your vendors XK02 g) Creation of Purchasing organization schema - OMFM
h) Assignment of Purchasing organization schema to your own purchasing organization OMFP i ) Linking Vendor schema, Purchasing organization schema and Calculation schema. OMFO
MM Tables
EINA Purchasing Info Record- General Data
EINE Purchasing Info Record- Purchasing Organization Data
MAKT Material Descriptions
MARA General Material Data
MARC Plant Data for Material
MARD Storage Location Data for Material
MAST Material to BOM Link
MBEW Material Valuation
MKPF Header- Material Document
MSEG Document Segment- Material
MVER Material Consumption
MVKE Sales Data for materials
RKPF Document Header- Reservation
T023 Mat. groups
T024 Purchasing Groups
T156 Movement Type
T157H Help Texts for Movement Types OY01- Country
OY04 – Decimal settings SU01 - SU01
SCC4 – SCC4 – display clients SE11 – Tables Display
SE71 - Form Change SE17 – Tables Content SE18, 19- Tables Content SE38 - Program Execution SA38 Program Execution SE09 - Transport Request SE10 - Transport Request
NACE - Condition for output Control SE16 - Data Browser
OMWD – valuation grouping code OMSY - periods
OMS2 - categories – define attributes of mat OBYC – AADet.
OBBG – Tax Assignment FTXP - Tax code Creation OB40 - A/C assignment OBCN – A/C keys
Se91 - msg maintenance Omrf – stochastic block sm21 – log analysis
se80 – object navagator
se30 – ABAP run time analysis su01 – user maintenance SCC1 – client copy transport
Physical Inventory
1. Create physical inventory doc – MI01
2. Set Posting Block for Physical Inventory – in the above doc 3. Enter the Physical Inventory – MI04
4. Post the differences-MI07
What are Tickets in SAP?
What are Tickets in SAP
Tickets in SD can be considered as the problems which the end user or the employee in the company face while working on R/3. Tickets usually occur during the implementation or after theimplementation of the project. There can be numerous problem which can occur in the production support and a person who is working in the support has to resolve those tickets in the limited duration, every ticket has the particular deadline alert so your responsibility is to finish it before that deadline.
To begin with , we should give “TICKET” to you for not knowing it.
Here is an eg of a ticket raise:
End user is not able to
1. Create Sales order for a customer from a New plant , since shipping point determination is not happened . ( Without Shipping point the document becomes INCOMPLETE and he will not be able to proceed further like DELIVERY, BILLING).
He raises a ticket and the priority is set in one of the below:
1. Low 2. Medium 3. High.
Now you need to solve this ticket. You would analyze the problem and identify that the SP configuration has to be done for the new plant.
You would request a transport for DEV CLIENT to BASIS. You do the change and Request one more Transport to BASIS for QA client. The End user will test the same by creating a sales order for the new plant and approve it.
Finally, you request a transport to move the changes to PRODUCTION. Once the change is deployed in production the TICKET is closed. What I have given is a small example. You would get some real issues with severity HIGH in your day-day support.
Handling tickets is called Issue Tracking system. The errors or bugs forwarded by the end user to the support team are prioritized under three seviority High, Medium and Low. Each and every seviority as got its time limits before that we have to fix the error.
The main job of the supporting consultant is to provide assistance on line to the customer or the organisation where SAP is already implemented for which the person should be very strong in the subject and the process which are implemented in SAP at the client side to understand,to analyse,to actuate and to give the right solution in right time.This is the job of the support consultant.
The issues or the tickets(problems) which are arised is taken care of on priority basis by the support team consultants.
The work process in support projects are given below for your reference.
1. The customer or the end user logs a call through any tool or by mail (RADIX).
2. Each one of the support team is a part of support group.
3. Whenever a customer logs a call he /she has to mention to which work group (by name).
4. Once the calls came to the work group the support consultant or the team need to send an IR (Initial Response) to the user depending upon the priority of the calls. (Top,High,Med,Low,None)
5. Then the error is fixed, debugged by the support consultant or the team. Then after testing properly by generating TR(Transport Request through the basis admin)
6. Then it is informed to the end user/customer/super user about the changes which have moved to the production server by CTS process.
These are the process. In summary, what I understand is that if any configuration or customization is required to solve the issue, then the consultant have to work on DEV Client, then the end user will test it in the QA client and after approval the BASIS consultant has to transport it to the PRODUCTION
For Import PO
- You should have different Pricing Procedure ,with all the Duties conditions defined.
- Import Vendor , with import currency
- Different Document type for import PO, in the PO for the Customs conditions give the Customs Vendor code.
- In PO tax code to be Zero or Nil %
- Do MIRO for Customs Vendor before doing MIGO
- Aftre doing MIRO do GR for the Item ( in MIGO you will get popup for the MIRO document done, excise details from this is populated in to the PO )
TOTAL IMPORT CONFIGURATION AND CYCLE in ur pricing u have to create following
JCDB IN: Basic Custom Duty JCV1 IN : CVD
JECV IN : Ed Cess on CVD J1CV IN : H&SECess on CVD JEDB IN : Ed Cess on BCD JSDB IN : H&SECess on BCD JADC Additional Duty of Custom
JCV1, JECV, J1CV and JADC will go to Excise MODVAT Accounts and JCDB, JEDB and JSDB will get loaded on inventory.
In M/06, for all above conditions, keep following controls;
Cond. class A (Discount or surcharge) Plus/minus A (Positive) Calculat.type A (Percentage)
Cond.category B (Delivery costs)
Activate "Currency Conversion" and "Accrual"
Now for setoff
maintain the following conditions in excise default settings.
JCV1, JECV, JADC
path: spro>logistic general >tax on goods movements>India >basic settings>determination of excise duty >maintain excise defaults >
along with ur tax procedure maintain these conditions in the specified fields JCV1 in CVD condition field.
JECV in ECS condition field.
JADC in ACD condition field.
in case of SECess on CVD, no need to maintain.
it is hardcode in the standard
Vendor in GR 2 (Entry always possible) Import scenario
1.Create material master of import goods.
2. Create vendor master record of import vendor and Customs clearing vendor.
3. Maintain CIN settings.
4. Maintain J1id.
5. Maintain Pricing procedure SAP standard JIMPOR.., maintain required conditions..JCDB, JCV1...
6.Assign the schema to respective import vendor in purchasing view of VMR.
7. Create import PO, ZERO tax code ,check in conditions of JCDB, JCV1 the customs clearing vendor(Indian vendor) and percentage is assigned. This can be done by In condition tab select condtion then click on display, then enter.
Save the PO.
8. MIRO --Capture Bill Of Entry.(Commercial Invoice No.,).Customs clearing first .Here CVD will b converted to BED.
9. Capture Excises invoice--j1iex.
10.MIGO. here system will ask u for the commertial invoice no ,give no gen in step8 12.Post Excise Invoice.
13.MIRO...Payment to vendor(import vendor)
In case of Normal Import Purchase, you will be aware of maintaining the Vendor Code of Customs Office against the following condition types;
JCDB IN:Basic Custom Duty JCV1 IN : CVD
JECV IN : Ed Cess on CVD J1CV IN : H&SECess on CVD JEDB IN : Ed Cess on BCD JSDB IN : H&SECess on BCD JADC Addnl Duty of Custom
Use above conditions and Customs Office Vendor when you have to pay duty to Customs Office.
In case of Advance License,
Here in this case, create following condition types in addition to above conditions and assign in the Import Pricing;
ZCV1 IN : CVD (Adv Lic) ZEC1 IN : Ed Cess on CVD Z1CV IN : H&SECess on CVD ZADC Addl Duty of Custom
And create Vendor Code for each Advance License No and assign this Vendor Code against the following condition types in Import PO;
JCDB IN:Basic Custom Duty ZCV1 IN : CVD (Adv Lic) ZEC1 IN : Ed Cess on CVD Z1CV IN : H&SECess on CVD ZEBC ED Cess on BCD ZSDB H&SECess on BCD ZADC Addl Duty of Custom
And do the rest of process similar as you do in case of Import Purchase In case of Import Purchase;
1. First you create Import PO and input all the Import duties in PO.
2.Then you do LIV for Customs Office (Here you enter all the Import duties as per Bill of Entry) and following A/c entry get generated;
Customs Office A/c - Cr (Vendor Recon A/c) Customs Duty Clearing A/c - Dr (OBYC - ZCC) CVD Clearing A/c - Dr (OBYC - ZCV)
3. Then Capture Bill of Entry in J1IEX.
4. Then you do GR w.r.t. Import PO (MIGO), Accounting Entry will come as following;
Stock A/c - Dr (OBYC - BSX)
GR/IR Clearing A/c - Cr (OBYC - WRX) Customs Clearing A/c - Cr (OBYC - ZCC)
5. Post Bill of Entry in J1IEX, and Accounting Entry will come as following;
CENVAT Receivable A/c (BED, ECS, SECess and ADC) - Dr (From Account Detmn of GRPO with Sub Trans Type - IP)
CVD Clearing A/c - Cr (From Compnay Code Settings of Excise) 6. MIRO - For Import Vendor
Import Vendor - Cr (Recon A/c) GR/IR Clearing A/c - Dr (WRX) 7. MIRO - For Clearing Agent Out of following conditions;
JCDB IN:Basic Custom Duty JCV1 IN : CVD
JECV IN : Ed Cess on CVD J1CV IN : H&SECess on CVD JEDB IN : Ed Cess on BCD JSDB IN : H&SECess on BCD JADC Addnl Duty of Custom
JCDB, JEDB, JSDB will get loaded to Stock and JCV1, JECV, J1CV and JADC will get posted to CENVAT Receivable A/c
In M/08, assign A/c Key ZCC to JCDB, JEDB, JSDB conditions and Customs Clearing A/c in OBYC and A/c Key ZCV to JCV1, JECV, J1CV and JADC conditions and CVD Clearing in OBYC.
Note: - Here you don't have to use Tax Procedure Accounting (OB40) in case of Imports. Only maintain a Zero % Tax Code in Import PO.
Also check following;
SPRO > Logistics - General > Tax on Goods Movements > India > Basic Settings > Determination of Excise Duty > Maintain Excise Defaults > Here assign following for Tax Procedure;
CVD cond. - CV1 ECS cond. - JECV ADC cond. - JADC
And J1CV need not be assigned since it is hard-coded in SAP Standard program.
Also do account determination in OBYC as your have already done for MIRO of Customs Invoice.
Also check in SPRO > Logistics - General > Tax on Goods Movements > India > Basic Settings >
Maintain Company Code Settings > Here Assign CVD Clearing A/c in your Company Cod