Registring SAP 4.0B in SDL
Hi Everybody.
Till now, I registered my SAP Systems (ECC 5.0, BW 3.5, etc.) in SLD using RZ70, like in Michal's blog /people/michal.krawczyk2/blog/2005/03/10/registering-a-new-technical-system-in-sld--abap-based
Now, I have to register an old SAP 4.0B System and according to BASIS team tcode RZ70 doesnt exist in SAP 4.0B.
Is there any other similiar tcode in SAP 4.0B ? Will I have to register the system in SLD by myself (by hands)?
thanks in advance
These links might help:
Tech System in SLD and RZ70 in 4.6c and 4.7 systems
How do I connect an old R/3 4.0B system to my SLD?
Thanks,
-Russ
Similar Messages
-
Hi everybody ,
We need the Discount to be calculated automatically on the Total Order Value.
Its a promotion.
Useful suggestions will be rewarded.
Thanks
KartikHi pls follow the procedure below, Hope it will help u out
VOFM: ON PRICING
This note is an explanation of function "Maintain: Requirements and Formulas", which is also known as "VOFM".
By using descriptions and examples, this note explains how the VOFM function works in the R/3 Standard System, which objects are related to it and which restrictions exist.
Chapter 2.7 explains possible causes of errors and solutions for problems with the VOFM function.
To provide a good overview, this note is subdivided into the following sub areas:
1. General information
1.1 Definition of terms
1.2 Application areas
1.3 A frank word on the "source code responsibility"
2. Technology
2.1 Introduction
2.2 Namespaces
2.2.1 SSCR object registration
2.3 Structure of a VOFM object
2.3.1 Include file with ABAP form routine
2.3.2 Table entries in TFRM and TFRMT
2.4 Calling VOFM objects
2.4.1 VOFM object carrier
2.5 Activation, generation and RV80HGEN
2.6 Transport
2.7 FAQs: Possible causes of errors and problems
Technical field names are displayed in angle brackets [].
Note that this note only explains the mode of operation of the VOFM in an R/3 Standard Core System.
For R/3 industry solutions or Add-Ons the VOFM function displays a different behavior in subareas, however, this is not dealt with in this note.
Additional key words
VOFM, SAPMV80H, TFRM, TFRMT, RV80HGEN, XPRA, formulas, requirements, data transport routine, copy routine, data transfer.
Cause and prerequisites
1. General information
1.1 Definition of terms
Depending on the business processes used it may be necessary to influence the standard behavior of R/3 applications. For that purpose the VOFM function provides a corresponding environment in order to be able to develop and manage customer-specific logic simply.
The system stores the objects generated via the VOFM in the Customizing of the respective application area
(Pricing, message determination and so on) and its programs call the objects correspondingly.
Also SAP delivers certain functions in the form of VOFM objects.
Consequently, the VOFM is an exit technology as explained in more detail in Note 381348.
1.2 Application areas
Typical VOFM objects are requirements, formulas and data transfer routines.
These are used in processes of the purchase order, the delivery, billing, price determination, material determination, message determination, the free goods, the pricing and of others.
In the entries of the R/3 core menu of Transaction VOFM you can find a precise overview of the supported application areas.
1.3 A frank word on the "source code responsibility"
As in user exits, in VOFM objects are many fields and tables available. Thus, the use of VOFM objects is very versatile and consequently also very critical under certain circumstances. For the use of "customer-specific" VOFM objects the statements in Note 381348 regarding the responsibility for customer enhancements (Maintenance responsibility, problems during the upgrade and so on) apply. Read this note carefully before you decide on the use of customer-specific VOFM objects.
Errors and data inconsistencies that are caused by improper application or implementation of VOFM objects are not processed by the SAP Support but exclusively within the framework of the Consulting that has to be purchased separately.
2. Technology
2.1 Introduction
A VOFM object is uniquely defined via characteristics "group indicator" [GRPZE] and "group number" [GRPNO].
Here the group indicator, technically represented by a character field of length 4, is the logical connection to the calling environment.
Examples:
ABED copying requirement in the order
ADAT data transfer in the order
PBED requirements pricing
CASC Data transfer for sales activities
PBEK requirements account determination
CHRG requirements batches
REAK archiving for orders
VFCL Multi-dimensional scales
You can find all defined group indicators in the allowed values of the "GRPZE" domain in the ABAP Dictionary (Transaction SE11).
The group number can have a value from 1 to 999.
Exceptions are group indicators "PSTK" (= group key routine pricing) and "TDAT" (= data transfer for texts). For these the system can only assign group numbers from 1 to 99.
2.2 Namespaces
The VOFM has separate number ranges in order to distinguish VOFM objects delivered by SAP from customer-specific VOFM objects. These number ranges are often also called "VOFM namespaces".
However, note that this is not a "real namespace" that is protected by corresponding entries in system table "TRESC" (= reserved names for Customizing tables and Customizing objects).
Instead, only the VOFM logic itself does the definition and check of the number ranges.
The following list displays the customer number ranges sorted according to group indicators:
Indicator Name Number range customer
FOFU Subsequent functions 900 - 999
PSTK Group key routines 50 - 99
TDAT Data transfer routines f. texts 50 - 99
all other group indicators 600 - 999
In Note 356737 you can find more information on the available VOFM number ranges.
2.2.1 SSCR object registration
VOFM objects are subject to SSCR registration (= SAP Software Change Registration).
The reason for that is the necessity that every VOFM object is physically assigned to that SAP development class, from whose programs a corresponding jump into the VOFM object later occurs.
If you use the VOFM interface the system makes the assignment automatically. An assignment of customer-specific development classes is not possible.
2.3 Structure of a VOFM object
A VOFM object consists of the following parts:
Include file with ABAP form routine
TFRM table entry
TFRMT table entry
2.3.1 Include file with ABAP form routine
In the ABAP form routine the desired function is programmed.
Example pricing value formula number 001:
Include name : FV64A001
Form routine : FRM_KONDI_WERT_001
Implementation: * * Profit margin considering rebate agreements
form frm_kondi_wert_001.
xkwert = komp-kzwi3 - komp-wavwr.
endform.
Dependending on the selected group indicator, the group number and the system type (SAP or customer system), the system assigns and generates the include name and form routine name automatically.
For this reason, standard routines delivered by SAP generally have a different structure of the include name than customer-specific routines.
Example:
SAP standard value formula for the pricing
=> prefix FV64A + object number with 3 places from 'SAP namespace'
=> for example FV64A001
Customer-specific value formula for the pricing
=> prefix RV64A + object number with 3 places from 'customer namespace'
=> for example RV64A905
2.3.2 Table entries in TFRM and TFRMT
The entries in tables TFRM and TFRMT belonging to a VOFM object are used for the status management and assignment. The system always analyzes them if the user calls Transaction VOFM or if a generation operation occurs (for details refer to section 2.5).
The system generates exactly one TFRM table entry per VOFM OBjekt. In this TFRM entry the following information is stored:
Group indicator GRPZE
Group number GRPNO
Routine 'active' indicator AKTIV_TFRM
Application KAPPL
Date of the last generation GNDAT
Time of the last generation GNZEI
Examples:
GRPZE GRPNE AKTIV_TFRM KAPPL GNDAT GNZEI
PBED 001 X V 06 13 2001 09 06 39
TDAT 001 X 06 13 2001 09 06 39
CHRG 003 X 06 13 2001 09 06 39
The meaning of group indicators and group numbers has already been dealt with.
The 'active indicator' controls whether a VOFM object is 'active' or 'inactive'. Active VOFM objects have characteristic value AKTIV_TFRM = 'X', inactive objects have characteristic value AKTIV_TFRM = initial.
VOFM objects flagged as 'active' are 'known' to the calling program logic, that means they were included in the main program of the 'calling program' and can thus be addressed and
processed during the runtime.
You cannot delete VOFM objects that are still 'active'. In this case you have to reset the active indicator manually before.
The content of the 'Application' field serves to filter the relevant VOFM objects in various display functions and Customizing functions.
Example: Condition value formula 010 'Relevant Price'. This formula has characteristic value 'MS' for the 'Application' field (= External Services Management purchasing). Therefore the object is not open for selection in the input help during the maintenance of pricing procedure SD (Transaction V/08), because this is a Customizing transaction assigned to application 'V' (= Sales and Distribution).
Storing an application key is optional.
The generation date and the generation time record the time of the last registration of the VOFM object (the object carrier, refer to section 2.4.1).
In addition to the respective TFRM entry a VOFM object can have 'n' entries in table TFRMT. The entries are used for the storage of language-dependent object descriptions, which are structured as follows:
- Language key [SPRAS]
- Group indicator [GRPZE]
- Group number [GRPNO]
- Description [BEZEI]
Examples:
SPRAS GRPZE GRPNO BEZEI
D PBED 001 Regulierer abweich
E PBED 001 Different payer
The system supplies the language key automatically with the logon language of the user during the creation of a new VOFM object.
The length of the object description is limited to 20 characters.
Important! A VOFM object is only consistent if both the Include file with ABAP form routine and a corresponding TFRM table entry exist. Entries in table TFRMT are optional.
2.4 Calling VOFM objects
As mentioned above, VOFM objects are called directly by the application logic of R/3 standard programs. Technically this is implemented by ABAP statement 'PERFORM ... IN PROGRAM'. With the aid of this statement you can specify both the name of the subroutine and the main program dynamically (during the runtime).
Example: Call of a condition value formula from the pricing
if xkomv-kofrm ne 0. <<< formula reference existing?
xkwert = xkomv-kwert. <<< act. value in work variable
frm_kondi_wert-nr = xkomv-kofrm. <<< set up object names
perform (frm_kondi_wert) in program saplv61a if found. <<<CALL
xkomv-kwert = xkwert. <<
endif.
In the example above the subroutine is determined by the contents of variable 'FRM_KONDI_WERT'; the main program, which is to be searched for the form routine, is SAPLV61A.
If the called routine is not known in the main program, a program termination with the title 'PERFORM_NOT_FOUND' occurs.
Therefore some users of the VOFM technology call ABAP statement 'PERFORM ... IN PROGRAM' together with the addition 'IF FOUND', which has the effect that a jump into the form routine is only executed if this in fact exists in the main program. This does indeed prevent a program termination, however, the result of the overall process may deviate from the
result expected by the user, because in this case the system does not execute the source code implemented in the VOFM object.
2.4.1 VOFM 'object carrier'
Object carriers are required to make a VOFM object 'known' in the main program of the calling program (refer to section 2.4). The object carrier is integrated in the main program of the calling program as an independent include (for example SAPLV61A, SAPMV45A and so on).
Example: Inclusion of object carriers for word processing in SD
documents; Program 'SAPLV45T'
System-defined Include-files. *
INCLUDE LV45TTOP. "Global Data
INCLUDE LV45TDEF.
INCLUDE LV45TUXX. "Function Modules
INCLUDE LV45TNNN. <<< 'carrier' copy requirements for texts
INCLUDE LV45TENN. <<< 'carrier' copy routines for texts
Every active VOFM object (for an explanation on the active indicator refer to section 2.3.2) must be registered in the 'carrier'.
The system writes standard VOFM objects delivered by SAP directly into the 'carrier', VOFM objects from the number range reserved for customers (refer to section 2.2 'Namespaces') are sorted into a 'sub-include' included in the carrier.
Exactly one carrier exists per group indicator. The names of all defined object carriers are hard-coded in program MV80HF0A, form routine 'AKTIVIEREN_TRAEGER_SETZEN'.
Here the names of the sub-include for customer-specific VOFM objects belonging to the main carrier are also defined.
Example: Carrier object 'FV63ANNN' for the registration of condition basis formulas in the pricing (Program SAPLV61A)
FV63ANNN
<<< main
carrier-include
|-INCLUDE RV63ANNN. "User-Routinen <<< sub-include customer objects
| |- INCLUDE RV63A910. "Customer specific
| |- INCLUDE RV63A911. "Customer specific
| |- INCLUDE RV63A912. "Customer specific
| |- ...
|- INCLUDE FV63A001. "Volume
|- INCLUDE FV63A002. "Net value
|- INCLUDE FV63A003. "Net Price
|- INCLUDE FV63A004. "Net Value Plus Tax
|- INCLUDE FV63A005. "KZWI1
|- ...
Because the content of the VOFM object carriers is automatically created source code, you should avoid manual changes to them.
SAP notes, which suggest manual changes to the object carriers, are therefore also incorrect. However, if you nevertheless receive such a note to solve a problem, contact the SAP
Support with a reference to this note.
2.5 Activation, generation and RV80HGEN
The 'activation' is the inclusion of an VOFM object in an object carrier. A 'deactivation' results in the removal of the VOFM object from the object carrier.
The overall process for the creation of a current object carrier is often called 'generation'.
Generally the activation or generation fall into three types.
- Individual activation
- Collective activation
- Generation of object carriers via report RV80HGEN
The 'individual activation' causes the registration of an individual VOFM object in the corresponding object carrier. Which object carrier is relevant is determined with the aid of the group indicator and the group number. In addition to the entry of the VOFM object in the object carrier the system writes the date and time of the generation into table TFRM (refer also to section 2.3.2).
You can start the individual activation only manually. It is always always executed when a user selects a line within the VOFM editing interfaces and afterwards selects activity
'Activate' from the 'Edit' menu.
The 'collective activation' causes the registration of all VOFM objects that belong to a certain group indicator. Analog to the individual activation the system determines the relevant object carrier automatically and writes date and time into table TFRM. The 'collective activation' is a process which you can start also only manually. For this purpose, choose activity
'Activate all' from the 'Edit' menu.
During the generation via report RV80HGEN the system sets up the object carriers of all defined group indicators again. However, the system includes only those VOFM objects that have set the 'active' indicator in the corresponding TFRM table entry. Nonactive VOFM objects are not included in object carriers during the generation via report RV80HGEN.
Due to the quantity of the data to be processed,
the generation via RV80HGEN can take between 0,5 and >5 minutes (depending on the system and the constellation).
Because the RV80HGEN is defined as 'XPRA', it is executed automatically during a system upgrade.
You can also use this XPRA feature for the transport of VOFM objects in order to implement an automatic update of the object carriers after the import of VOFM objects into the target system (section 2.6 provides more details on the transport).
Both the collective activation and the activation via report RV80HGEN technically revert to the program components of the individual activation. For the separate control of the individual activation types form routine AKTIVIEREN_EINZELN (Include MV80HF0A) has a 'USING' parameter, which can have the following characteristic values:
'E' Activate individually
'A' Activate all (= collective activation)
' ' Deactivate individually
During the generation via RV80HGEN the system executes a collective activation for every group indicator sequentially, that means a call of form routine
AKTIVIEREN_EINZELN with characteristic value 'A'.
2.6 Transport
If you want to transfer VOFM objects from one system (= source) into another system (= target), this is generally made with an object transport.
As of Release 4.0, the VOFM function has a connection to the SAP 'Change and Transport System' (CTS) in order to simplify the transfer process for the user.
By the transport connection the system automatically adds newly created or changed VOFM objects to the object list of a transport request which was selected by the user before.
All steps necessary for the execution of a VOFM transport are described in detail in Note 22808 'Transferring formulas'. Note that steps 1-4 are only needed
if the VOFM maintenance environment providesno automatic connection to the transport system or if you want to combine a transport request manually. In any case you must execute step 5, regardless of how the transport request was created.
In addition to Note 22808, Note 385067 contains an overview for releases >= 4.6C regarding which sorts of tasks and object entries are required in a
transport request (depending on the activity carried out (create/change/activate/deactivate/delete)) in order to transport a VOFM object successfully. -
Hello folks
Am going to my first CIN Implementation.
I would be greatful if you people can tell me what all details i have to collect from the client from MM point of view and the sequence in which the configurations to be done.
Also please help me with the tips and points to be remembered at the time of implementation.
Any helpful inputs are appreciated.
regards to all
Sindhyahi,
***CIN CONFUGURATION***
1.1 Maintain Excise Registration
SAPSPRO Basic setting>India-> tax on Goods Movements>Logistics general >Ref. IMG Maintain Excise Registrations>
APPLICABLE
1.2 Maintain Company Code Settings
tax on Good-> Logistics general -- SAP Ref. IMG SPRO Maintain Company Code Basic setting --India --Movements Settings
APPLICABLE
1.3 Maintain Plant Settings
SAP Ref.--SPRO -- Basic setting --India -- tax on Goods Movements-- Logistics general ---IMG Maintain Plant Settings
APPLICABLE
1.4 Maintain Excise Groups
SPRO Basic--India -- tax on Goods Movements-- Logistics general -- SAP Ref. IMG - Maintain Excise Groupssetting
APPLICABLE
1.5 Maintain Series Groups
India -tax on Goods MovementsLogistics general -SAP Ref. IMG -SPRO Maintain Series Groups--Basic setting
APPLICABLE
1.6 Maintain Excise Duty Indicators
tax on Goods---- Logistics general -SAP Ref. IMG -SPRO Maintain Excise Duty-Basic setting -
India -
Movements Indicators
APPLICABLE
1.7 Maintain Sub transaction Type with Text
India tax on Goods Movements Logistics general SAP Ref. IMG SPRO Maintain Sub transaction Type with TextBasic setting
APPLICABLE
1.8 Determination of Excise Duty
tax Logistics general SAP Ref. IMG SPRO Select Tax Calculation Determination of Excise DutyIndia on Goods Movements Procedure
APPLICABLE
1.9 Maintain Excise Defaults
SAP Ref.SPRO Determination of ExciseIndia tax on Goods Movements Logistics general IMG Maintain Excise DefaultsDuty
APPLICABLE
1.10 Condition-Based Excise Determination
tax on Goods Logistics general SAP Ref. IMG SPRO Define Tax Code for Condition-Based Excise DeterminationIndia Movements Purchasing Documents
APPLICABLE
1.11 Condition-Based Excise Determination
tax on Goods Logistics general SAP Ref. IMG SPRO Assign Tax Code to Condition-Based Excise DeterminationIndia Movements Company Codes
APPLICABLE
1.12 Classify Condition Types
SAPSPRO Condition-BasedIndia tax on Goods Movements Logistics general Ref. IMG Classify Condition TypesExcise Determination
APPLICABLE
1.13 Maintain Chapter IDs
tax on Goods Logistics general SAP Ref. IMG SPRO Maintain Chapter ids Master dataIndia Movements
APPLICABLE
1.14 Assign Users to Material Master Screen Sequence for Excise Duty
SPRO Master dataIndia tax on Goods Movements Logistics general SAP Ref. IMG Assign Users to Material Master Screen Sequence for Excise Duty
APPLICABLE
1.15 Specify Excise Accounts per Excise Transaction
tax on Goods Logistics general SAP Ref. IMG SPRO Specify Excise Accounts per Excise Account determinationIndia Movements Transaction
APPLICABLE
1.16 Specify G/L Accounts per Excise Transaction
tax on Goods Logistics general SAP Ref. IMG SPRO Specify G/L Accounts per Excise Account determinationIndia Movements Transaction
APPLICABLE
1.17 Incoming Excise Invoices
SAPSPRO BusinessIndia tax on Goods Movements Logistics general Ref. IMG Incoming Excise InvoicesTransactions
APPLICABLE
1.18 Define Processing Modes Per Transaction
Logistics general SAP Ref. IMG SPRO Define Processing Modes Business TransactionsIndia tax on Goods Movements Per Transaction
APPLICABLE
1.19 Define Reference Documents Per Transaction
tax on Goods Logistics general SAP Ref. IMG SPRO Define Reference Documents Per Business TransactionsIndia Movements Transaction
APPLICABLE
1.20 Maintain Rejection Codes
SAPSPRO BusinessIndia tax on Goods Movements Logistics general Ref. IMG Maintain Rejection CodesTransactions
APPLICABLE
1.21 Specify Which Movement Types Involve Excise Invoices
Logistics SAP Ref. IMG SPRO Specify Which Business TransactionsIndia tax on Goods Movementsgeneral Movement Types Involve Excise Invoices
APPLICABLE
1.22 Outgoing Excise Invoices
tax on Goods Logistics general SAP Ref. IMG SPRO Assign Outgoing Excise Invoices Business TransactionsIndia Movements Billing Types to Delivery Types
APPLICABLE
1.23 Maintain Default Excise Groups and Series Groups
Logistics general SAP Ref. IMG SPRO Outgoing Excise Invoices Business TransactionsIndia tax on Goods Movements Maintain Default Excise Groups and Series Groups
APPLICABLE
1.24 Subcontracting Attributes
tax on Logistics general SAP Ref. IMG SPRO Subcontracting Subcontracting Business TransactionsIndia Goods Movements Attributes
APPLICABLE
1.25 Maintain Movement Type Groups
SPRO BusinessIndia tax on Goods Movements Logistics general SAP Ref. IMG Subcontracting SubcontractingTransactions Attributes
APPLICABLE
1.26 Utilization Determination
SAPSPRO BusinessIndia tax on Goods Movements Logistics general Ref. IMG Utilization UtilizationTransactions Determination
APPLICABLE
1.27 Specify SAP script Forms
SPRO BusinessIndia tax on Goods Movements Logistics general SAP Ref. IMG Specify SAP script Excise RegistersTransactions Forms
APPLICABLE
1.28 Number Ranges
SAP Ref. IMG SPRO Number ToolsIndia tax on Goods MovementsLogistics general Ranges
APPLICABLE
1.29 Message Control
SAP Ref. IMG SPRO Message ToolsIndia tax on Goods MovementsLogistics general Control
APPLICABLE
Hope it helps...
Regards
Priyanka.P -
Hi Folks,
I am working on requirements.
I am a bit new to this process.I wud like to have some detailed info on the same.Please clarify the below mentioned.
1.I've seen Requirements in VOFM only for some areas..like output control,pricing,material determination etc. <b>what is the working mechanism</b> of this? How is it different from USER EXITS?
2.The same piece of code appears twice in the same requirement under to differnet form definitions,namely form KOMBD and KOMBV ? <b>why this is required twice</b>?
3.why do we need to run <b>RV80HGEN</b> after creating a requirement?
4.From where the number series starts for newly defined routines apart from standard requirements?
5.If we want to modify the standard exist <b>what are the precaution to take?</b> what i heard is ..once we give the access key for it...there is some icons apper on tool bar like INSERT DELETE etc..
Your help is appreciated.
Thanks
RajaHello Raja,
As indicated only for the following as indicated number range is allowed for rest it is 600-999.
Name Number
Subsequent functions 900 - 999
Group key routines 50 - 99
Data transfer routines f. texts 50 - 99
<b></b>all other group indicators 600 - 999
<b></b>
I am attaching another note which deals with VOFM problem. Keep this with u as it will prove useful.
<b></b> SAP Note 327220<b></b>
This note is an explanation of function "Maintain: Requirements and Formulas", which is also known as "VOFM".
By using descriptions and examples, this note explains how the VOFM function works in the R/3 Standard System, which objects are related to it and which restrictions exist.
Chapter 2.7 explains possible causes of errors and solutions for problems with the VOFM function.
To provide a good overview, this note is subdivided into the following subareas:
1. General information
1.1 Definition of terms
1.2 Application areas
1.3 A frank word on the "source code responsibility"
2. Technology
2.1 Introduction
2.2 Namespaces
2.2.1 SSCR object registration
2.3 Structure of a VOFM object
2.3.1 Include file with ABAP form routine
2.3.2 Table entries in TFRM and TFRMT
2.4 Calling VOFM objects
2.4.1 VOFM object carrier
2.5 Activation, generation and RV80HGEN
2.6 Transport
2.7 FAQs: Possible causes of errors and problems
Technical field names are displayed in angle brackets [].
Note that this note only explains the mode of operation of the VOFM in an R/3 Standard Core System. For R/3 industry solutions or Add-Ons the VOFM function displays a different behavior in subareas, however, this is not dealt with in this note.
Additional key words
VOFM, SAPMV80H, TFRM, TFRMT, RV80HGEN, XPRA, formulas, requirements, data transport routine, copy routine, data transfer.
Cause and prerequisites
1. General information
1.1 Definition of terms
Depending on the business processes used it may be necessary to influence the standard behavior of R/3 applications. For that purpose the VOFM function provides a corresponding environment in order to be able to develop and manage customer-specific logic simply.
The system stores the objects generated via the VOFM in the Customizing of the respective application area (Pricing, message determination and so on) and its programs call the objects correspondingly.
Also SAP delivers certain functions in the form of VOFM objects.
Consequently, the VOFM is an exit technology as explained in more detail in Note 381348.
1.2 Application areas
Typical VOFM objects are requirements, formulas and data transfer routines.
These are used in processes of the purchase order, the delivery, billing, price determination, material determination, message determination, the free goods, the pricing and of others.
In the entries of the R/3 core menu of Transaction VOFM you can find a precise overview of the supported application areas.
1.3 A frank word on the "source code responsibility"
As in user exits, in VOFM objects are many fields and tables available. Thus, the use of VOFM objects is very versatile and consequently also very critical under certain circumstances. For the use of "customer-specific" VOFM objects the statements in Note 381348 regarding the responsibility for customer enhancements (Maintenance responsibility, problems during the upgrade and so on) apply. Read this note carefully before you decide on the use of customer-specific VOFM objects. Errors and data inconsistencies that are caused by improper application or implementation of VOFM objects are not processed by the SAP Support but exclusively within the framework of the Consulting that has to be purchased separately.
2. Technology
2.1 Introduction
A VOFM object is uniquely defined via characteristics "group indicator" [GRPZE] and "group number" [GRPNO].
Here the group indicator, technically represented by a character field of length 4, is the logical connection to the calling environment.
Examples:
ABED copying requirement in the order
ADAT data transfer in the order
PBED requirements pricing
CASC Data transfer for sales activities
PBEK requirements account determination
CHRG requirements batches
REAK archiving for orders
VFCL Multi-dimensional scales
You can find all defined group indicators in the allowed values of the "GRPZE" domain in the ABAP Dictionary (Transaction SE11).
The group number can have a value from 1 to 999.
Exceptions are group indicators "PSTK" (= group key routine pricing) and "TDAT" (= data transfer for texts). For these the system can only assign group numbers from 1 to 99.
2.2 Namespaces
The VOFM has separate number ranges in order to distinguish VOFM objects delivered by SAP from customer-specific VOFM objects. These number ranges are often also called "VOFM namespaces".
However, note that this is not a "real namespace" that is protected by corresponding entries in system table "TRESC" (= reserved names for Customizing tables and Customizing objects). Instead, only the VOFM logic itself does the definition and check of the number ranges.
The following list displays the customer number ranges sorted according to group indicators:
Indicator Name Number range customer
FOFU Subsequent functions 900 - 999
PSTK Group key routines 50 - 99
TDAT Data transfer routines f. texts 50 - 99
all other group indicators 600 - 999
In Note 356737 you can find more information on the available VOFM number ranges.
2.2.1 SSCR object registration
VOFM objects are subject to SSCR registration (= SAP Software Change Registration).
The reason for that is the necessity that every VOFM object is physically assigned to that SAP development class, from whose programs a corresponding jump into the VOFM object later occurs.
If you use the VOFM interface the system makes the assignment automatically. An assignment of customer-specific development classes is not possible.
2.3 Structure of a VOFM object
A VOFM object consists of the following parts:
Include file with ABAP form routine
TFRM table entry
TFRMT table entry
2.3.1 Include file with ABAP form routine
In the ABAP form routine the desired function is programmed.
Example pricing value formula number 001:
Include name : FV64A001
Form routine : FRM_KONDI_WERT_001
Implementation: * * Profit margin considering rebate agreements
form frm_kondi_wert_001.
xkwert = komp-kzwi3 - komp-wavwr.
endform.
Dependending on the selected group indicator, the group number and the system type (SAP or customer system), the system assigns and generates the include name and form routine name automatically.
For this reason, standard routines delivered by SAP generally have a different structure of the include name than customer-specific routines.
Example:
SAP standard value formula for the pricing
=> prefix FV64A + object number with 3 places from 'SAP namespace'
=> for example FV64A001
Customer-specific value formula for the pricing
=> prefix RV64A + object number with 3 places from 'customer namespace'
=> for example RV64A905
2.3.2 Table entries in TFRM and TFRMT
The entries in tables TFRM and TFRMT belonging to a VOFM object are used for the status management and assignment. The system always analyzes them if the user calls Transaction VOFM or if a generation operation occurs (for details refer to section 2.5).
The system generates exactly one TFRM table entry per VOFM OBjekt. In this TFRM entry the following information is stored:
- Group indicator [GRPZE]
- Group number [GRPNO]
- Routine 'active' indicator [AKTIV_TFRM]
- Application [KAPPL]
- Date of the last generation [GNDAT]
- Time of the last generation [GNZEI]
Examples: GRPZE GRPNE AKTIV_TFRM KAPPL GNDAT GNZEI
PBED 001 X V 06/13/2001 09:06:39
TDAT 001 X 06/13/2001 09:06:39
CHRG 003 X 06/13/2001 09:06:39
The meaning of group indicators and group numbers has already been dealt with.
The 'active indicator' controls whether a VOFM object is 'active' or 'inactive'. Active VOFM objects have characteristic value AKTIV_TFRM = 'X', inactive objects have characteristic value AKTIV_TFRM = initial.
VOFM objects flagged as 'active' are 'known' to the calling program logic, that means they were included in the main program of the 'calling program' and can thus be addressed and processed during the runtime.
You cannot delete VOFM objects that are still 'active'. In this case you have to reset the active indicator manually before.
The content of the 'Application' field serves to filter the relevant VOFM objects in various display functions and Customizing functions.
Example: Condition value formula 010 'Relevant Price'. This formula has characteristic value 'MS' for the 'Application' field (= External Services Management purchasing). Therefore the object is not open for selection in the input help during the maintenance of pricing procedure SD (Transaction V/08), because this is a Customizing transaction assigned to application 'V' (= Sales and Distribution). Storing an application key is optional.
The generation date and the generation time record the time of the last registration of the VOFM object (the object carrier, refer to section 2.4.1).
In addition to the respective TFRM entry a VOFM object can have 'n' entries in table TFRMT. The entries are used for the storage of language-dependent object descriptions, which are structured as follows:
- Language key [SPRAS]
- Group indicator [GRPZE]
- Group number [GRPNO]
- Description [BEZEI]
Examples: SPRAS GRPZE GRPNO BEZEI
D PBED 001 Regulierer abweich.
E PBED 001 Different payer
The system supplies the language key automatically with the logon language of the user during the creation of a new VOFM object.
The length of the object description is limited to 20 characters.
Important! A VOFM object is only consistent if both the Include file with ABAP form routine and a corresponding TFRM table entry exist. Entries in table TFRMT are optional.
2.4 Calling VOFM objects
As mentioned above, VOFM objects are called directly by the application logic of R/3 standard programs. Technically this is implemented by ABAP statement 'PERFORM ... IN PROGRAM'. With the aid of this statement you can specify both the name of the subroutine and the main program dynamically (during the runtime).
Example: Call of a condition value formula from the pricing
if xkomv-kofrm ne 0. <<< formula reference existing?
xkwert = xkomv-kwert. <<< act. value in work variable
frm_kondi_wert-nr = xkomv-kofrm. <<< set up object names
perform (frm_kondi_wert) in program saplv61a if found. <<<call
xkomv-kwert = xkwert. <<<result value assignment
endif.
In the example above the subroutine is determined by the contents of variable 'FRM_KONDI_WERT'; the main program, which is to be searched for the form routine, is SAPLV61A.
If the called routine is not known in the main program, a program termination with the title 'PERFORM_NOT_FOUND' occurs. Therefore some users of the VOFM technology call ABAP statement 'PERFORM ... IN PROGRAM' together with the addition 'IF FOUND', which has the effect that a jump into the form routine is only executed if this in fact exists in the main program. This does indeed prevent a program termination, however, the result of the overall process may deviate from the result expected by the user, because in this case the system does not execute the source code implemented in the VOFM object.
2.4.1 VOFM 'object carrier'
Object carriers are required to make a VOFM object 'known' in the main program of the calling program (refer to section 2.4). The object carrier is integrated in the main program of the calling program as an independent include (for example SAPLV61A, SAPMV45A and so on).
Example: Inclusion of object carriers for word processing in SD
documents; Program 'SAPLV45T'
System-defined Include-files. *
INCLUDE LV45TTOP. "Global Data
INCLUDE LV45TDEF.
INCLUDE LV45TUXX. "Function Modules
INCLUDE LV45TNNN. <<< 'carrier' copy requirements for texts
INCLUDE LV45TENN. <<< 'carrier' copy routines for texts
Every active VOFM object (for an explanation on the active indicator refer to section 2.3.2) must be registered in the 'carrier'. The system writes standard VOFM objects delivered by SAP directly into the 'carrier', VOFM objects from the number range reserved for customers (refer to section 2.2 'Namespaces') are sorted into a 'sub-include' included in the carrier.
Exactly one carrier exists per group indicator. The names of all defined object carriers are hard-coded in program MV80HF0A, form routine 'AKTIVIEREN_TRAEGER_SETZEN'. Here the names of the sub-include for customer-specific VOFM objects belonging to the main carrier are also defined.
Example: Carrier object 'FV63ANNN' for the registration of condition basis formulas in the pricing (Program SAPLV61A)
FV63ANNN
<<< main
carrier-include
|-INCLUDE RV63ANNN. "User-Routinen <<< sub-include customer objects
| |- INCLUDE RV63A910. "Customer specific
| |- INCLUDE RV63A911. "Customer specific
| |- INCLUDE RV63A912. "Customer specific
| |- ...
|- INCLUDE FV63A001. "Volume
|- INCLUDE FV63A002. "Net value
|- INCLUDE FV63A003. "Net Price
|- INCLUDE FV63A004. "Net Value Plus Tax
|- INCLUDE FV63A005. "KZWI1
|- ...
Because the content of the VOFM object carriers is automatically created source code, you should avoid manual changes to them.
SAP notes, which suggest manual changes to the object carriers, are therefore also incorrect. However, if you nevertheless receive such a note to solve a problem, contact the SAP Support with a reference to this note.
2.5 Activation, generation and RV80HGEN
The 'activation' is the inclusion of an VOFM object in an object carrier. A 'deactivation' results in the removal of the VOFM object from the object carrier. The overall process for the creation of a current object carrier is often called 'generation'.
Generally the activation or generation fall into three types.
- Individual activation
- Collective activation
- Generation of object carriers via report RV80HGEN
The 'individual activation' causes the registration of an individual VOFM object in the corresponding object carrier. Which object carrier is relevant is determined with the aid of the group indicator and the group number. In addition to the entry of the VOFM object in the object carrier the system writes the date and time of the generation into table TFRM (refer also to section 2.3.2).
You can start the individual activation only manually. It is always always executed when a user selects a line within the VOFM editing interfaces and afterwards selects activity 'Activate' from the 'Edit' menu.
The 'collective activation' causes the registration of all VOFM objects that belong to a certain group indicator. Analog to the individual activation the system determines the relevant object carrier automatically and writes date and time into table TFRM. The 'collective activation' is a process which you can start also only manually. For this purpose, choose activity 'Activate all' from the 'Edit' menu.
During the generation via report RV80HGEN the system sets up the object carriers of all defined group indicators again. However, the system includes only those VOFM objects that have set the 'active' indicator in the corresponding TFRM table entry. Nonactive VOFM objects are not included in object carriers during the generation via report RV80HGEN. Due to the quantity of the data to be processed, the generation via RV80HGEN can take between 0,5 and >5 minutes (depending on the system and the constellation).
Because the RV80HGEN is defined as 'XPRA', it is executed automatically during a system upgrade.
You can also use this XPRA feature for the transport of VOFM objects in order to implement an automatic update of the object carriers after the import of VOFM objects into the target system (section 2.6 provides more details on the transport).
Both the collective activation and the activation via report RV80HGEN technically revert to the program components of the individual activation. For the separate control of the individual activation types form routine AKTIVIEREN_EINZELN (Include MV80HF0A) has a 'USING' parameter, which can have the following characteristic values:
'E' Activate individually
'A' Activate all (= collective activation)
' ' Deactivate individually
During the generation via RV80HGEN the system executes a collective activation for every group indicator sequentially, that means a call of form routine AKTIVIEREN_EINZELN with characteristic value 'A'.
2.6 Transport
If you want to transfer VOFM objects from one system (= source) into another system (= target), this is generally made with an object transport. As of Release 4.0, the VOFM function has a connection to the SAP 'Change and Transport System' (CTS) in order to simplify the transfer process for the user. By the transport connection the system automatically adds newly created or changed VOFM objects to the object list of a transport request which was selected by the user before.
All steps necessary for the execution of a VOFM transport are described in detail in Note 22808 'Transferring formulas'. Note that steps 1-4 are only needed if the VOFM maintenance environment providesno automatic connection to the transport system or if you want to combine a transport request manually. In any case you must execute step 5, regardless of how the transport request was created.
In addition to Note 22808, Note 385067 contains an overview for releases >= 4.6C regarding which sorts of tasks and object entries are required in a transport request (depending on the activity carried out (create/change/activate/deactivate/delete)) in order to transport a VOFM object successfully.
2.7 FAQs: Possible causes of errors and problems
This chapter deals with the most frequent errors and problems that occur when using the VOFM function and its objects. If problems arise for which this note provides no explanation or solution, create an OSS message on component CA-GTF-BS-VOFM and send it to the SAP Support.
(01) Question/problem:
During the order processing, in the shipping, LIS, billing and so on a program termination with error message: PERFORM_NOT_FOUND occurs when you call a VOFM object. This symptom can occur for all users of VOFM objects.
(01) Answer:
The used VOFMobject is not known in the main program of the calling program and thus cannot be addressed. Details on the call method of VOFMobjects are described in section 2.4 of this note. Note 28683 describes how to correct this error.
(02) Question/problem:
Even though report RV80HGEN was executed, the VOFMobject is not registered in the object carrier. Why?
(02) Answer:
During the setup of the object carriers via RV80HGEN the system includes only VOFMobjects which have set the 'active indicator' (refer to section 2.3.2). If the active indicator for the corresponding object is not set, the RV80HGEN does not process the VOFMobject. Solution: Set the active indicator for the respective object and start the RV80HGEN again.
(03) Question/problem:
The syntax check in the ABAP form routine of an VOFM object displays syntax errors.
(03) Answer:
Note the explanations on the work method of the syntax check in Note 393012. In addition, the restrictions of the SAP maintenance responsibility to customer-specific VOFM objects (described in section 1.3) apply.
(04) Question/problem:
When you create/change VOFM objects the system requires an SSCRregistration key, even though the VOFM is within the 'customer namespace'.
(04) Answer:
Refer to the explanations given in section 2.2. 1 'Registration'.
(05) Question/problem:
In which namespace can I create customer-specific VOFM objects? Or: Which routine numbers are reserved for customers?
(05) Answer:
Refer to Note 356737, in addition refer to the explanations in section 2.2 'Namespaces'.
(06) Question/problem:
Is it possible to assign VOFM objects to own development classes?
(06) Answer:
No. Refer also to section 2.2.1
(07) Question/problem:
When you create a VOFM object the system displays information message TR 015 'Object can only be created in SAP development class'.
(07) Answer:
This is no error. Refer to section 2.2.1. and the answer to question number 5.
(08) Question/problem:
How can I transport VOFM objects via the Change and Transport System ?
(08) Answer:
The steps necessary for a successful transport are described in detail in Note 22808.
(09) Question/problem:
The used transport request does not contain an entry for the VOFM object carrier in the object list (for example RV61ANNN, FV45ANNN ...)
(09) Answer:
The object carriers must not be transported. Instead, a setup of a current object carrier suitable for this system is required in the target system. For details refer to Note 22808, step 5 as well as section 2.4.1 and 2.5 of this note.
(10) Question/problem:
How are VOFM objects deleted? And can deletions of VOFM objects also be transported?
(10) Answer:
You should delete VOFM objects only via the editing interface of the VOFM function. Only this way it is ensured that all subobjects (ABAP form routine, TFRM and TFRMT table entries) are completely removed.
You can also transport the deletion youmade into an additional system. For that purpose, the setup of an object list in a transport request analog to the creation (refer to Note 22808) is required.
During the deletion of objects the system deletes the object in the source system. At the time of the export the export program (R3trans) notes that the object does not exist any more. In this case the system enters a "D" into the 'Object function' field in the corresponding entry in the object list of the transport request.
The deletion of table entries is made analog to the deletion of objects. First delete the keys in the source system. Then specify the deleted keys in the request. At the time of the export the transport program notes that the specified keys do not exist any more and deletes them in the target system. If you combine the object list of the transport request manually, you must set the object function of the individual entries correspondingly. To do that, proceed as described in the F1 help of the 'Object function' field.
(11) Question/problem:
During the creation of VOFMobjects the system requires a transport request which contains a task of the 'Repair' category. The system displays message TK 181 'Repair &1 may only contain repaired objects'.
(11) Answer
This problem is caused by a program error. Implement the corrections of Note 326560 or Note 385067 depending on your release.
(12) Question/problem:
During the creation the system displays message TK 112 'Edit objects separately since they belong to different original systems'.
(12) Answer:
This problem is caused by a program error. Implement the corrections of Note 326560 or Note 385067 depending on your release.
(13) Question/problem:
When you create or activate VOFM objects the system displays message: 'Report/PROGRAM statement is missing or program type is INCLUDE?'.
(13) Answer:
This problem is caused by a program error. Implement the corrections of Note 326560 or Note 385067 depending on your release.
(14) Question/problem:
Why does the system generate VOFM objects with source system 'SAP'?
(14) Answer:
Design. The entire VOFM logic depends extremely on basis functions like transport, object directory entries, generation and so on. Because VOFM objects are inserted in SAP standard development classes, these receive ID 'SAP' for source system during the generation process. This cannot be avoided and does not affect the VOFM function.
(15) Question/problem
The system does not insert report RV80HGEN automatically as XPRA into the object list of a transport request.
(15) Answer
Whether the system inserts report RV80HGEN automatically into the object list of the transport request depends on the release you use. For Releases 4.0A to 4.6B the system generates a corresponding entry, provided that all corrections for the VOFM function exist in the system. As of Release 4.6C the basis function of the 'Change & Transport System' (CTS) does not support the automatic insertion of objects of the 'XPRA' category into an object list any more. If you want an automatic registration of the transported routines in the target system, proceed as described in Note 22808, step 5.
(16) Question/problem:
During the activation of VOFM objectsa termination occurs or the system requires a registration key for additional VOFM objects, even if they were not changed.
(16) Answer:
There are inconsistent VOFM objects in the system (refer also to section 2.3.), that means table TFRMcontains entries for which no include with corresponding ABAP form routine exist.
If the termination occurs for VOFM objectsfrom the SAP namespace, this is normally due to a delivery error as described, for example, in Notes 395600 and 0403705. Check whether already a corresponding note exists for the affected VOFMobject. If not, contact the SAP Support.
If the problem occurs for customer-specific routines, the inconsistency is mostly due to a handling or transport error. For example the deletion of VOFMincludes via Transaction SE38has the effect that the system does delete the form routine and the corresponding include, however the system does not delete the entries in tables TFRM and TFRMT. Inconsistencies can also occur due to incomplete or incorrect object lists in transport requests. You can make a correction by newly creating the same object via the VOFM interface or be deletion analog to the method described in Note 395600.
(17) Question/problem:
During the import of Support Packages or during the system upgrade, customer-specific VOFM objects were overwritten or are missing completely.
(17) Answer:
First, check whether the missing VOFMobjects are really missing and if yes, whether all or only certain subobjects do not exist anymore (refer to section 2.3). if the VOFMobject is completely there, generally only a new setup of the object carriers is required. Read section 2.5 'Activation, generation and RV80HGEN' to learn which options exist for this purpose.
If there is indeed a VOFM object but ifthe source code of the ABAP form routine does not correspond to the customer-specific, this is a delivery error. However, you can reconstruct the customer-specific source code with the version management. Proceed as follows: call the ABAP Editor for the affected objects by using Transaction SE38. Afterwards branch into menu 'UTILITIES' -> 'VERSIONS' -> 'VERSION MANAGEMENT'. Deselect the version delivered by SAP and select your original, customer-specific version instead. Choose 'RETRIEVE' to restore this version.
Delivery errors of this type are documented by notes. If there is no corresponding note for the overwritten object in the OSS, contact the SAP Support.
(18) Question/problem:
In the display of the Object Navigator (Transaction SE80) the system does not display newly created VOFM objects. On the other hand, it can also occur that deleted VOFM objects are still contained in the Object Navigator.
(18) Answer:
The Object Navigator displays an obsolete status (refer also to Note 15447). Choose button 'Refresh object list' above the tree structure in order to correct this inconsistency.
(19) Question/problem:
Is it possible to delete VOFM objects delivered by SAP in the standard?
(19) Answer:
Yes. However, because of separate number ranges for VOFM objects SAP does not recommend a deletion of SAP standard objects.
(20) Question/problem:
Which maintenance responsibility has SAP for customer-specific VOFM objects?
(20) Answer:
None. Refer to the explanations in section '1. 3 A frank word on the "source code responsibility"'. According to Note 381348 this includes also VOFMobjects whose creation wasbased on notes of the 'Consulting' or 'Workaround for missing function' category.
(21) Question/problem:
Where can I get help, if my customer-specific VOFM object does not work as expected?
(21) Answer:
If you need support during the implementation of customer-specific VOFM objects you can contact the SAP Remote Consulting. Please understand that SAP cannot check VOFM objectswithin the framework of the normal support. -
Model provider class and data provider class
please explain Model provider class and data provider class?
Hi,
both MPC and DPC get generated as runtime artifacts.
MPC - This is used to define model. you can use the method Define to create entity, properties etc using code based implementation. you rarely use MPC extension class.
DPC - used to code your CRUDQ methods as well as function import methods. you write all your logic in redefined methods of DPC extension class.
Refer Generated ABAP Classes and Service Registration - SAP NetWeaver Gateway - SAP Library for more information.
you can also refer my blog Let’s code CRUDQ and Function Import operations in OData service! which will provide you clear idea on how to redefine various CRUDQ methods in DPC extension class.
Regards,
Chandra -
CIN activation for comapny code in IDES..?
Hi all
Can anybody explain me from basic settings for CIN activation for my own company code which is configured in IDES.
I have created 1 manufacturing plant & 1 depot plant.
Please explain me all the configuarion for CIN (Both plants-manufacturing and depot).
Please forward me documnets , if possible pls suggest all the precaution for this CIN configuration.
Thanks
sap-mmhi,
covers all of the tasks associated with Country Version India (CIN), including Customizing, day-to-day operations, and reporting.
In Customizing and master data, the Excise Manager is authorized to:
Work with the CIN Implementation Guide (IMG)
Use the health check tool
Define number ranges for excise invoices
Maintain excise master data
Make retrospective price amendments
In your day-to-day operations, this role allows you to:
Capture, change, display, post, and cancel incoming excise invoices
Capture excise invoices at depots
Complete subcontracting challans and perform quantity reconciliation
Post excise invoice journal vouchers
Track forms
Activities in Financial Accounting (FI)
The Excise Manager can:
Create the excise registers
Transfer outstanding CENVAT credit on capital goods to the appropriate CENVAT accounts
So in this way roles are divided for excise clerk, supervisor, manager, tds clerk etc...
A Country Version is designed specifically to cater the business operations of that country over and above the generic SAP system functionalities. It comprises of functionalities degined for the laws and business practices pertaining to the country.
Most of the country-specific functions for India relate to Financials and Logistics.
The main areas are as follows:
Excise duty and the central value-added tax system (CENVAT)
Withholding tax (also known as tax deducted at source)
Sales tax
Maintenance and printing of statutory excise registers
The official help documentation for Country Version India:
http://help.sap.com/saphelp_erp2005/helpdata/en/09/ebf138cdd78a4be10000000a114084/frameset.htm
For further details refer below links..
https://wiki.sdn.sap.com/wiki/display/ERPLO/CIN+Configuration
https://wiki.sdn.sap.com/wiki/display/ERPLO/CINConfiguration%28India%29
***CIN CONFUGURATION***
1.1 Maintain Excise Registration
SAPSPRO Basic settingIndia tax on Goods Movements Logistics general Ref. IMG Maintain Excise Registrations
APPLICABLE
1.2 Maintain Company Code Settings
tax on Goods Logistics general SAP Ref. IMG SPRO Maintain Company Code Basic setting India Movements Settings
APPLICABLE
1.3 Maintain Plant Settings
SAP Ref.SPRO Basic setting India tax on Goods Movements Logistics general IMG Maintain Plant Settings
APPLICABLE
1.4 Maintain Excise Groups
SPRO BasicIndia tax on Goods Movements Logistics general SAP Ref. IMG Maintain Excise Groupssetting
APPLICABLE
1.5 Maintain Series Groups
India tax on Goods Movements Logistics general SAP Ref. IMG SPRO Maintain Series GroupsBasic setting
APPLICABLE
1.6 Maintain Excise Duty Indicators
tax on Goods Logistics general SAP Ref. IMG SPRO Maintain Excise Duty Basic setting India Movements Indicators
APPLICABLE
1.7 Maintain Sub transaction Type with Text
India tax on Goods Movements Logistics general SAP Ref. IMG SPRO Maintain Sub transaction Type with TextBasic setting
APPLICABLE
1.8 Determination of Excise Duty
tax Logistics general SAP Ref. IMG SPRO Select Tax Calculation Determination of Excise DutyIndia on Goods Movements Procedure
APPLICABLE
1.9 Maintain Excise Defaults
SAP Ref.SPRO Determination of ExciseIndia tax on Goods Movements Logistics general IMG Maintain Excise DefaultsDuty
APPLICABLE
1.10 Condition-Based Excise Determination
tax on Goods Logistics general SAP Ref. IMG SPRO Define Tax Code for Condition-Based Excise DeterminationIndia Movements Purchasing Documents
APPLICABLE
1.11 Condition-Based Excise Determination
tax on Goods Logistics general SAP Ref. IMG SPRO Assign Tax Code to Condition-Based Excise DeterminationIndia Movements Company Codes
APPLICABLE
1.12 Classify Condition Types
SAPSPRO Condition-BasedIndia tax on Goods Movements Logistics general Ref. IMG Classify Condition TypesExcise Determination
APPLICABLE
1.13 Maintain Chapter IDs
tax on Goods Logistics general SAP Ref. IMG SPRO Maintain Chapter ids Master dataIndia Movements
APPLICABLE
1.14 Assign Users to Material Master Screen Sequence for Excise Duty
SPRO Master dataIndia tax on Goods Movements Logistics general SAP Ref. IMG Assign Users to Material Master Screen Sequence for Excise Duty
APPLICABLE
1.15 Specify Excise Accounts per Excise Transaction
tax on Goods Logistics general SAP Ref. IMG SPRO Specify Excise Accounts per Excise Account determinationIndia Movements Transaction
APPLICABLE
1.16 Specify G/L Accounts per Excise Transaction
tax on Goods Logistics general SAP Ref. IMG SPRO Specify G/L Accounts per Excise Account determinationIndia Movements Transaction
APPLICABLE
1.17 Incoming Excise Invoices
SAPSPRO BusinessIndia tax on Goods Movements Logistics general Ref. IMG Incoming Excise InvoicesTransactions
APPLICABLE
1.18 Define Processing Modes Per Transaction
Logistics general SAP Ref. IMG SPRO Define Processing Modes Business TransactionsIndia tax on Goods Movements Per Transaction
APPLICABLE
1.19 Define Reference Documents Per Transaction
tax on Goods Logistics general SAP Ref. IMG SPRO Define Reference Documents Per Business TransactionsIndia Movements Transaction
APPLICABLE
1.20 Maintain Rejection Codes
SAPSPRO BusinessIndia tax on Goods Movements Logistics general Ref. IMG Maintain Rejection CodesTransactions
APPLICABLE
1.21 Specify Which Movement Types Involve Excise Invoices
Logistics SAP Ref. IMG SPRO Specify Which Business TransactionsIndia tax on Goods Movementsgeneral Movement Types Involve Excise Invoices
APPLICABLE
1.22 Outgoing Excise Invoices
tax on Goods Logistics general SAP Ref. IMG SPRO Assign Outgoing Excise Invoices Business TransactionsIndia Movements Billing Types to Delivery Types
APPLICABLE
1.23 Maintain Default Excise Groups and Series Groups
Logistics general SAP Ref. IMG SPRO Outgoing Excise Invoices Business TransactionsIndia tax on Goods Movements Maintain Default Excise Groups and Series Groups
APPLICABLE
1.24 Subcontracting Attributes
tax on Logistics general SAP Ref. IMG SPRO Subcontracting Subcontracting Business TransactionsIndia Goods Movements Attributes
APPLICABLE
1.25 Maintain Movement Type Groups
SPRO BusinessIndia tax on Goods Movements Logistics general SAP Ref. IMG Subcontracting SubcontractingTransactions Attributes
APPLICABLE
1.26 Utilization Determination
SAPSPRO BusinessIndia tax on Goods Movements Logistics general Ref. IMG Utilization UtilizationTransactions Determination
APPLICABLE
1.27 Specify SAP script Forms
SPRO BusinessIndia tax on Goods Movements Logistics general SAP Ref. IMG Specify SAP script Excise RegistersTransactions Forms
APPLICABLE
1.28 Number Ranges
SAP Ref. IMG SPRO Number ToolsIndia tax on Goods MovementsLogistics general Ranges
APPLICABLE
1.29 Message Control
SAP Ref. IMG SPRO Message ToolsIndia tax on Goods MovementsLogistics general Control
APPLICABLE
J1I2
Prepare a sales tax register
J1I3
Create outgoing excise invoices in batches
J1I5
Update the RG 1 and Part I registers
J1IEX
Incoming Excise Invoices (central transaction)
J1IEX_C
Capture an incoming excise invoice (excise clerk)
J1IEX_P
Post an incoming excise invoice (excise supervisor)
J1IF01
Create a subcontracting challan
J1IF11
Change a subcontracting challan
J1IF12
Display a subcontracting challan
J1IF13
Complete, reverse, or recredit a subcontracting challan
J1IFQ
Reconcile quantities for subcontracting challan
J1IFR
List subcontracting challan
J1IH
Make a CENVAT adjustment posting
J1IIN
Create an outgoing excise invoice
J1IJ
Assign excise invoices to a delivery for sales from depots
J1INJV
Adjust withholding tax Item
J1INREP
Reprint a withholding tax certificate for a vendor
J1IQ
Year-End Income Tax Depreciation Report
J1IR
Download register data
J1IS
Process an excise invoice (outgoing) for other movements
J1IU
Process exemption forms
J1IW
Verify and post an incoming excise invoice
J1IX
Create an incoming excise invoice (without reference to purchase order)
J2I8
Transfer excise duty to CENVAT account
J2IU
Remit excise duty fortnightly
J2I9
Monthly CENVAT return
J1IG
Excise invoice entry at depot
J1IGA
Create additional excise entry at depot
J2I5
Extract data for excise registers
J2I6
Print excise registers
Regards
Priyanka.P -
Dear Experts,
Please provide me user manulas for MM-CIN.I am not asking for Config of CIN.Kindly provide me the day to day transactions from user perspective and the report perspective also.........***CIN CONFUGURATION***
1.1 Maintain Excise Registration
SAP@SPRO Basic setting@India @ tax on Goods Movements@ Logistics general @Ref. IMG Maintain Excise Registrations@
APPLICABLE
1.2 Maintain Company Code Settings
tax on Goods@ Logistics general @ SAP Ref. IMG @SPRO Maintain Company Code@ Basic setting @India @Movements Settings
APPLICABLE
1.3 Maintain Plant Settings
SAP Ref.@SPRO @ Basic setting @India @ tax on Goods Movements@ Logistics general @IMG Maintain Plant Settings
APPLICABLE
1.4 Maintain Excise Groups
SPRO Basic@India @ tax on Goods Movements@ Logistics general @ SAP Ref. IMG @ Maintain Excise Groups@setting
APPLICABLE
1.5 Maintain Series Groups
@India @ tax on Goods Movements@ Logistics general @ SAP Ref. IMG @SPRO Maintain Series Groups@Basic setting
APPLICABLE
1.6 Maintain Excise Duty Indicators
tax on Goods@ Logistics general @ SAP Ref. IMG @SPRO Maintain Excise Duty@ Basic setting @India @Movements Indicators
APPLICABLE
1.7 Maintain Sub transaction Type with Text
@India @ tax on Goods Movements@ Logistics general @ SAP Ref. IMG @SPRO Maintain Sub transaction Type with Text@Basic setting
APPLICABLE
1.8 Determination of Excise Duty
tax@ Logistics general @ SAP Ref. IMG @SPRO Select Tax Calculation@ Determination of Excise Duty@India @on Goods Movements Procedure
APPLICABLE
1.9 Maintain Excise Defaults
SAP Ref.@SPRO Determination of Excise@India @ tax on Goods Movements@ Logistics general @IMG Maintain Excise Defaults@Duty
APPLICABLE
1.10 Condition-Based Excise Determination
tax on Goods@ Logistics general @ SAP Ref. IMG @SPRO Define Tax Code for@ Condition-Based Excise Determination@India @Movements Purchasing Documents
APPLICABLE
1.11 Condition-Based Excise Determination
tax on Goods@ Logistics general @ SAP Ref. IMG @SPRO Assign Tax Code to@ Condition-Based Excise Determination@India @Movements Company Codes
APPLICABLE
1.12 Classify Condition Types
SAP@SPRO Condition-Based@India @ tax on Goods Movements@ Logistics general @Ref. IMG Classify Condition Types@Excise Determination
APPLICABLE
1.13 Maintain Chapter IDs
tax on Goods@ Logistics general @ SAP Ref. IMG @SPRO Maintain Chapter ids@ Master data@India @Movements
APPLICABLE
1.14 Assign Users to Material Master Screen Sequence for Excise Duty
@SPRO @ Master data@India @ tax on Goods Movements@ Logistics general @SAP Ref. IMG Assign Users to Material Master Screen Sequence for Excise Duty
APPLICABLE
1.15 Specify Excise Accounts per Excise Transaction
tax on Goods@ Logistics general @ SAP Ref. IMG @SPRO Specify Excise Accounts per Excise@ Account determination@India @Movements Transaction
APPLICABLE
1.16 Specify G/L Accounts per Excise Transaction
tax on Goods@ Logistics general @ SAP Ref. IMG @SPRO Specify G/L Accounts per Excise@ Account determination@India @Movements Transaction
APPLICABLE
1.17 Incoming Excise Invoices
SAP@SPRO Business@India @ tax on Goods Movements@ Logistics general @Ref. IMG Incoming Excise Invoices@Transactions
APPLICABLE
1.18 Define Processing Modes Per Transaction
@ Logistics general @ SAP Ref. IMG @SPRO Define Processing Modes@ Business Transactions@India @tax on Goods Movements Per Transaction
APPLICABLE
1.19 Define Reference Documents Per Transaction
tax on Goods@ Logistics general @ SAP Ref. IMG @SPRO Define Reference Documents Per@ Business Transactions@India @Movements Transaction
APPLICABLE
1.20 Maintain Rejection Codes
SAP@SPRO Business@India @ tax on Goods Movements@ Logistics general @Ref. IMG Maintain Rejection Codes@Transactions
APPLICABLE
1.21 Specify Which Movement Types Involve Excise Invoices
Logistics@ SAP Ref. IMG @SPRO Specify Which@ Business Transactions@India @ tax on Goods Movements@general Movement Types Involve Excise Invoices
APPLICABLE
1.22 Outgoing Excise Invoices
tax on Goods@ Logistics general @ SAP Ref. IMG @SPRO Assign@ Outgoing Excise Invoices @ Business Transactions@India @Movements Billing Types to Delivery Types
APPLICABLE
1.23 Maintain Default Excise Groups and Series Groups
@ Logistics general @ SAP Ref. IMG @SPRO @ Outgoing Excise Invoices @ Business Transactions@India @tax on Goods Movements Maintain Default Excise Groups and Series Groups
APPLICABLE
1.24 Subcontracting Attributes
tax on@ Logistics general @ SAP Ref. IMG @SPRO Subcontracting@ Subcontracting@ Business Transactions@India @Goods Movements Attributes
APPLICABLE
1.25 Maintain Movement Type Groups
@SPRO Business@India @ tax on Goods Movements@ Logistics general @SAP Ref. IMG Subcontracting@ Subcontracting@Transactions Attributes
APPLICABLE
1.26 Utilization Determination
SAP@SPRO Business@India @ tax on Goods Movements@ Logistics general @Ref. IMG Utilization@ Utilization@Transactions Determination
APPLICABLE
1.27 Specify SAP script Forms
@SPRO Business@India @ tax on Goods Movements@ Logistics general @SAP Ref. IMG Specify SAP script@ Excise Registers@Transactions Forms
APPLICABLE
1.28 Number Ranges
@ SAP Ref. IMG @SPRO Number@ Tools@India @ tax on Goods Movements@Logistics general Ranges
APPLICABLE
1.29 Message Control
@ SAP Ref. IMG @SPRO Message@ Tools@India @ tax on Goods Movements@Logistics general Control
APPLICABLE
J1I2
Prepare a sales tax register
J1I3
Create outgoing excise invoices in batches
J1I5
Update the RG 1 and Part I registers
J1IEX
Incoming Excise Invoices (central transaction)
J1IEX_C
Capture an incoming excise invoice (excise clerk)
J1IEX_P
Post an incoming excise invoice (excise supervisor)
J1IF01
Create a subcontracting challan
J1IF11
Change a subcontracting challan
J1IF12
Display a subcontracting challan
J1IF13
Complete, reverse, or recredit a subcontracting challan
J1IFQ
Reconcile quantities for subcontracting challan
J1IFR
List subcontracting challan
J1IH
Make a CENVAT adjustment posting
J1IIN
Create an outgoing excise invoice
J1IJ
Assign excise invoices to a delivery for sales from depots
J1INJV
Adjust withholding tax Item
J1INREP
Reprint a withholding tax certificate for a vendor
J1IQ
Year-End Income Tax Depreciation Report
J1IR
Download register data
J1IS
Process an excise invoice (outgoing) for other movements
J1IU
Process exemption forms
J1IW
Verify and post an incoming excise invoice
J1IX
Create an incoming excise invoice (without reference to purchase order)
J2I8
Transfer excise duty to CENVAT account
J2IU
Remit excise duty fortnightly
J2I9
Monthly CENVAT return
J1IG
Excise invoice entry at depot
J1IGA
Create additional excise entry at depot
J2I5
Extract data for excise registers
J2I6
Print excise registers
Regards,
Indranil -
CIN - complete doc and customization doc
Dear all,
Pls give me cin related full info and customization doc with full detailed and screen shots.
yr input will be very greatful for me. thanks in advnce.
rgds
JKWhat is CIN?
CIN Means Country India Version
In Indian Taxing procedure, Excise Duty plays a vital role in manufacturing cenariou2019s. Excise related configuration is known as CIN configuration. CIN Configuration is a topic in itself.
Some info on CIN Configuration (it may not appear as understandable below, but if you check on screen, it will be understood better)
Country Version India comes with four pricing procedures as follows:
- JINFAC (Sales from manufacturing plants)
- JINEXP (Export sales)
- JINDEP (Sales from depots)
- JINSTK (Stock transfers
CIN: IMG > Logistics - General > Tax on Goods Movement > India > Basic Settings > Maintain Excise Registrations
In this IMG activity, you maintain the data relating to your excise registrations.
- Enter each of your excise registrations, specifying a four-character code for each Excise Registration Ids
In this activity, you maintain excise registration IDs. You create one ID for each of your business's excise registrations.
- For each excise registration in your business create a registration ID, and state:
- Which taxes the registration covers (additional excise duty, special excise duty, and cess) Fields for any taxes that are not covered will be hidden in transactions involving excise duty.
- The maximum number of items to be printed on each excise invoice
- Whether you are allowed partial CENVAT credits
Maintain Registration ID NUMBER, Excise code number, excise registration number
ECC Number: Specifies the organization's ECC number.
Excise Registration Number: A number assigned to each premises or location that has registered as a manufacturer with the excise authorities.
Every entity with an excise registration number is required to keep its own excise books.
Excise range: Specifies the excise range in whose area the excise registration is located.
Excise Division: Specifies the excise division in whose area the excise registration is located.
Excise Collectorate: The code of the excise collectorate in whose area the excise registration is located.
Indicator for confirming, AED usage Additional Excise duty Percentage.
These are livable under the additional duties of excise act. These duties are in addition to basic excise duty and special excise duty. Example - Additional Excise duty is livable in case of textile products, tobacco and sugar.
Similarly for SED CESS Number of Items in Excise Invoice Shows the maximum number of line items that the authorities allow per excise invoice.
Dependencies - This information is used when you create an excise invoice in Sales and Distribution (SD) for factory sales and for other movements. This information is used to split the transfer postings' items into multiple subcontracting challans.
Excise register set description: Description of the excise registers set.
Partial CENVAT Credit: Indicates that the excise registration ID is allowed to credit only a portion of its input excise duty to its CENVAT account
Dependencies - When you post a goods receipt, the system splits the input excise duty on the material into its deductible and nondeductible amounts. It posts the deductible duty to the appropriate CENVAT account, and adds the nondeductible duty to the material value.
This information is also shown when you post the vendor's excise invoice.
Maintain Company Code Settings.
In this IMG activity, you maintain the data relating to your company codes.
Document Type for CENVAT Postings.
It controls, which document type the system uses when making CENVAT postings in Financial Accounting (FI). Here ED is document type for cenvat posting.
Indicator for providing debit account overwriting
Debit Account Overwrite Indicator. X - Indicates debit accounts can be overwritten. Use In excise journal voucher transaction. It provides the flexibility to the user to enter the debit account of his choice depending on the nature of transaction.
Automatic balance Indicator - Excise year start month. The calendar month marking the beginning of the excise year. This start month represents the month for the start of the excise invoice number range. The month 04 is entered here indicating April of the calendar year as the start month for excise invoices. Any change by the Excise authorities regarding start month should be taken care of by an entry in this field and initialization.
Excise invoice selection procedure :Excise invoice selection type. To indicate the method opted by the company for selecting the excise invoice. It can be either earliest or latest invoices that were received. Number of excise invoices to be selected Indicates the number of excise invoices that needs to be selected in the excise invoice selection.
Days to be considered for excise invoice selection Number of days from document date for excise invoice selection.
Example - If the value of this field is 20 and today is 28-03-97. The excise invoice selection will show the related invoices only for the period 08-03-97 to 28-03-97.
Document type for TDS FI posting: Financial accounting document type for TDS posting.
Document type for FI posting on Utilisation Financial accounting document type for TDS posting.
Indicator for item level excise duty round off - This indicator is to be used for deciding whether Item level excise
duty amount rounding off is required during procurement cycle. If marked 'X' then the excise duty amount will be rounded off to the nearest rupee at the Purchase order level. This will not round off the CENVAT credit to be taken. If the duty amount is less than one rupee then no rounding is done
Rounding off of Excise duty for outgoing excise invoice - You can round off the Excise amount to be paid during an outgoing
Excise invoice by marking this indicator as 'X'. The rounding is done at the item level for each item where the amount is greater than 1 Rupee.
Immediate Credit on Capital Goods - Instructs the system, when you verify a goods receipt for capital goods, to immediately post half of the input excise duty to the appropriate CENVAT accounts. The rest is posted the CENVAT on hold account, for use in the following year.
CVD Clearing Account - Specifies which G/L account the system credits when you take a CENVAT credit on countervailing duty in the Incoming Excise Invoices transaction.
Exchange rate type - Key representing a type of exchange rate in the system.
- You enter the exchange rate type to store different exchange rates. Example - You can use the exchange rate type to define a buying rate, selling rate, or average rate for translating foreign currency amounts. You can use the average rate for the currency translation, and the bank buying and selling rates for valuation of foreign currency amounts.
Exchange rate type to be used for Export excise duty converts - When you are creating an Excise invoice for export sales then the exchange rate for duty calculation will be picked up using this Exchange rate type.
Maintain Plant Settings - In this IMG activity, you maintain excise information relating to your plants.
Plant Settings - In this activity, you maintain excise information relating to your plants.
For each plant:
- Specify whether it is a manufacturing site or a depot.
- Assign it an excise registration ID. - You can assign the same ID to more than one plant, if required.
Depot - Indicates that the plant in question is a depot. - Depots are required to prepare register RG 23D, and follow different procedures for goods receipt and invoice generation.
- Number of goods receipt per excise invoice.
- Multiple GR for one excise invoice, Single credit
- Multiple GR for one excise invoice, multiple credit
Maintain Excise Groups - In this IMG activity, you define your excise groups. For each excise group, you can also control how various excise invoice transactions will work.
Excise Groups - In this activity, you define excise groups. An excise group allows you to maintain a separate set of excise registers and excise accounts. The RG 23A, RG 23C and PLA serial numbers are created for an excise group.
Recommendation - Under normal circumstances, excise authorities require every business to maintain only one set of excise registers and one set of accounts. But through exemption from the authorities, multiple books can be maintained.
If your company has only one set of excise registers, then you need to maintain only one excise group.
1. Create one excise group for each set of registers that you need to keep.
2. Assign the excise groups to plants.
3. Maintain whether this Excise group is for a depot or not.
If you receive only one consignment for an Excise challan then you can leave GR's per EI as blank. If you receive multiple GR's for a given Excise challan and would like to avail multiple credit mark the GRs per EI as 'Multiple GR's for one excise invoice, multiple credit'. Alternatively if you want to availa the credit only after all the goods receipts have been made mark it as ' Multiple GR for one excise invoice, single credit'.
4. If you want to automatically create Excise invoice during Sales cycle at the time of billing the tick the indicator 'Create EI'
5. During depot sales if you do not want to do RG23D selection and posting separately and would like to complete RG23D selection in one step mark the indicator 'RG23D Auto post'. This will post the selected records into RG23D automatically. You cannot cancel the selection later.
6. If the indicator 'Default GR qty' is marked system will default the Excise challan quantity on to the Goods receipt if the Excise invoice number is given in the pop-up.
7. If the indicator 'Folio no create' is marked system will generate Folio numbers for RG23D during receipt of excise invoice into depot.
8. 'Automatic posting' when ticked will post the Excise invoice other movements automatically along with creation in single step.
9. 'Create Part1 for Block Stock' when marked will create a Part1 during the receipt of material into Blocked stock .
10. 'Create Part1 for STO' when marked will create a Part1 during the receipt of material through inter plant transfers.
11. 'Create Part1 for consumption stock' when marked will create a Part1 during the receipt of material into consumption stock. Excise Group Governs which set of excise registers a business transaction will be included in.
Following is the relation between excise group, plant and registration. - In define excise groups in Customizing.
Then, in transactions involving excise duty, for example, when you post a vendor's excise invoice, you specify which excise group you are using. This information tells the system which G/L accounts to post the excise to. At the end of the period, when you come to prepare your excise registers, you create different sets for each excise group.
Indicates that the plant in question is a depot. - Depots are required to prepare register RG 23D, and follow different procedures for goods receipt and invoice generation.
- GR Per Excise Invoice
- Multiple GR for one excise invoice , Multiple credit
- Multiple GR for one excise invoice , Single Credit
Create Excise Invoice Automatically - Instructs the system to automatically create a Sales and Distribution (SD) excise invoice immediately you create a commercial invoice or a pro forma invoice.
The excise invoice is created in the background. - If you want to make use of this function, you must also define the
default plant, excise group, and series groups in Customizing for Sales and Distribution (SD), by choosing Excise Group - Series Group Determination.
RG23D Sales Creation and posting option - RG23D Automatic Option if selected will create Depot excise invoice by posting the selection of excise invoices in single step. If this is not selected then you need to separately do RG23D selection
followed by PGI and then RG23D verification and posting. If you need automatic posting of RG23D selection then the Post Goods Issue should have been completed before running RG23D selection.
Default excise qty in GR - If this indicator is ticked then while doing Goods Receipt using 'MB01' system will default the excise invoice quantity on to the Goods receipt document.
Folio number for depo Posting - If this indicator is marked then while creating Excise invoice for other movements system automatically does the Verify and Post. You need not separately Post the excise invoice
Also we can set indicator for creation of part 1 for:
- Blocked stock
- Stock transport order
- Consignment stock
Maintain Series Group - In this IMG activity, you define the different excise series groups within your company. Series groups allow you to maintain multiple number ranges for the outgoing excise documents. Based on excise regulations and exemptions from the authorities you can maintain multiple number series for outgoing documents. But each of these series has to be declared to the excise authorities.
- Define excise series groups based on type of outgoing document
- Assign series group to excise registration ID
- If no financial postings are required for an Excise invoice in this seris group then you tick the 'No utilization' indicator.
- If the CENVAT has to be paid immediately and you need not wait for the Fort nightly payment then mark the 'Immediate Utilization' Iindicator. Example - You could define two series groups, group 001 for excise invoices, and group 002 for 57 F4 documents.
- No account postings for CENVAT in sales cycle
- No utilization Flag
If you do not need any CENVAT utilization for an excise invoice but would like to just generate an excise invoice then you need to mark this indicator.
If the flag is checked then system will create an Excise invoice in the given Series group but there will not be any account postings or Part2 postings.
Immediate Utilization of CENVAT - Specifies that when you create an excise invoice, the system immediately pays the amount from CENVAT and creates the Part II entry. Such invoices will not be listed for fortnightly utilization.
If you have both fortnightly and immediate utilization for the same excise group, the account determination within CIN IMG should point to the ED interim account.
Account determination for immediate payment will be done exactly the same as being done for fortnightly utilization program.
Maintain Excise Duty Indicators - In this IMG activity, you maintain the excise duty indicators.
IMG > Logistics - General > Tax On Goods Movement > India > Basic Settings > Determination of Excise Duty > Select Tax Calculation Procedure
In this IMG activity, you specify which tax procedure you want to use for determining excise duties and sales taxes on input materials in India.
- If you use condition-based excise determination, use a copy of the tax procedure TAXINN.
- If you use formula-based excise determination, use a copy of the tax procedure TAXINJ.
This tax procedure also supports condition-based excise determination, so that you can work with both concurrently.
We strongly recommend that new customers use condition-based excise determination. Note that once you have started using a tax procedure, you cannot switch to another one, otherwise you will not be able to display old documents.
Maintain Excise Defaults - In this IMG activity, you define which tax procedure and pricing condition types are used in calculating excise taxes using formula-based excise determination.
If you use condition-based excise determination, fill out the CVD cond. field and leave all the others blank.
If you use formula-based excise determination, fill out all of the fields as follows:
- Enter the tax procedure and the pricing conditions that are relevant for excise tax processing.
- Specify the purchasing and sales conditions types used for basic excise duty, additional excise duty, special excise duty, and cess.
- Specify the conditions in the sales order that are used for excise rates.
- Specify the countervailing duty condition type used for import purchase orders.
See also : SAP Library -> Logistics -> Country Versions -> Asia-Pacific -> India -> Materials Management (MM) -> Condition-Based Excise Determination and -> Formula-Based Excise Determination.
IMG > Logistics - General > Tax On Goods Movement > India > Basic Settings > Determination of Excise Duty >
Condition-Based Excise Determination
When you enter a purchasing document, for example, a purchase order, the R/3 System automatically calculates the applicable excise duties using the condition technique.
Features : The standard system comes with two tax calculation procedures. TAXINN is only supports condition-based excise determination, whereas TAXINJ supports condition-based excise determination and formula-based excise determination. Both tax procedures contain condition types that cover all of the excise duties and sales taxes applicable.
Since the exact rates of excise duty can vary on a large number of factors, such as which vendor you purchase a material from, or which chapter ID the vendor stocks the material under, you create condition records for every sort of excise duty.
When you come to enter a purchasing document, the system applies the excise duty at the rates you have entered in the condition records.
Customizing : Make the settings in Customizing Basic -> India -> for Logistics u2013 General, by choosing Taxes on Goods Movements Account -> Excise Duties Using Condition Technique and u2026-> Settings Determination.
These activities include one activity where you define a tax code for condition-based excise determination.
Master Data - Create condition records for all excise duties that apply, and enter the tax code for condition-based excise determination in each.
Day-to-Day Activities - When you enter a purchase order or other purchasing document, enter the tax code for condition-based excise determination in each line item. The system then calculates the excise duties using the condition records you have created.
When the ordered materials arrive, you post the goods receipt and the excise invoice. The system posts the excise duty to the appropriate accounts for deductible input taxes when you enter the excise invoice.
Creating Condition Records for Excise Duty
1. In the command field, enter FV11 and choose .
2. Enter the condition type that you want to create a condition record for and choose .
The Key Combination dialog box appears.
3. Select the combination of objects that you want to create the condition record for. On the dialog box, Control Code means "chapter ID." So, for example, to create a condition record for a tax that applies to a combination of country, plant, and chapter ID, select Country/Plant/Control Code.
4. Choose .
5. Enter data as required. - In the Tax Code field, enter the dummy tax code that you have defined.
6. Save the condition record.
Formula-Based Excise Determination - When you execute a business transaction involving materials that are subject to excise duty, the system automatically calculates the duty for you.
In order for the system to be able to determine which rate of excise duty to apply, you must have maintained all the data on the Excise Rate Maintenance screen, which you can Master Data®access from the SAP Easy Access screen by choosing Indirect Taxes Excise Rate Maintenance.
You maintain the following types of data:
- Plant master data
You assign each of your plants an excise duty indicator. You can use the same indicator for all the plants with the same excise status from a legal point of view, such as all those that are in an exempt zone. See also the information about manufacturers that are only entitled to deduct a certain portion of the duty (see Partial CENVAT Credit).
- Vendor master data
For each of your vendors with the same excise status from a legal perspective, you define an excise duty indicator. You must also specify the vendor type u2013 for example, whether the vendor is a manufacturer, a depot, or a first-stage dealer. You must also stipulate if the vendor qualifies as a small-scale industry. For each permutation of plant indicator and vendor indicator, you then create a final excise duty indicator.
- Customer master data
Similarly, you assign the same excise duty indicator to each of your customers that share the same legal excise status.
Again, for each permutation of plant indicator and customer indicator, you then create a final excise duty indicator.
- Material master data
Each material is assigned a chapter ID.
- Excise tax rate
For every chapter ID and final excise duty indicator, you maintain the rate of excise duty.
If your business only qualifies for partial CENVAT credit, you must customize your system accordingly.
Let us consider an example to illustrate how the system determines which rate of excise duty to apply to a material. Assume you are posting a sale of ball bearings to a customer. The system automatically determines the rate of excise duty as follows:
1. Looks up the customer master data to see what status you have assigned the customer.
Let's assume you've assigned the customer status 3.
2. Looks up the plant master data to see what status you have assigned the plant. Similarly, your plant has status 2.
3. The system looks up the table under Excise Indicator for Plant and Customer to see what the final excise duty indicator is for customer status 3 and plant status 2: It is 7.
4. The system determines the chapter ID of the ball bearing for the plant.
Letu2019s assume the chapter ID at plant for the ball bearings is 1000.01.
5. Finally, the system looks up the table under Excise Tax Rate to see what rate of duty applies to chapter ID 1000.01 under
status 7.
Define Tax Code for Purchasing Documents - In this IMG activity, you define a tax code for the purposes of calculating excise duty when you enter purchasing documents. Only carry out this activity if you use condition-based excise
determination.
- Create a new tax code, and set the tax code type to V (input tax). Do not make any other settings for it.
- Assign Tax Code to Company Codes
In this IMG activity, assign the tax code for purchasing documents to the company codes where it will be used.
Only carry out this activity if you use condition-based excise determination.
Classify Condition Types - In this IMG activity, you specify which condition types you use for which sort of tax. Note that this only applies to condition types that you use with the new excise determination method. The system uses this information when you create a document from another one. For example, when you enter an incoming excise invoice from a
purchase order, or when you create an outgoing excise invoice from a sales order, the system determines the various excise duties in the excise invoice using the information that you have entered here. In addition, when you create a purchasing document, the system only uses the condition types that you enter here.
- For taxes on purchases, use the condition types contained in the tax procedure.
- For taxes on sales, use the condition types contained in the pricing procedures.
The standard system comes with sample settings for the tax calculation procedures and pricing procedures.
Use these settings as a basis for your own.
IMG > Logistics - General > Tax On Goods Movement > India > Account Determination
Define G/L Accounts for Taxes - In this IMG activity, you specify which G/L accounts you will use to record which taxes.
Requirements - You have set up G/L accounts for each of the processing keys listed below.
- Assign an account to each of the following posting keys. The accounts for VS1, VS2, and VS3 are used as clearing accounts during excise invoice verification.
- VS1 (basic excise duty)
- VS2 (additional excise duty)
- VS3 (special excise duty)
- VS5 (sales tax setoff)
- MWS (central sales tax)
- MW3 (local sales tax)
- ESA (service tax)
- ESE (service tax expense)
Specify Excise Accounts per Excise Transaction - In this IMG activity, you specify which excise accounts (for excise
duty and CENVAT) are to be posted to for the various transaction types. Enter all the accounts that are affected by each transaction type. If you use sub transaction types, enter the accounts for each sub transaction type as well.
Transaction type UTLZ is used for determining accounts only while posting excise JVs and also if the payment of excise duty has to be done fortnightly. The fortnightly CENVAT payment utility picks up the credit side accounts from the transaction types of GRPO, EWPO, and TR6C for determining the CENVAT and PLA accounts. There is no separate transaction type for fortnightly payment.
Example:
- Excise TT DC ind Account name
- GRPO CR CENVAT clearing account
- GRPO CR RG 23 BED account
- GRPO DR CENVAT on hld account
Specify G/L Accounts per Excise Transaction - In this IMG activity, you assign the excise and CENVAT accounts to G/L
accounts. When you come to execute the various transactions, the system determines which G/L accounts to post to by looking at the:
- Excise group
- Company code
- Chart of accounts
Furthermore, if you want separate account determination settings within an excise group, you can also use sub transaction types.
Requirements
You have already:
- Defined the G/L accounts
- Defined the excise groups
- Maintained the transaction accounts
Activities - For each excise group, assign the excise and CENVAT accounts to G/L accounts. For most businesses, one set of accounts will suffice for all transactions.
Note : you need not remit the CENVAT to the excise department immediately, so maintain the credit account for transaction type DLFC as an excise duty interim account. This will be set off when you remit the duty. Config setting needed to be done in order to get the Excise Details Screen in Material Master.
Even though this functionality is available in enterprise version, a small configuration step has to be made in Screen Sequences for Material Master.
Following document helps you to do this configuration.
- Material Master à Logistics General
1. Go to IMG Define Structure of Data Screen for each Configuring the Material master Screen Sequence.
2. Select your screen sequence. Usually it would be 21. Select the same and click on Data Screen in the left frame.
3. Once the data screens are exhibited, select data screen no. 15, ie. SSq. 21and Scrn 15, which is u201CForeign Trade: Import Datau201D. Select the same and click on Sub screens in the left frame.
4. Go to the last sub screen i.e. 21-15-6 - SAPLMGD1- 0001 and select the same. Click on tab view sub screen and ensure that the sub screen is blank.
5. Now in the last sub screen i.e. no.6 you delete SAPLMGD1 u2013 0001 and instead add SAPLJ1I_MATERIAL_MASTER and in the screen no. 2205.
6. Save the setting.
7. Create a Material Master and check whether in Screen Foreign Trade
u2013 Import, Excise related sub screen appears.
***CIN CONFUGURATION***
1.1 Maintain Excise Registration
SAPSPRO Basic settingIndia tax on Goods Movements Logistics general Ref. IMG Maintain Excise Registrations
APPLICABLE
1.2 Maintain Company Code Settings
tax on Goods Logistics general SAP Ref. IMG SPRO Maintain Company Code Basic setting India Movements Settings
APPLICABLE
1.3 Maintain Plant Settings
SAP Ref.SPRO Basic setting India tax on Goods Movements Logistics general IMG Maintain Plant Settings
APPLICABLE
1.4 Maintain Excise Groups
SPRO BasicIndia tax on Goods Movements Logistics general SAP Ref. IMG Maintain Excise Groupssetting
APPLICABLE
1.5 Maintain Series Groups
India tax on Goods Movements Logistics general SAP Ref. IMG SPRO Maintain Series GroupsBasic setting
APPLICABLE
1.6 Maintain Excise Duty Indicators
tax on Goods Logistics general SAP Ref. IMG SPRO Maintain Excise Duty Basic setting India Movements Indicators
APPLICABLE
1.7 Maintain Sub transaction Type with Text
India tax on Goods Movements Logistics general SAP Ref. IMG SPRO Maintain Sub transaction Type with TextBasic setting
APPLICABLE
1.8 Determination of Excise Duty
tax Logistics general SAP Ref. IMG SPRO Select Tax Calculation Determination of Excise DutyIndia on Goods Movements Procedure
APPLICABLE
1.9 Maintain Excise Defaults
SAP Ref.SPRO Determination of ExciseIndia tax on Goods Movements Logistics general IMG Maintain Excise DefaultsDuty
APPLICABLE
1.10 Condition-Based Excise Determination
tax on Goods Logistics general SAP Ref. IMG SPRO Define Tax Code for Condition-Based Excise DeterminationIndia Movements Purchasing Documents
APPLICABLE
1.11 Condition-Based Excise Determination
tax on Goods Logistics general SAP Ref. IMG SPRO Assign Tax Code to Condition-Based Excise DeterminationIndia Movements Company Codes
APPLICABLE
1.12 Classify Condition Types
SAPSPRO Condition-BasedIndia tax on Goods Movements Logistics general Ref. IMG Classify Condition TypesExcise Determination
APPLICABLE
1.13 Maintain Chapter IDs
tax on Goods Logistics general SAP Ref. IMG SPRO Maintain Chapter ids Master dataIndia Movements
APPLICABLE
1.14 Assign Users to Material Master Screen Sequence for Excise Duty
SPRO Master dataIndia tax on Goods Movements Logistics general SAP Ref. IMG Assign Users to Material Master Screen Sequence for Excise Duty
APPLICABLE
1.15 Specify Excise Accounts per Excise Transaction
tax on Goods Logistics general SAP Ref. IMG SPRO Specify Excise Accounts per Excise Account determinationIndia Movements Transaction
APPLICABLE
1.16 Specify G/L Accounts per Excise Transaction
tax on Goods Logistics general SAP Ref. IMG SPRO Specify G/L Accounts per Excise Account determinationIndia Movements Transaction
APPLICABLE
1.17 Incoming Excise Invoices
SAPSPRO BusinessIndia tax on Goods Movements Logistics general Ref. IMG Incoming Excise InvoicesTransactions
APPLICABLE
1.18 Define Processing Modes Per Transaction
Logistics general SAP Ref. IMG SPRO Define Processing Modes Business TransactionsIndia tax on Goods Movements Per Transaction
APPLICABLE
1.19 Define Reference Documents Per Transaction
tax on Goods Logistics general SAP Ref. IMG SPRO Define Reference Documents Per Business TransactionsIndia Movements Transaction
APPLICABLE
1.20 Maintain Rejection Codes
SAPSPRO BusinessIndia tax on Goods Movements Logistics general Ref. IMG Maintain Rejection CodesTransactions
APPLICABLE
1.21 Specify Which Movement Types Involve Excise Invoices
Logistics SAP Ref. IMG SPRO Specify Which Business TransactionsIndia tax on Goods Movementsgeneral Movement Types Involve Excise Invoices
APPLICABLE
1.22 Outgoing Excise Invoices
tax on Goods Logistics general SAP Ref. IMG SPRO Assign Outgoing Excise Invoices Business TransactionsIndia Movements Billing Types to Delivery Types
APPLICABLE
1.23 Maintain Default Excise Groups and Series Groups
Logistics general SAP Ref. IMG SPRO Outgoing Excise Invoices Business TransactionsIndia tax on Goods Movements Maintain Default Excise Groups and Series Groups
APPLICABLE
1.24 Subcontracting Attributes
tax on Logistics general SAP Ref. IMG SPRO Subcontracting Subcontracting Business TransactionsIndia Goods Movements Attributes
APPLICABLE
1.25 Maintain Movement Type Groups
SPRO BusinessIndia tax on Goods Movements Logistics general SAP Ref. IMG Subcontracting SubcontractingTransactions Attributes
APPLICABLE
1.26 Utilization Determination
SAPSPRO BusinessIndia tax on Goods Movements Logistics general Ref. IMG Utilization UtilizationTransactions Determination
APPLICABLE
1.27 Specify SAP script Forms
SPRO BusinessIndia tax on Goods Movements Logistics general SAP Ref. IMG Specify SAP script Excise RegistersTransactions Forms
APPLICABLE
1.28 Number Ranges
SAP Ref. IMG SPRO Number ToolsIndia tax on Goods MovementsLogistics general Ranges
APPLICABLE
1.29 Message Control
SAP Ref. IMG SPRO Message ToolsIndia tax on Goods MovementsLogistics general Control
APPLICABLE
J1I2
Prepare a sales tax register
J1I3
Create outgoing excise invoices in batches
J1I5
Update the RG 1 and Part I registers
J1IEX
Incoming Excise Invoices (central transaction)
J1IEX_C
Capture an incoming excise invoice (excise clerk)
J1IEX_P
Post an incoming excise invoice (excise supervisor)
J1IF01
Create a subcontracting challan
J1IF11
Change a subcontracting challan
J1IF12
Display a subcontracting challan
J1IF13
Complete, reverse, or recredit a subcontracting challan
J1IFQ
Reconcile quantities for subcontracting challan
J1IFR
List subcontracting challan
J1IH
Make a CENVAT adjustment posting
J1IIN
Create an outgoing excise invoice
J1IJ
Assign excise invoices to a delivery for sales from depots
J1INJV
Adjust withholding tax Item
J1INREP
Reprint a withholding tax certificate for a vendor
J1IQ
Year-End Income Tax Depreciation Report
J1IR
Download register data
J1IS
Process an excise invoice (outgoing) for other movements
J1IU
Process exemption forms
J1IW
Verify and post an incoming excise invoice
J1IX
Create an incoming excise invoice (without reference to purchase order)
J2I8
Transfer excise duty to CENVAT account
J2IU
Remit excise duty fortnightly
J2I9
Monthly CENVAT return
J1IG
Excise invoice entry at depot
J1IGA
Create additional excise entry at depot
J2I5
Extract data for excise registers
J2I6
Print excise registers
regards,
indranil -
Conversion exit for project definition
Hi
I have created a generic extractor to get some data of table PRPS. The project-definition number in this table is in field PSPHI. When you display the result of the extractor in the extractor checker (RSA3) the correct number (e.g. PG5707) is showing, however, when it comes into BW, it is showing the internal number (e.g. 000002). In BW I use this field to populate 0PROJECT, but due to the internal number being sent, I cant use it.
Can anyone please tell me what conversion exit I can call in my extractor to get the external number?
I also notice in SE16 for this table there is a selection in the user parameters to tick under the "Format" section in the data browser tab. If it is not selected, it shows the internal number, but if selected, the external number is displayed. I want to do this in my extractor.
Thanks
KarinHello Karin,
Have a look at these OSS
SAP Note 776990 Conversion exits with string parameters
SAP Note 756662 RSAR 196:InfoObj. contains val. which is not conversion exit
SAP Note 925589 P8:SDL:New DS:Possible problems w/
SAPI conversion exit call
SAP Note 843164 P27:SDL: Problems with conversion exits in the selection tab
SAP Note 557148 Executing conversion exits
SAP Note 497043 P6:SDL:Scheduler selections in fields with conversion exits
SAP Note 1034798 P13:SDL:New DataSource uses incorrect conversion exit
SAP Note 681931 Error due to conversion exits during the file upload
SAP Note 1003431 Error in target fields with conversion exits
SAP Note 374997 SDL: Conversion exits: ABPSN, ABPRJ, ABPSP and MATN1
[Thanks|http://chandranonline.blogspot.com/]
[Chandran|http://chandranonline.blogspot.com/] -
Hi,
Please explain the full excise process, setting, todes for sap system...Also provide tables and reports if available...
Help will be definetly rewarded...
Thanks
Edited by: P P on Aug 29, 2008 8:53 AMWhat is CIN?
CIN Means Country India Version
In Indian Taxing procedure, Excise Duty plays a vital role in manufacturing cenariou2019s. Excise related configuration is known as CIN configuration. CIN Configuration is a topic in itself.
Some info on CIN Configuration (it may not appear as understandable below, but if you check on screen, it will be understood better)
Country Version India comes with four pricing procedures as follows:
- JINFAC (Sales from manufacturing plants)
- JINEXP (Export sales)
- JINDEP (Sales from depots)
- JINSTK (Stock transfers
CIN: IMG > Logistics - General > Tax on Goods Movement > India > Basic Settings > Maintain Excise Registrations
In this IMG activity, you maintain the data relating to your excise registrations.
- Enter each of your excise registrations, specifying a four-character code for each Excise Registration Ids
In this activity, you maintain excise registration IDs. You create one ID for each of your business's excise registrations.
- For each excise registration in your business create a registration ID, and state:
- Which taxes the registration covers (additional excise duty, special excise duty, and cess) Fields for any taxes that are not covered will be hidden in transactions involving excise duty.
- The maximum number of items to be printed on each excise invoice
- Whether you are allowed partial CENVAT credits
Maintain Registration ID NUMBER, Excise code number, excise registration number
ECC Number: Specifies the organization's ECC number.
Excise Registration Number: A number assigned to each premises or location that has registered as a manufacturer with the excise authorities.
Every entity with an excise registration number is required to keep its own excise books.
Excise range: Specifies the excise range in whose area the excise registration is located.
Excise Division: Specifies the excise division in whose area the excise registration is located.
Excise Collectorate: The code of the excise collectorate in whose area the excise registration is located.
Indicator for confirming, AED usage Additional Excise duty Percentage.
These are livable under the additional duties of excise act. These duties are in addition to basic excise duty and special excise duty. Example - Additional Excise duty is livable in case of textile products, tobacco and sugar.
Similarly for SED CESS Number of Items in Excise Invoice Shows the maximum number of line items that the authorities allow per excise invoice.
Dependencies - This information is used when you create an excise invoice in Sales and Distribution (SD) for factory sales and for other movements. This information is used to split the transfer postings' items into multiple subcontracting challans.
Excise register set description: Description of the excise registers set.
Partial CENVAT Credit: Indicates that the excise registration ID is allowed to credit only a portion of its input excise duty to its CENVAT account
Dependencies - When you post a goods receipt, the system splits the input excise duty on the material into its deductible and nondeductible amounts. It posts the deductible duty to the appropriate CENVAT account, and adds the nondeductible duty to the material value.
This information is also shown when you post the vendor's excise invoice.
Maintain Company Code Settings.
In this IMG activity, you maintain the data relating to your company codes.
Document Type for CENVAT Postings.
It controls, which document type the system uses when making CENVAT postings in Financial Accounting (FI). Here ED is document type for cenvat posting.
Indicator for providing debit account overwriting
Debit Account Overwrite Indicator. X - Indicates debit accounts can be overwritten. Use In excise journal voucher transaction. It provides the flexibility to the user to enter the debit account of his choice depending on the nature of transaction.
Automatic balance Indicator - Excise year start month. The calendar month marking the beginning of the excise year. This start month represents the month for the start of the excise invoice number range. The month 04 is entered here indicating April of the calendar year as the start month for excise invoices. Any change by the Excise authorities regarding start month should be taken care of by an entry in this field and initialization.
Excise invoice selection procedure :Excise invoice selection type. To indicate the method opted by the company for selecting the excise invoice. It can be either earliest or latest invoices that were received. Number of excise invoices to be selected Indicates the number of excise invoices that needs to be selected in the excise invoice selection.
Days to be considered for excise invoice selection Number of days from document date for excise invoice selection.
Example - If the value of this field is 20 and today is 28-03-97. The excise invoice selection will show the related invoices only for the period 08-03-97 to 28-03-97.
Document type for TDS FI posting: Financial accounting document type for TDS posting.
Document type for FI posting on Utilisation Financial accounting document type for TDS posting.
Indicator for item level excise duty round off - This indicator is to be used for deciding whether Item level excise
duty amount rounding off is required during procurement cycle. If marked 'X' then the excise duty amount will be rounded off to the nearest rupee at the Purchase order level. This will not round off the CENVAT credit to be taken. If the duty amount is less than one rupee then no rounding is done
Rounding off of Excise duty for outgoing excise invoice - You can round off the Excise amount to be paid during an outgoing
Excise invoice by marking this indicator as 'X'. The rounding is done at the item level for each item where the amount is greater than 1 Rupee.
Immediate Credit on Capital Goods - Instructs the system, when you verify a goods receipt for capital goods, to immediately post half of the input excise duty to the appropriate CENVAT accounts. The rest is posted the CENVAT on hold account, for use in the following year.
CVD Clearing Account - Specifies which G/L account the system credits when you take a CENVAT credit on countervailing duty in the Incoming Excise Invoices transaction.
Exchange rate type - Key representing a type of exchange rate in the system.
- You enter the exchange rate type to store different exchange rates. Example - You can use the exchange rate type to define a buying rate, selling rate, or average rate for translating foreign currency amounts. You can use the average rate for the currency translation, and the bank buying and selling rates for valuation of foreign currency amounts.
Exchange rate type to be used for Export excise duty converts - When you are creating an Excise invoice for export sales then the exchange rate for duty calculation will be picked up using this Exchange rate type.
Maintain Plant Settings - In this IMG activity, you maintain excise information relating to your plants.
Plant Settings - In this activity, you maintain excise information relating to your plants.
For each plant:
- Specify whether it is a manufacturing site or a depot.
- Assign it an excise registration ID. - You can assign the same ID to more than one plant, if required.
Depot - Indicates that the plant in question is a depot. - Depots are required to prepare register RG 23D, and follow different procedures for goods receipt and invoice generation.
- Number of goods receipt per excise invoice.
- Multiple GR for one excise invoice, Single credit
- Multiple GR for one excise invoice, multiple credit
Maintain Excise Groups - In this IMG activity, you define your excise groups. For each excise group, you can also control how various excise invoice transactions will work.
Excise Groups - In this activity, you define excise groups. An excise group allows you to maintain a separate set of excise registers and excise accounts. The RG 23A, RG 23C and PLA serial numbers are created for an excise group.
Recommendation - Under normal circumstances, excise authorities require every business to maintain only one set of excise registers and one set of accounts. But through exemption from the authorities, multiple books can be maintained.
If your company has only one set of excise registers, then you need to maintain only one excise group.
1. Create one excise group for each set of registers that you need to keep.
2. Assign the excise groups to plants.
3. Maintain whether this Excise group is for a depot or not.
If you receive only one consignment for an Excise challan then you can leave GR's per EI as blank. If you receive multiple GR's for a given Excise challan and would like to avail multiple credit mark the GRs per EI as 'Multiple GR's for one excise invoice, multiple credit'. Alternatively if you want to availa the credit only after all the goods receipts have been made mark it as ' Multiple GR for one excise invoice, single credit'.
4. If you want to automatically create Excise invoice during Sales cycle at the time of billing the tick the indicator 'Create EI'
5. During depot sales if you do not want to do RG23D selection and posting separately and would like to complete RG23D selection in one step mark the indicator 'RG23D Auto post'. This will post the selected records into RG23D automatically. You cannot cancel the selection later.
6. If the indicator 'Default GR qty' is marked system will default the Excise challan quantity on to the Goods receipt if the Excise invoice number is given in the pop-up.
7. If the indicator 'Folio no create' is marked system will generate Folio numbers for RG23D during receipt of excise invoice into depot.
8. 'Automatic posting' when ticked will post the Excise invoice other movements automatically along with creation in single step.
9. 'Create Part1 for Block Stock' when marked will create a Part1 during the receipt of material into Blocked stock .
10. 'Create Part1 for STO' when marked will create a Part1 during the receipt of material through inter plant transfers.
11. 'Create Part1 for consumption stock' when marked will create a Part1 during the receipt of material into consumption stock. Excise Group Governs which set of excise registers a business transaction will be included in.
Following is the relation between excise group, plant and registration. - In define excise groups in Customizing.
Then, in transactions involving excise duty, for example, when you post a vendor's excise invoice, you specify which excise group you are using. This information tells the system which G/L accounts to post the excise to. At the end of the period, when you come to prepare your excise registers, you create different sets for each excise group.
Indicates that the plant in question is a depot. - Depots are required to prepare register RG 23D, and follow different procedures for goods receipt and invoice generation.
- GR Per Excise Invoice
- Multiple GR for one excise invoice , Multiple credit
- Multiple GR for one excise invoice , Single Credit
Create Excise Invoice Automatically - Instructs the system to automatically create a Sales and Distribution (SD) excise invoice immediately you create a commercial invoice or a pro forma invoice.
The excise invoice is created in the background. - If you want to make use of this function, you must also define the
default plant, excise group, and series groups in Customizing for Sales and Distribution (SD), by choosing Excise Group - Series Group Determination.
RG23D Sales Creation and posting option - RG23D Automatic Option if selected will create Depot excise invoice by posting the selection of excise invoices in single step. If this is not selected then you need to separately do RG23D selection
followed by PGI and then RG23D verification and posting. If you need automatic posting of RG23D selection then the Post Goods Issue should have been completed before running RG23D selection.
Default excise qty in GR - If this indicator is ticked then while doing Goods Receipt using 'MB01' system will default the excise invoice quantity on to the Goods receipt document.
Folio number for depo Posting - If this indicator is marked then while creating Excise invoice for other movements system automatically does the Verify and Post. You need not separately Post the excise invoice
Also we can set indicator for creation of part 1 for:
- Blocked stock
- Stock transport order
- Consignment stock
Maintain Series Group - In this IMG activity, you define the different excise series groups within your company. Series groups allow you to maintain multiple number ranges for the outgoing excise documents. Based on excise regulations and exemptions from the authorities you can maintain multiple number series for outgoing documents. But each of these series has to be declared to the excise authorities.
- Define excise series groups based on type of outgoing document
- Assign series group to excise registration ID
- If no financial postings are required for an Excise invoice in this seris group then you tick the 'No utilization' indicator.
- If the CENVAT has to be paid immediately and you need not wait for the Fort nightly payment then mark the 'Immediate Utilization' Iindicator. Example - You could define two series groups, group 001 for excise invoices, and group 002 for 57 F4 documents.
- No account postings for CENVAT in sales cycle
- No utilization Flag
If you do not need any CENVAT utilization for an excise invoice but would like to just generate an excise invoice then you need to mark this indicator.
If the flag is checked then system will create an Excise invoice in the given Series group but there will not be any account postings or Part2 postings.
Immediate Utilization of CENVAT - Specifies that when you create an excise invoice, the system immediately pays the amount from CENVAT and creates the Part II entry. Such invoices will not be listed for fortnightly utilization.
If you have both fortnightly and immediate utilization for the same excise group, the account determination within CIN IMG should point to the ED interim account.
Account determination for immediate payment will be done exactly the same as being done for fortnightly utilization program.
Maintain Excise Duty Indicators - In this IMG activity, you maintain the excise duty indicators.
IMG > Logistics - General > Tax On Goods Movement > India > Basic Settings > Determination of Excise Duty > Select Tax Calculation Procedure
In this IMG activity, you specify which tax procedure you want to use for determining excise duties and sales taxes on input materials in India.
- If you use condition-based excise determination, use a copy of the tax procedure TAXINN.
- If you use formula-based excise determination, use a copy of the tax procedure TAXINJ.
This tax procedure also supports condition-based excise determination, so that you can work with both concurrently.
We strongly recommend that new customers use condition-based excise determination. Note that once you have started using a tax procedure, you cannot switch to another one, otherwise you will not be able to display old documents.
Maintain Excise Defaults - In this IMG activity, you define which tax procedure and pricing condition types are used in calculating excise taxes using formula-based excise determination.
If you use condition-based excise determination, fill out the CVD cond. field and leave all the others blank.
If you use formula-based excise determination, fill out all of the fields as follows:
- Enter the tax procedure and the pricing conditions that are relevant for excise tax processing.
- Specify the purchasing and sales conditions types used for basic excise duty, additional excise duty, special excise duty, and cess.
- Specify the conditions in the sales order that are used for excise rates.
- Specify the countervailing duty condition type used for import purchase orders.
See also : SAP Library -> Logistics -> Country Versions -> Asia-Pacific -> India -> Materials Management (MM) -> Condition-Based Excise Determination and -> Formula-Based Excise Determination.
IMG > Logistics - General > Tax On Goods Movement > India > Basic Settings > Determination of Excise Duty >
Condition-Based Excise Determination
When you enter a purchasing document, for example, a purchase order, the R/3 System automatically calculates the applicable excise duties using the condition technique.
Features : The standard system comes with two tax calculation procedures. TAXINN is only supports condition-based excise determination, whereas TAXINJ supports condition-based excise determination and formula-based excise determination. Both tax procedures contain condition types that cover all of the excise duties and sales taxes applicable.
Since the exact rates of excise duty can vary on a large number of factors, such as which vendor you purchase a material from, or which chapter ID the vendor stocks the material under, you create condition records for every sort of excise duty.
When you come to enter a purchasing document, the system applies the excise duty at the rates you have entered in the condition records.
Customizing : Make the settings in Customizing Basic -> India -> for Logistics u2013 General, by choosing Taxes on Goods Movements Account -> Excise Duties Using Condition Technique and u2026-> Settings Determination.
These activities include one activity where you define a tax code for condition-based excise determination.
Master Data - Create condition records for all excise duties that apply, and enter the tax code for condition-based excise determination in each.
Day-to-Day Activities - When you enter a purchase order or other purchasing document, enter the tax code for condition-based excise determination in each line item. The system then calculates the excise duties using the condition records you have created.
When the ordered materials arrive, you post the goods receipt and the excise invoice. The system posts the excise duty to the appropriate accounts for deductible input taxes when you enter the excise invoice.
Creating Condition Records for Excise Duty
1. In the command field, enter FV11 and choose .
2. Enter the condition type that you want to create a condition record for and choose .
The Key Combination dialog box appears.
3. Select the combination of objects that you want to create the condition record for. On the dialog box, Control Code means "chapter ID." So, for example, to create a condition record for a tax that applies to a combination of country, plant, and chapter ID, select Country/Plant/Control Code.
4. Choose .
5. Enter data as required. - In the Tax Code field, enter the dummy tax code that you have defined.
6. Save the condition record.
Formula-Based Excise Determination - When you execute a business transaction involving materials that are subject to excise duty, the system automatically calculates the duty for you.
In order for the system to be able to determine which rate of excise duty to apply, you must have maintained all the data on the Excise Rate Maintenance screen, which you can Master Data®access from the SAP Easy Access screen by choosing Indirect Taxes Excise Rate Maintenance.
You maintain the following types of data:
- Plant master data
You assign each of your plants an excise duty indicator. You can use the same indicator for all the plants with the same excise status from a legal point of view, such as all those that are in an exempt zone. See also the information about manufacturers that are only entitled to deduct a certain portion of the duty (see Partial CENVAT Credit).
- Vendor master data
For each of your vendors with the same excise status from a legal perspective, you define an excise duty indicator. You must also specify the vendor type u2013 for example, whether the vendor is a manufacturer, a depot, or a first-stage dealer. You must also stipulate if the vendor qualifies as a small-scale industry. For each permutation of plant indicator and vendor indicator, you then create a final excise duty indicator.
- Customer master data
Similarly, you assign the same excise duty indicator to each of your customers that share the same legal excise status.
Again, for each permutation of plant indicator and customer indicator, you then create a final excise duty indicator.
- Material master data
Each material is assigned a chapter ID.
- Excise tax rate
For every chapter ID and final excise duty indicator, you maintain the rate of excise duty.
If your business only qualifies for partial CENVAT credit, you must customize your system accordingly.
Let us consider an example to illustrate how the system determines which rate of excise duty to apply to a material. Assume you are posting a sale of ball bearings to a customer. The system automatically determines the rate of excise duty as follows:
1. Looks up the customer master data to see what status you have assigned the customer.
Let's assume you've assigned the customer status 3.
2. Looks up the plant master data to see what status you have assigned the plant. Similarly, your plant has status 2.
3. The system looks up the table under Excise Indicator for Plant and Customer to see what the final excise duty indicator is for customer status 3 and plant status 2: It is 7.
4. The system determines the chapter ID of the ball bearing for the plant.
Letu2019s assume the chapter ID at plant for the ball bearings is 1000.01.
5. Finally, the system looks up the table under Excise Tax Rate to see what rate of duty applies to chapter ID 1000.01 under
status 7.
Define Tax Code for Purchasing Documents - In this IMG activity, you define a tax code for the purposes of calculating excise duty when you enter purchasing documents. Only carry out this activity if you use condition-based excise
determination.
- Create a new tax code, and set the tax code type to V (input tax). Do not make any other settings for it.
- Assign Tax Code to Company Codes
In this IMG activity, assign the tax code for purchasing documents to the company codes where it will be used.
Only carry out this activity if you use condition-based excise determination.
Classify Condition Types - In this IMG activity, you specify which condition types you use for which sort of tax. Note that this only applies to condition types that you use with the new excise determination method. The system uses this information when you create a document from another one. For example, when you enter an incoming excise invoice from a
purchase order, or when you create an outgoing excise invoice from a sales order, the system determines the various excise duties in the excise invoice using the information that you have entered here. In addition, when you create a purchasing document, the system only uses the condition types that you enter here.
- For taxes on purchases, use the condition types contained in the tax procedure.
- For taxes on sales, use the condition types contained in the pricing procedures.
The standard system comes with sample settings for the tax calculation procedures and pricing procedures.
Use these settings as a basis for your own.
IMG > Logistics - General > Tax On Goods Movement > India > Account Determination
Define G/L Accounts for Taxes - In this IMG activity, you specify which G/L accounts you will use to record which taxes.
Requirements - You have set up G/L accounts for each of the processing keys listed below.
- Assign an account to each of the following posting keys. The accounts for VS1, VS2, and VS3 are used as clearing accounts during excise invoice verification.
- VS1 (basic excise duty)
- VS2 (additional excise duty)
- VS3 (special excise duty)
- VS5 (sales tax setoff)
- MWS (central sales tax)
- MW3 (local sales tax)
- ESA (service tax)
- ESE (service tax expense)
Specify Excise Accounts per Excise Transaction - In this IMG activity, you specify which excise accounts (for excise
duty and CENVAT) are to be posted to for the various transaction types. Enter all the accounts that are affected by each transaction type. If you use sub transaction types, enter the accounts for each sub transaction type as well.
Transaction type UTLZ is used for determining accounts only while posting excise JVs and also if the payment of excise duty has to be done fortnightly. The fortnightly CENVAT payment utility picks up the credit side accounts from the transaction types of GRPO, EWPO, and TR6C for determining the CENVAT and PLA accounts. There is no separate transaction type for fortnightly payment.
Example:
- Excise TT DC ind Account name
- GRPO CR CENVAT clearing account
- GRPO CR RG 23 BED account
- GRPO DR CENVAT on hld account
Specify G/L Accounts per Excise Transaction - In this IMG activity, you assign the excise and CENVAT accounts to G/L
accounts. When you come to execute the various transactions, the system determines which G/L accounts to post to by looking at the:
- Excise group
- Company code
- Chart of accounts
Furthermore, if you want separate account determination settings within an excise group, you can also use sub transaction types.
Requirements
You have already:
- Defined the G/L accounts
- Defined the excise groups
- Maintained the transaction accounts
Activities - For each excise group, assign the excise and CENVAT accounts to G/L accounts. For most businesses, one set of accounts will suffice for all transactions.
Note : you need not remit the CENVAT to the excise department immediately, so maintain the credit account for transaction type DLFC as an excise duty interim account. This will be set off when you remit the duty. Config setting needed to be done in order to get the Excise Details Screen in Material Master.
Even though this functionality is available in enterprise version, a small configuration step has to be made in Screen Sequences for Material Master.
Following document helps you to do this configuration.
- Material Master à Logistics General
1. Go to IMG Define Structure of Data Screen for each Configuring the Material master Screen Sequence.
2. Select your screen sequence. Usually it would be 21. Select the same and click on Data Screen in the left frame.
3. Once the data screens are exhibited, select data screen no. 15, ie. SSq. 21and Scrn 15, which is u201CForeign Trade: Import Datau201D. Select the same and click on Sub screens in the left frame.
4. Go to the last sub screen i.e. 21-15-6 - SAPLMGD1- 0001 and select the same. Click on tab view sub screen and ensure that the sub screen is blank.
5. Now in the last sub screen i.e. no.6 you delete SAPLMGD1 u2013 0001 and instead add SAPLJ1I_MATERIAL_MASTER and in the screen no. 2205.
6. Save the setting.
7. Create a Material Master and check whether in Screen Foreign Trade
u2013 Import, Excise related sub screen appears.
***CIN CONFUGURATION***
1.1 Maintain Excise Registration
SAPSPRO Basic settingIndia tax on Goods Movements Logistics general Ref. IMG Maintain Excise Registrations
APPLICABLE
1.2 Maintain Company Code Settings
tax on Goods Logistics general SAP Ref. IMG SPRO Maintain Company Code Basic setting India Movements Settings
APPLICABLE
1.3 Maintain Plant Settings
SAP Ref.SPRO Basic setting India tax on Goods Movements Logistics general IMG Maintain Plant Settings
APPLICABLE
1.4 Maintain Excise Groups
SPRO BasicIndia tax on Goods Movements Logistics general SAP Ref. IMG Maintain Excise Groupssetting
APPLICABLE
1.5 Maintain Series Groups
India tax on Goods Movements Logistics general SAP Ref. IMG SPRO Maintain Series GroupsBasic setting
APPLICABLE
1.6 Maintain Excise Duty Indicators
tax on Goods Logistics general SAP Ref. IMG SPRO Maintain Excise Duty Basic setting India Movements Indicators
APPLICABLE
1.7 Maintain Sub transaction Type with Text
India tax on Goods Movements Logistics general SAP Ref. IMG SPRO Maintain Sub transaction Type with TextBasic setting
APPLICABLE
1.8 Determination of Excise Duty
tax Logistics general SAP Ref. IMG SPRO Select Tax Calculation Determination of Excise DutyIndia on Goods Movements Procedure
APPLICABLE
1.9 Maintain Excise Defaults
SAP Ref.SPRO Determination of ExciseIndia tax on Goods Movements Logistics general IMG Maintain Excise DefaultsDuty
APPLICABLE
1.10 Condition-Based Excise Determination
tax on Goods Logistics general SAP Ref. IMG SPRO Define Tax Code for Condition-Based Excise DeterminationIndia Movements Purchasing Documents
APPLICABLE
1.11 Condition-Based Excise Determination
tax on Goods Logistics general SAP Ref. IMG SPRO Assign Tax Code to Condition-Based Excise DeterminationIndia Movements Company Codes
APPLICABLE
1.12 Classify Condition Types
SAPSPRO Condition-BasedIndia tax on Goods Movements Logistics general Ref. IMG Classify Condition TypesExcise Determination
APPLICABLE
1.13 Maintain Chapter IDs
tax on Goods Logistics general SAP Ref. IMG SPRO Maintain Chapter ids Master dataIndia Movements
APPLICABLE
1.14 Assign Users to Material Master Screen Sequence for Excise Duty
SPRO Master dataIndia tax on Goods Movements Logistics general SAP Ref. IMG Assign Users to Material Master Screen Sequence for Excise Duty
APPLICABLE
1.15 Specify Excise Accounts per Excise Transaction
tax on Goods Logistics general SAP Ref. IMG SPRO Specify Excise Accounts per Excise Account determinationIndia Movements Transaction
APPLICABLE
1.16 Specify G/L Accounts per Excise Transaction
tax on Goods Logistics general SAP Ref. IMG SPRO Specify G/L Accounts per Excise Account determinationIndia Movements Transaction
APPLICABLE
1.17 Incoming Excise Invoices
SAPSPRO BusinessIndia tax on Goods Movements Logistics general Ref. IMG Incoming Excise InvoicesTransactions
APPLICABLE
1.18 Define Processing Modes Per Transaction
Logistics general SAP Ref. IMG SPRO Define Processing Modes Business TransactionsIndia tax on Goods Movements Per Transaction
APPLICABLE
1.19 Define Reference Documents Per Transaction
tax on Goods Logistics general SAP Ref. IMG SPRO Define Reference Documents Per Business TransactionsIndia Movements Transaction
APPLICABLE
1.20 Maintain Rejection Codes
SAPSPRO BusinessIndia tax on Goods Movements Logistics general Ref. IMG Maintain Rejection CodesTransactions
APPLICABLE
1.21 Specify Which Movement Types Involve Excise Invoices
Logistics SAP Ref. IMG SPRO Specify Which Business TransactionsIndia tax on Goods Movementsgeneral Movement Types Involve Excise Invoices
APPLICABLE
1.22 Outgoing Excise Invoices
tax on Goods Logistics general SAP Ref. IMG SPRO Assign Outgoing Excise Invoices Business TransactionsIndia Movements Billing Types to Delivery Types
APPLICABLE
1.23 Maintain Default Excise Groups and Series Groups
Logistics general SAP Ref. IMG SPRO Outgoing Excise Invoices Business TransactionsIndia tax on Goods Movements Maintain Default Excise Groups and Series Groups
APPLICABLE
1.24 Subcontracting Attributes
tax on Logistics general SAP Ref. IMG SPRO Subcontracting Subcontracting Business TransactionsIndia Goods Movements Attributes
APPLICABLE
1.25 Maintain Movement Type Groups
SPRO BusinessIndia tax on Goods Movements Logistics general SAP Ref. IMG Subcontracting SubcontractingTransactions Attributes
APPLICABLE
1.26 Utilization Determination
SAPSPRO BusinessIndia tax on Goods Movements Logistics general Ref. IMG Utilization UtilizationTransactions Determination
APPLICABLE
1.27 Specify SAP script Forms
SPRO BusinessIndia tax on Goods Movements Logistics general SAP Ref. IMG Specify SAP script Excise RegistersTransactions Forms
APPLICABLE
1.28 Number Ranges
SAP Ref. IMG SPRO Number ToolsIndia tax on Goods MovementsLogistics general Ranges
APPLICABLE
1.29 Message Control
SAP Ref. IMG SPRO Message ToolsIndia tax on Goods MovementsLogistics general Control
APPLICABLE
J1I2
Prepare a sales tax register
J1I3
Create outgoing excise invoices in batches
J1I5
Update the RG 1 and Part I registers
J1IEX
Incoming Excise Invoices (central transaction)
J1IEX_C
Capture an incoming excise invoice (excise clerk)
J1IEX_P
Post an incoming excise invoice (excise supervisor)
J1IF01
Create a subcontracting challan
J1IF11
Change a subcontracting challan
J1IF12
Display a subcontracting challan
J1IF13
Complete, reverse, or recredit a subcontracting challan
J1IFQ
Reconcile quantities for subcontracting challan
J1IFR
List subcontracting challan
J1IH
Make a CENVAT adjustment posting
J1IIN
Create an outgoing excise invoice
J1IJ
Assign excise invoices to a delivery for sales from depots
J1INJV
Adjust withholding tax Item
J1INREP
Reprint a withholding tax certificate for a vendor
J1IQ
Year-End Income Tax Depreciation Report
J1IR
Download register data
J1IS
Process an excise invoice (outgoing) for other movements
J1IU
Process exemption forms
J1IW
Verify and post an incoming excise invoice
J1IX
Create an incoming excise invoice (without reference to purchase order)
J2I8
Transfer excise duty to CENVAT account
J2IU
Remit excise duty fortnightly
J2I9
Monthly CENVAT return
J1IG
Excise invoice entry at depot
J1IGA
Create additional excise entry at depot
J2I5
Extract data for excise registers
J2I6
Print excise registers
regards
indranil -
Hi Experts,
M new to SAP recently while saving a query i got some error in my system, seaching for the anser in SDN i found some link in sap marketplace ie sap service.
now my question is can many people register to sap service market place with same instalation number?
answer will make my base clear about SAP installation and its work, please helpabajames,
Registration in the support marketplace is against a customer installation number and it is charged.
You can have as many registrations as required against a customer installation number - but then will have to pay for the same.
Also this registration is usually done by a designated person in the company who administers the Customer Installation / the installation is registered in his/her name.
Arun -
XI RFC-Sender not registred at SAP Gateway
Hi XI specialists,
i have configured a rfc-sender within XI using the blog: /people/michal.krawczyk2/blog/2005/03/29/configuring-the-sender-rfc-adapter--step-by-step
but in the transacion SMGW in my R/3-System (CRM5.0) there is no program id registred. The RFC-Settings:
RFC-Sender
GW-Host = SAP-BusiniessSystem (crmhost01)
GW-Service = SAP-BusinessSystem-Sysno(sapgw12)
ProgID = BS_CRM_LISTENER
Any Ideas ?
In XI-Monitoring: component_monitoring>Adapterengine>communication channel i can not find my new RFC-Sender....
Thanks.
Best regards,
André
Message was edited by:
André BorrmannHi,
Know sounds really silly but please can you give a program id without any underscore in your name and do the test!!!
Please give IP address:
GW-Host = SAP-BusiniessSystem (crmhost01)
Q 13: What is the correct value within the field 'Application server service (Gateway)' for sender channels?
A: This value has to be the name of the service port which is running the gateway. Normally this will be a name like sapgwXX, where XX is the system number of the particular system. This value also can be looked up in the gateway monitor. Open transaction SMGW and choose Goto -> Parameters -> Display. Beneath Attributes there will be the entries 'gateway hostname' and 'gateway service'.#
so is your GW-Service = SAP-BusinessSystem-Sysno(sapgw12) coreect?
From your server name it looks as though the system number is 01.
regards
vijaya
Message was edited by:
vijaya kumari
Message was edited by:
vijaya kumari -
Hi, I'm triying to add a Portlet producer form SAP, an when I try to connect I get this Exception,
oracle.portlet.client.container.PortletException: java.lang.RuntimeException: Error converting the following SOAP element to JAXB package 'oracle.portlet.wsrp.v1':
node: ns0:getServiceDescriptionResponse = null
attribute: xmlns:SOAP-ENV = http://schemas.xmlsoap.org/soap/envelope/
attribute: xmlns:ns0 = urn:oasis:names:tc:wsrp:v1:types
attribute: xmlns:xsd = http://www.w3.org/2001/XMLSchema
attribute: xmlns:env = http://schemas.xmlsoap.org/soap/envelope/
attribute: xmlns:xsi = http://www.w3.org/2001/XMLSchema-instance
node: ns0:requiresRegistration = null
node: #text = true
node: ns0:offeredPortlets = null
node: ns0:portletHandle = null
node: #text = pop_np:pop_scoped%pcd:portal_content/com.prueba.zprueba/ZMW_PRD_INF_PRU_PORTAL
node: ns0:markupTypes = null
node: ns0:mimeType = null
node: #text = text/html
node: ns0:modes = null
node: #text = wsrp:view
node: ns0:modes = null
node: #text = wsrp:edit
node: ns0:modes = null
node: #text = wsrp:help
node: ns0:modes = null
node: #text = wsrp:preview
node: ns0:windowStates = null
node: #text = wsrp:normal
node: ns0:windowStates = null
node: #text = wsrp:minimized
node: ns0:windowStates = null
node: #text = wsrp:maximized
node: ns0:windowStates = null
node: #text = wsrp:solo
node: ns0:locales = null
node: #text = en-US
node: ns0:groupID = null
node: #text = DEFAULT_WSRP_GROUP_NAME
node: ns0:description = null
attribute: xml:lang = en_US
attribute: resourceName = com.sap.portal.pcm.Description
node: ns0:value = null
node: #text = Informes Producción Prueba Portal
node: ns0:shortTitle = null
attribute: xml:lang = en_US
attribute: resourceName = com.sap.portal.pcm.Title
node: ns0:value = null
node: #text = Informes Producción Prueba Portal
node: ns0:title = null
attribute: xml:lang = en_US
attribute: resourceName = com.sap.portal.pcm.Title
node: ns0:value = null
node: #text = Informes Producción Prueba Portal
node: ns0:usesMethodGet = null
node: #text = false
node: ns0:defaultMarkupSecure = null
node: #text = false
node: ns0:onlySecure = null
node: #text = false
node: ns0:userContextStoredInSession = null
node: #text = false
node: ns0:templatesStoredInSession = null
node: #text = false
node: ns0:hasUserSpecificState = null
node: #text = false
node: ns0:doesUrlTemplateProcessing = null
node: #text = true
node: ns0:offeredPortlets = null
node: ns0:portletHandle = null
node: #text = pop_np:pop_scoped%pcd:portal_content/com.prueba.zprueba/TEST
node: ns0:markupTypes = null
node: ns0:mimeType = null
node: #text = text/html
node: ns0:modes = null
node: #text = wsrp:view
node: ns0:modes = null
node: #text = wsrp:edit
node: ns0:modes = null
node: #text = wsrp:help
node: ns0:modes = null
node: #text = wsrp:preview
node: ns0:windowStates = null
node: #text = wsrp:normal
node: ns0:windowStates = null
node: #text = wsrp:minimized
node: ns0:windowStates = null
node: #text = wsrp:maximized
node: ns0:windowStates = null
node: #text = wsrp:solo
node: ns0:locales = null
node: #text = en-US
node: ns0:groupID = null
node: #text = DEFAULT_WSRP_GROUP_NAME
node: ns0:description = null
attribute: xml:lang = en_US
attribute: resourceName = com.sap.portal.pcm.Description
node: ns0:value = null
node: ns0:shortTitle = null
attribute: xml:lang = en_US
attribute: resourceName = com.sap.portal.pcm.Title
node: ns0:value = null
node: #text = TEST
node: ns0:title = null
attribute: xml:lang = en_US
attribute: resourceName = com.sap.portal.pcm.Title
node: ns0:value = null
node: #text = TEST
node: ns0:usesMethodGet = null
node: #text = false
node: ns0:defaultMarkupSecure = null
node: #text = false
node: ns0:onlySecure = null
node: #text = false
node: ns0:userContextStoredInSession = null
node: #text = false
node: ns0:templatesStoredInSession = null
node: #text = false
node: ns0:hasUserSpecificState = null
node: #text = false
node: ns0:doesUrlTemplateProcessing = null
node: #text = true
node: ns0:requiresInitCookie = null
node: #text = perGroup
at oracle.adfinternal.model.portlet.manager.PortletProviderManager.registerWSRPProducer(PortletProviderManager.java:2024)
at oracle.adfinternal.model.portlet.manager.PortletProviderManager.registerPortletProvider(PortletProviderManager.java:1582)
at oracle.adfinternal.model.portlet.manager.PortletProviderManager.registerPortletProvider(PortletProviderManager.java:545)
at oracle.adfdtinternal.model.portlet.wizards.registration.wsrp.WSRPProducerRegUtil.registerProducer(WSRPProducerRegUtil.java:308)
at oracle.adfdtinternal.model.portlet.wizards.registration.wsrp.WSRPProducerRegistrationWizard$1.doWork(WSRPProducerRegistrationWizard.java:862)
at oracle.ide.dialogs.ProgressRunnable.run(ProgressRunnable.java:161)
at oracle.ide.dialogs.ProgressBar.run(ProgressBar.java:655)
at java.lang.Thread.run(Thread.java:619)
Caused by: java.lang.RuntimeException: Error converting the following SOAP element to JAXB package 'oracle.portlet.wsrp.v1':
node: ns0:getServiceDescriptionResponse = null
attribute: xmlns:SOAP-ENV = http://schemas.xmlsoap.org/soap/envelope/
attribute: xmlns:ns0 = urn:oasis:names:tc:wsrp:v1:types
attribute: xmlns:xsd = http://www.w3.org/2001/XMLSchema
attribute: xmlns:env = http://schemas.xmlsoap.org/soap/envelope/
attribute: xmlns:xsi = http://www.w3.org/2001/XMLSchema-instance
node: ns0:requiresRegistration = null
node: #text = true
node: ns0:offeredPortlets = null
node: ns0:portletHandle = null
node: #text = pop_np:pop_scoped%pcd:portal_content/com.prueba.zprueba/ZMW_PRD_INF_PRU_PORTAL
node: ns0:markupTypes = null
node: ns0:mimeType = null
node: #text = text/html
node: ns0:modes = null
node: #text = wsrp:view
node: ns0:modes = null
node: #text = wsrp:edit
node: ns0:modes = null
node: #text = wsrp:help
node: ns0:modes = null
node: #text = wsrp:preview
node: ns0:windowStates = null
node: #text = wsrp:normal
node: ns0:windowStates = null
node: #text = wsrp:minimized
node: ns0:windowStates = null
node: #text = wsrp:maximized
node: ns0:windowStates = null
node: #text = wsrp:solo
node: ns0:locales = null
node: #text = en-US
node: ns0:groupID = null
node: #text = DEFAULT_WSRP_GROUP_NAME
node: ns0:description = null
attribute: xml:lang = en_US
attribute: resourceName = com.sap.portal.pcm.Description
node: ns0:value = null
node: #text = Informes Producción Prueba Portal
node: ns0:shortTitle = null
attribute: xml:lang = en_US
attribute: resourceName = com.sap.portal.pcm.Title
node: ns0:value = null
node: #text = Informes Producción Prueba Portal
node: ns0:title = null
attribute: xml:lang = en_US
attribute: resourceName = com.sap.portal.pcm.Title
node: ns0:value = null
node: #text = Informes Producción Prueba Portal
node: ns0:usesMethodGet = null
node: #text = false
node: ns0:defaultMarkupSecure = null
node: #text = false
node: ns0:onlySecure = null
node: #text = false
node: ns0:userContextStoredInSession = null
node: #text = false
node: ns0:templatesStoredInSession = null
node: #text = false
node: ns0:hasUserSpecificState = null
node: #text = false
node: ns0:doesUrlTemplateProcessing = null
node: #text = true
node: ns0:offeredPortlets = null
node: ns0:portletHandle = null
node: #text = pop_np:pop_scoped%pcd:portal_content/com.prueba.zprueba/TEST
node: ns0:markupTypes = null
node: ns0:mimeType = null
node: #text = text/html
node: ns0:modes = null
node: #text = wsrp:view
node: ns0:modes = null
node: #text = wsrp:edit
node: ns0:modes = null
node: #text = wsrp:help
node: ns0:modes = null
node: #text = wsrp:preview
node: ns0:windowStates = null
node: #text = wsrp:normal
node: ns0:windowStates = null
node: #text = wsrp:minimized
node: ns0:windowStates = null
node: #text = wsrp:maximized
node: ns0:windowStates = null
node: #text = wsrp:solo
node: ns0:locales = null
node: #text = en-US
node: ns0:groupID = null
node: #text = DEFAULT_WSRP_GROUP_NAME
node: ns0:description = null
attribute: xml:lang = en_US
attribute: resourceName = com.sap.portal.pcm.Description
node: ns0:value = null
node: ns0:shortTitle = null
attribute: xml:lang = en_US
attribute: resourceName = com.sap.portal.pcm.Title
node: ns0:value = null
node: #text = TEST
node: ns0:title = null
attribute: xml:lang = en_US
attribute: resourceName = com.sap.portal.pcm.Title
node: ns0:value = null
node: #text = TEST
node: ns0:usesMethodGet = null
node: #text = false
node: ns0:defaultMarkupSecure = null
node: #text = false
node: ns0:onlySecure = null
node: #text = false
node: ns0:userContextStoredInSession = null
node: #text = false
node: ns0:templatesStoredInSession = null
node: #text = false
node: ns0:hasUserSpecificState = null
node: #text = false
node: ns0:doesUrlTemplateProcessing = null
node: #text = true
node: ns0:requiresInitCookie = null
node: #text = perGroup
at oracle.portlet.utils.SoapJaxbTranslationUtils.soapToJaxb(SoapJaxbTranslationUtils.java:129)
at oracle.portlet.wsrp.v1.WSRP_v1_ServiceDescription_PortTypeJaxbToSoap.toJaxb(WSRP_v1_ServiceDescription_PortTypeJaxbToSoap.java:38)
at oracle.portlet.wsrp.v1.WSRP_v1_ServiceDescription_PortTypeJaxbToSoap.getServiceDescription(WSRP_v1_ServiceDescription_PortTypeJaxbToSoap.java:73)
at oracle.portlet.wsrp.v1.ServerToWSRPv1.getServiceDescription(ServerToWSRPv1.java:121)
at oracle.portlet.client.connection.wsrp.ActivityServerWrapper.getServiceDescription(ActivityServerWrapper.java:1224)
at oracle.portlet.client.techimpl.wsrp.WSRPClientImpl.registerProducer(WSRPClientImpl.java:2542)
at oracle.portlet.client.techimpl.wsrp.WSRPClientImpl.register(WSRPClientImpl.java:182)
at oracle.portlet.client.techimpl.wsrp.WSRPClientImpl.createProducer(WSRPClientImpl.java:3155)
at oracle.portlet.client.containerimpl.wsrp.WSRPProducerFactoryImpl._createProducer(WSRPProducerFactoryImpl.java:130)
at oracle.portlet.client.containerimpl.wsrp.WSRPProducerFactoryImpl.createProducer(WSRPProducerFactoryImpl.java:107)
at oracle.adfinternal.model.portlet.manager.PortletProviderManager.registerWSRPProducer(PortletProviderManager.java:1976)
... 7 more
Caused by: javax.xml.bind.UnmarshalException: Unexpected end of attribute {http://www.w3.org/XML/1998/namespace}:lang
at oracle.portlet.wsrp.v1.impl.runtime.SAXUnmarshallerHandlerImpl.handleEvent(SAXUnmarshallerHandlerImpl.java:536)
at oracle.portlet.wsrp.v1.impl.runtime.AbstractUnmarshallingEventHandlerImpl.reportError(AbstractUnmarshallingEventHandlerImpl.java:147)
at oracle.portlet.wsrp.v1.impl.runtime.AbstractUnmarshallingEventHandlerImpl.reportError(AbstractUnmarshallingEventHandlerImpl.java:144)
at oracle.portlet.wsrp.v1.impl.runtime.AbstractUnmarshallingEventHandlerImpl.unexpectedLeaveAttribute(AbstractUnmarshallingEventHandlerImpl.java:167)
at oracle.portlet.wsrp.v1.impl.runtime.AbstractUnmarshallingEventHandlerImpl.leaveAttribute(AbstractUnmarshallingEventHandlerImpl.java:100)
at oracle.portlet.wsrp.v1.impl.LocalizedStringImpl$Unmarshaller.leaveAttribute(LocalizedStringImpl.java:372)
at oracle.portlet.wsrp.v1.impl.runtime.SAXUnmarshallerHandlerImpl.consumeAttribute(SAXUnmarshallerHandlerImpl.java:431)
at oracle.portlet.wsrp.v1.impl.LocalizedStringImpl$Unmarshaller.enterElement(LocalizedStringImpl.java:227)
at oracle.portlet.wsrp.v1.impl.PortletDescriptionImpl$Unmarshaller.enterElement(PortletDescriptionImpl.java:929)
at oracle.portlet.wsrp.v1.impl.runtime.SAXUnmarshallerHandlerImpl.startElement(SAXUnmarshallerHandlerImpl.java:133)
at com.sun.xml.bind.unmarshaller.DOMScanner.visit(DOMScanner.java:240)
at com.sun.xml.bind.unmarshaller.DOMScanner.visit(DOMScanner.java:277)
at com.sun.xml.bind.unmarshaller.DOMScanner.visit(DOMScanner.java:246)
at com.sun.xml.bind.unmarshaller.DOMScanner.visit(DOMScanner.java:277)
at com.sun.xml.bind.unmarshaller.DOMScanner.visit(DOMScanner.java:246)
at com.sun.xml.bind.unmarshaller.DOMScanner.visit(DOMScanner.java:277)
at com.sun.xml.bind.unmarshaller.DOMScanner.visit(DOMScanner.java:246)
at com.sun.xml.bind.unmarshaller.DOMScanner.parse(DOMScanner.java:150)
at oracle.portlet.wsrp.v1.impl.runtime.UnmarshallerImpl.unmarshal(UnmarshallerImpl.java:166)
at oracle.portlet.utils.SoapJaxbTranslationUtils.soapToJaxb(SoapJaxbTranslationUtils.java:110)
... 17 more
Any Idea?,
ThanksHi,
when you develop your app with the NWDS and choose: Enterprise Poral application, your app will be compatible with EP (PRT). But you'll have to make sure that you don't use libraries / functionanlity that isn't WSRP compatible (like: JCo, BI integration, etc). The portal simply won't know if your app is WSRP-compliant or not. Your consumer will call the WSRP app. If this will work or not will depend on your app. So you'll have to make sure that your app is WSRP-compliant.
But first: you'll have to register your consumer. This works with BEA / Oracle and (sometimes) with JBoss also.
br,
Tobias -
SAP Tech ED : Workshop Session Registration
Dear All ,
Could any one tell me when registration for the Workshop session will be open for SAP Tech Ed 2010 Bangalore .
Thanks ,
Aryan.Gagan & other friends,
Have you registered for full conference or lecture only sessions ? Anybody (with Lecture only pass) started receiving mails for TechEd registration confirmation ?
I'll be attending this TechEd in India at Bangalore. Need this information, am I supposed get a mail confirmation now ? or it'll come later ?
Thanks -
SAP TABLE of developer registration keys
Hi, is there anyone who nows the table where sap stores
the developer registration keys and related users (in release 45B)?
Thanks and Regards.
Riccardo GalliHi riccardo,
1. DEVACCESS table.
regards,
amit m.
Maybe you are looking for
-
HP Officejet 4215 all-in-one printer, copier, fax and scanner
Before I installed Leopard, I had various options in my print menu available to me. For example, I could print a document or webpage in black and white (to save ink) that was originally in color. After installing Leopard, those printer options do not
-
Page Size for Z2100 - Mac Software
I print lots of long documents, all of which are 23" wide but of vaiable lengths. I used to use HP Instant Printing software on my PC, where I would simply add the file and my HP Designjet Z2100 would print it and then cut the roll before moving onto
-
It it possible to create a boot disk on CDROM, but this limits the size to 650 MB (roughly). Is it possible to make a boot disk in DVD format, and if so, can it be done by burning all the relevant files on a Win 2k DVD burner? Our rep is suggesting a
-
WL commerce server install problem
Ok, this has me feeling real stupid: Fresh install, Windows 2000, JDK 1.3, WLS 5.1, SP6 (including the tags file). Once I start the installer and enter the installation directory (it doesn't show a default, should it?), the installer says something l
-
Can't ftp in xdb when value xs:maxLength (schema)
I can't ftp into xdb when the content of a xml element is larger then xs:maxLength(schema) of that xml element. schema <xs:element name="b"> <xs:simpleType> <xs:restriction base="xs:string"> <xs:maxLength value="13"/> </xs:restriction> </xs:simpleTyp