Beruflich Dokumente
Kultur Dokumente
GST
GST Configuration:
1. Access Sequence: OBQ2, copy MWST and create input and output access key(ISSS,OSSS)
a.Input: CGST,SGST,IGST,UGST
b.Output: CGST,SGST,IGST,UGST
a.Input:CIS,SIS,IIS,UIS
b.Output:COS,SOS,IOS,UOS,
5.Define Tax procedure: OBYZ, Append your GST condition type to TAXINN tax procedure.
6.crete GL accounts:FS00
Double click on account key one by one:CIS, posting 40& 50 cr,dr and assign GL account assets for
input. Liabilities for output GL A/C.
Country key:IN/DE
Tax code:G1(0%,5%,12%,18%,28%)
Tax procedure:TAXINN
G3:12% I e CGST:6%,SGST:6%
Inter input Tax:G6:0%,G7:5%,G8:12%,G9:18% etc, this is integrated tax between two states
A3:12% I e CGST:6%,SGST:6%
Inter input Tax:B1:0%,B2:5%,B3:12%,B4:18% etc, this is integrated tax between two states
TO give vendor no, amount, click on tax, enter expense account 400000 and enter amount
TO give Customer no, amount, click on tax, enter Revenue account 300000 and enter amount
SM30, Table:J_1ICONDTAX
FICO:
AR and AP:
1. Company code:7777
2. Chart of AC:Ob13:7777,Assin to company code:OB62
3. G/L Accounts Groups:OBD4
4. Filed status area:OBC4
5. Field status area assigned to company code:OBC5
6. Retained Earning AC:OB53
7. GL A/C:FS00: 100000-Liabilities(G001-Balance sheet),200000 (Assets-G005-Balance
sheet),300000(Expense-P&L-G001),400000(Income-P&L-G001)
8. Define Fiscal year:OB29
9. Assign Fiscal Year:OB37
10. Period open and Closed:OBBO
11. Assign Period(Open & Close):OBBP
12. OB52(Period open & Closed)
13. Number Ranges:OBA7
14. Tolerance Limit:OBA4
15. Posting :FB50(GL Postings) error: There is no item category assigned to account in chart of
accounts SAP, settings:Financial Account Splitting—select Deactivation per company code—
position-company code-select check box inactive.
16. Error: No item category assigned to account 100000/ssss.(Financial Acounting-GL Accouting
New-Business Transaction-Document Splitting
For Vendor creation:XK01-FS00-1st tab-check Balance sheet, 2nd Control tab-Recon account type
is Vendor, tick line item display, 3rd tab-create/bank/Interest, FSG G067
AR:
7.Invoice FB70
8.FBL5N Overview
9.Payment:F-28
AP:
3.Creat vendor:FK01
4.Number Ranges: OBA7 , 17 for Vendor Doc, 15 for vendor payment, 19 for invoice, KA,KR,KZ
6.Customer Tolerance:OBA3
8.FBL1N Overview
9.Payment:F-53, Bank AC
Division SD, MM
Sales Order
Taxes SD, FI
Delivery
Packing SD, MM
Introduction
A user exit is a place in a software program where a customer can arrange for their own tailor-made program to be
called. In R/3, some user exits use Include statements to include customer program enhancements that are called from
the program. Other user exits use tables that are accessed through customization.
Warning
Documentation below is copied from SPRO activities documentation and SAP library :
Relevant Information
CMOD Customer Exits
Include Routines It is reserved for customers, for which you need a modification key
Customer Exits
Include Routines
Include Description
MV45AOZZ For entering additional installation-specific modules for sales document processing
which are called up by the screen and run under PBO (Process Before Output) prior
to output of the screen.
MV45AIZZ For entering additional installation-specific modules for sales document processing.
These are called up by the screen and run under PAI (Process After Input) after data
input (for example, data validation).
MV45AFZZ For entering installation-specific FORM routines and for using user exits, which may
and be required and can be used if necessary.
MV45EFZ1
Customer Exits
V05N0001 User Exits for Printing Billing Docs. using POR Procedure
Customer Exits
V50R0004 Calculation of Stock for POs for Shipping Due Date List
V02V0003 User exit for gate + matl staging area determination (headr)
Include Routines
Include Description
MV50AFZK The user exits in this include can be used to fill the condition tables for material
listing and material exclusion (KOMKG and KOMPG) and product selection (KOMKD
and KOMPD) with own data.
MV50AFZL In delivery creation process for sales orders there is the possibility to restrict the delivery
creation to some order items. If these order items are member of a delivery group, but not
all items of this delivery group are includes in the restriction range of the order item nubers,
you can specify in this routine what to do.
MV50AFZP This user exit can be used to modify change mode of pricing screens in delivery processing.
Include Routines
Include Description
MV56AOZZ You can include your own modules in this program, to be processed in shipment processing
screens during PBO.
MV56AIZZ You can include your own modules in this program, to be processed in shipment processing
screens during PAI.
MV56AFZY You can include your own FORM routines in this program. They can contain your own
adjustments for shipment processsing.
MV56AFZZ This program contains pre-defined FORM routines, in which you can carry out your own
adjustments for transportation processing.
USEREXIT_FIELD_MODIFICATION SAPMV61A MV61AFZA You can use this user exit to adjust
the display of individual lines in the
condition
screen by changing the display
attributes of the screen fields. This
does not
include the display of subtotals. This
user exit is also used in order
processing.
USEREXIT_CHANGE_PRICING_RULE SAPMV61A MV61AFZA You can use this user exit to change
the pricing type that has been
predefined in the
copying control table in billing.
USEREXIT_XKOMV_ERGAENZEN_MANU SAPLV61A RV61AFZB You can use this user exit to change
the ready-for-input fields of the
manually entered
condition record in add mode in the
condition screen.
USEREXIT_PRICING_COPY SAPLV61A RV61AFZA You can change the KONV fields for
copied price components.
Note: as of Release 4.6A, the display of the condition screen (screen 6201) has been converted from a full screen to a
subscreen. The full screen is included in the SAPMV61A module pool, the subscreen, however, in program SAPLV69A.
Therefore, instead of MV61AFZA and MV61AFZB, the user exits in LV69AFZZ should be used. For reference, see OSS
note 313569.
EXIT_SAPLV09A_001 You can use this user exit to control whether an address that was entered manually
and has already been used in other documents (referenced), should be referenced
again if it changes or whether a new address shold be created (duplicated).
EXIT_SAPLV09A_002 Call up this user exit if a customer has not been maintained in the current sales area.
EXIT_SAPLV09A_003 Use this user exit to control the origin of partners in the partner determination procedure
(origin X, Y or Z). If X, Y, or Z has been entered in the Origin field, this user exit is automatically
called up during partner determination.
EXIT_SAPLV09A_004 Use this user exit to integrate your own check in a program, that runs before the partner
is saved in the document.
For more detailed information, see the program documentation for each ofthe user exits.
LVKMPFZ1 USER_CREDIT_CHECK1
LVKMPFZ2 USER_CREDIT_CHECK2
LVKMPFZ3 USER_CREDIT_CHECK3
USEREXIT_AVAIL_CHECK_CREDIT MV45AFZF This user exit allows you to determine whether the system
should or should not
User exit Include Description
RVKMPUS2 Using this user exit, you can define new forms of payment guarantee.
BILLING_SCHEDULE_DELTA
For milestone billing a percentage value is fully invoiced for each billing deadline. In the case
of deviations between
the original item value and any later changes, you can use the user exit to determine
whether the difference should
be stored in the final invoice or sent to the next deadline.
USEREXIT_MOVE_FIELD_TO_FPLT : This user exit allows you to create your own fields in
table FPLT.
USEREXIT_MOVE_FIELD_TO_FPLA : This user exit allows you to create your own fields in
table FPLA.
USEREXIT_PRICING_PREPARE_TKOMX
This user exit is used to copy or create an additional field in the definitive communication
structure for pricing.
The user exit is also often used to change the duration of a billing plan deadline. You can do
this by overwriting
the following fields:
tkomp-anz_tage (Number of days in a deadline)
tkomp-anz_monate (Number of months in a deadline)
tkomp-anz_jahre(Number of years in a deadline)
tkomp-anz_wochen (Number of weeks in a deadline)
USEREXIT_DATE_PROPOSAL
In the standard release deadlines are set according to a template in the billing plan. This grid
entry list sets the deadlines
for each day but you can adjust the template with the user exit so that the grid entry list
could, for example, follow a monthly
User exit Include Description
pattern instead.
Modification report for billing plan SDFPLA02
This report enables you to update the header data for a billing plan with the result that new
billing plan deadlines are determined
and set in the billing plan.
In this way you can, for example, set the goods issue date as the starting date for the billing
plan.
Additions to billing plan with transaction SMOD
User exit SDVAX001
In the standard release the billing plan type is determined from the item category of the
sales document and set in the billing plan.
You can also use the user exit to determine the billing plan type dependent on data from the
order header, order item, etc.
User exit V60F0001
This user exit is for changing the deviating billing date (FPLT-AFDAT).
RV60FUS5 This userexit can be used to split date lines TKOMK for Header fields
USEREXIT_PLANT_SELECTION RV03VFZZ The user exits named here are planned for projects that are to
be carried out in agreement
with SAP development as they may only be used in
consultation with SAP. SAP provides no
guarantee if they are used without our advice in program is
an exception to this rule
User exit Include Description
USEREXIT_ADD_FIELD_TO_HEADER FV45VFZZ
USEREXIT_ADD_FIELD_TO_LINE
USEREXIT_DELIVERY_GROUPS FV45VFZY
USEREXIT_MVERF_INIT
USEREXIT_QUOTA_KEY_VALUE
USEREXIT_AVAILABILITY_IN RV03VFZZ This user exit is used to adjust the flow during plant transfer.
USEREXIT_AVAILABILITY_OUT A list of permitted plants, where
USEREXIT_DARA_REFRESH this material is created, is determined and checked in the
USEREXIT_PLANT_SELECTION standard R/3 delivery. A dialog box
appears where you can select the plants. The user exits allow
you to modify the plant table
so that plant selection takes place in advance for every
flagged selection and a dialog box
becomes unnecessary.
USEREXIT_CHECK_VBLB- MV45AFZC These user exits are available for checking customer reserve fields
USR01 from VBLB-USR01 to
USEREXIT_CHECK_VBLB- VBLB-USR05. The reserve fields are used in the component
USR02 supplier industry. The system
USEREXIT_CHECK_VBLB- calls them in the screen flow logic for header data in forecast and
USR03 JIT delivery schedules
USEREXIT_CHECK_VBLB-
USR04
USEREXIT_CHECK_VBLB-
USR05
Function module V450001 is available as an SAP extension for the component supplier industry. It contains the
following user exits:
EXIT_SAPLVED4_004 General - You can use this user exit to overwrite the standard method with which the
system determines the recipient of messages (either at sales document level or in the
customer master record). You can define a special recipient for an incoming document that
has just been processed.
EXIT_SAPLV45L_001 For delivery schedules - The system checks an incoming delivery schedule against the
current/old delivery schedule to determine if there are any differences.
EXIT_SAPLV45L_002 For delivery schedules - With this user exit, you can change the VBLB structure (sales
document: delivery schedule data), before the system copies delivery schedule data to the
corresponding internal table.
EXIT_SAPMV45L_001 Planned delivery schedules - This user exit allows you to process schedule lines generated
automatically in a planning delivery schedule..
EXIT_SAPLVED4_004 General - You can use this user exit to overwrite the standard method with which the
system determines the recipient of messages (either at sales document level or in the
customer master record). You can define a special recipient for an incoming document that
has just been processed.
EXIT_SAPMV45L_002 Planned delivery schedules - This user exit allows you to modify the calendar used in a
delivery schedule split.
EXIT_SAPMV45A_005 For delivery orders (MAIS) - This user exit enables you to control how the system copies
packing proposals into the outbound delivery order.
EXIT_SAPLVED4_001 For delivery orders (MAIS) - These user exits allow you to change the workflow
EXIT_SAPLVED4_002 parameters for processing inbound EDI messages.
EXIT_SAPLVED4_003
EXIT_SAPLVED4_005
EXIT_SAPLVED4_006
EXIT_SAPLVED4_001 For the self-billing procedure - You can use these user exits for the standard self-billing
EXIT_SAPLVED4_005 procedure.
EXIT_SAPLVED4_006
EXIT_SAPLVED5_002 For the self-billing procedure -You can use these user exits for the self-billing procedure
EXIT_SAPLVED5_003 with invoice creation.
EXIT_SAPLVED5_004
RV45HFZZ enhancement
USEREXIT_INV_REQ_ITEM
USEREXIT_INV_REQ_ITEM_PARTNER
You can use the following user exits for resource-related billing as of Release 4.5A:
V46H0001 enhancement
EXIT_SAPLV46H_001
EXIT_SAPLV46H_002User Exits For Billing
The internal number range used in the standard system is specified in the billing type table and can be changed in this
user exit. This user exit is only called when the billing documents is created.
In this user exit additional fields for account determination that are not provided in the standard system are copied into
communication structure KOMKCV (header fields).
USEREXIT_ACCOUNT_PREP_KOMPCV (Module pool SAPLV60A)
In this user exit additional fields for account determination that are not provided in the standard system are copied into
communication structure KOMPCV (item fields).
Depending on the number range, table TVFKD is used to set the billing date (country-specific requirments in Italy).
USEREXIT_NUMBER_RANGE is automatically deactivated when this user exit is being applied.
This user exit is only called when the billing document is created. It is used to provide the header and the item of the
new billing document with deviating or additional data.
USEREXIT_NEWROLE_XVBPAK_AVBPAK
USEREXIT_NEWROLE_XVBPAP_AVBPAK
The following user exits are available in report SAPLV60B for transfer to accounting (function group V60B):
EXIT_SAPLV60B_004: Change a GL account item ACCIT You can add information to a GL account item (such as
quantity specifications) with this exit.
EXIT_SAPLV60B_005: User exit for accruals
Once all relevant data for accruals was entered in the GL account item, you can add to this data with this exit.
EXIT_SAPLV60B_0011: Change the parameter for cash account determination or reconciliation account determination
You can use this exit to change inbound parameters in order to influence account determination. User Exits For
General Billing Interface
With this user exit for the general billing interface, deviating address data for different partner functions can be copied
from the interface.
With this user exit for the general billing interface, new partner functions can be copied from the interface.
With this user exit for the general billing interface, a key field can be added in the aggregrated flow.
Special user exit for the general billing interface with which a key field can be added in the aggregrated flow.
User Exits For Sales Support
In Sales Support, you can use the following SAP enhancements:
MCV2001 - Expand LIS fields for sales activities/sales promotions. This enhancement contains the following user exit:
EXIT_SAPLMCV2_001
V43MLIS - Expand LIS fields for address lists. This enhancement contains the following user exit:
EXIT_SAPLV43M_007
V43K0001 - Enhancement for linking to calendar. This enhancement contains the following user exit:
EXIT_SAPLV43K_001
V43ADATA - Change sales activity data in dialog. This enhancement contains the following user exit:
EXIT_SAPMV43A_007
RVKPRFZ2 This allows the sort sequence for the first issue of the list to be defined.
There are two additional user exits for listing sales documents, which influence the way in which the communication
structure is filled. These user exits do not affect the structure of the list but the way in which the data is transferred and
how the new additional fields are filled.
CUSTOMER_FILL_1
CUSTOMER_FILL_2
sd
Enterprise Structure:
Definition:
1. Financial Accounts: Define company, credit control area, company code, Business area,
Functional area, Maintain Consolidate Business Area, Profit Centre.
2. Controlling: Controlling Area, cost centers, operating concern
3. Logistic General: Define Valuation level,Plant,Location & Division
4. Sales & Distribution: Sales org,Distribution channel, maintain Sales Office & maintain Sales
Group
5. Material Management: Maintain Storage Location & Purchase org
6. Logistic Execution: Define Warehouse, shipping point, maintain Loading group,
Transportation planning point
7. Plant Maintenance: Maintain Plant Maintenance plant
Assignment:
Financial Accounting:
Controlling:
Logistic General:
SD:
Material Management:
Logistics Execution:
2.Financial account-Financial account global setting-fiscal year-assign fiscal year to company code
Billing-Invoice Date, invoice listing date,inco terms,payment terms, credit control area,Account
assignment group,MWST Tax,payment guarantee payment,check(rebate, price determination)
Material Master:MM01/MM02/MM03
Basic data1:Base unit of measure, Division, product allocation,X-plant material status,Item category
group, Gross weight,Net weight, Material group pack material.
MRP1: MRP type, MRP Controller, MRP group, Lot size, Max lot size
Inquiry:VA11
Quotation:VA21
Sales order:VA01
Scheduling Agreement-VA31
Contract-VA41
Back order-V_RA(SD),CO06(Material)
Rescheduling-V_V2
Eassy access-Logistics-SD-Sales-Inquiry/Quotation/Order
Pricing:
Condition record:VK11
Condition type:V/06
Exclusion group:
Condition supplement:
Condition scale:
Pricing scale:
Minimum order:
Group condition:
Basic Functions:
.Account determination:
Define acount assignment group for customer and material: IMG-SD-Basic functions-account
assignment/costing-Define materila account group,
Create table:01,02,03,04,05
Assign GL accounts:VKOA
Route determination:
Output determination:
T.code:NACE=Output control(V1-sales,V2-Delivery,V3-Billing)
NAST=Output table
Text Determination:
Copy Control:VOFM
IMG-SD-sales-sales documents-Maintain copy control for sales documents:Header, item & schedule
line
Incompletion Log:
Above structure: Item category:ERLA, item category: TAQ(Header level),TAE(sub item), delivery and
billing carried at header level,sub item treated as text item
Below structure:item category :LUMF, item category: TAP(header level),TAN(sub item),delivery and
billing carried at sub item, header item is text item.
Material determination:
Define condition table, access sequence, define condition types (A001),define material
determination procedure(A00001)
XD02: check item proposal check box in customer master sales area section
Logistics-SD_Master data-products-Listing/Exclusion:VB01
Cross selling:
Customer Material Info Records: VD51: customer place the order with own material code, we can
create CMIR.
Credit Management:SD+FI
FD32:
Define Groups:
Define automatic credit control: OVA8: Credit control area+risk category+credit group
Transfer or Requirement:SD+MM+PP
Availability check:SD+MM+PP+CO