0FI_AR_4 Extractor Enhancement without user exit code Question

Hi
I have a requirement to enhance 0FI_AR_4 Extractor with below Fields from BSID:
Field     DataElement
PRCTR       PRCTR
VPOS2       NUM06
VBUND       RASSC
As per SAP Note: 410799, I am assuming I don't need to write any ABAP code to populate these fields.
In the extract structure DTFIAR_3 of extractor 0FI_AR_4 Double clicked on the Include CI_BSID.
It prompted "Structure CI_BSID not available. Create the structure?"
After entering Access key it created new Structure "CI_BSID".
I have entered the Component and Component Type values as below:
Component   Component Type
YYPRCTR     PRCTR
YYVPOS2     NUM06
YYVBUND     RASSC
1. Please let me know Component and Component Type values and the steps I followed are correct or not?
2. And I hope I don't need to write the code in the User exit to populate these fields?
Thanks
Sree

Hi,
For any FI datasource enhancement there are two scenarios :-
1. All the fields of the customer enhancement in the customer include are available in the read structure BSID
Then no additional action is required. The fields of the customer enhancement are filled automatically by the datasource from the assigned read structure via "move-corresponding".
2. Fields of the customer enhancement in the customer include are not contained in the read structure BSID
In this case you have to program a function module to fill the field of the customer enhancement. To do this, there is a Business Transaction Event available (open FI interface for process 00005021). Create any function module you like and use function module SAMPLE_PROCESS_00005021 as a template for the interface (input parameter, changing parameter).
Hope this helps.
Reg,
Rahul

Similar Messages

Extractor enhancement with user exit RSAP0001

Hello,
I am using user exit RSAP0001 to enhance SAP business partner extractors. When I am processing the data pack in function module EXIT_SAPLRSAP_002, is there any chance to get information about the receiving BI system (e.g. logical system name) I am just processing data for?
The reason why I want to do that is data protection issues. Data is being extracted into different BI systems, but certain fields may only be extracted into some of them. The idea is that I can decide to clear those fields depending on the BI that is requesting the data.
Kind regards,
Christoph Reuter

Hi Christoph,
You can make use of the following tables . They contain R/3- BI connection related info.
T000 ( clients table) - fields MANDT and LOGSYS of this table give the u2018Client IDsu2019 and u2018Logical
                                  IDsu2019 of the R/3 system as shown.
   RSBASIDOC (Assignment of source systems to BI systems incl. IDoc typ) -
                In this the fields SLOGSYS, RLOGSYS and OBJSTAT correspondingly hold the
                logical Id of source system (R/3), Logical ID of the receiver system (BI) and the status of the connection between them ( 0 or 1 meaning active or inactive).
In addition to these, you can make use of the Function module RFC_READ_TABLE to read data from a master data table in BI to R/3 system.
So, by creating a master data object in BI and maintaining a specific key value representing each BI system, you can identify the BI system by reading the value in the master data table in BI into R/3.
Though the information given here is a bit brief, I hope this helps you
Edited by: nithin reddy on May 15, 2009 7:43 PM

BW User Exit - Code in function of the query name

Hi,
I would like to create an user exit code which execute a algorithm different in function of the query executed. do you know in which variable is store the technical name of the query.
CASE query
    WHEN 'Z_ZAPO_001'.
       V1 = 1
    WHEN 'Z_ZAPO_002'.
      V1 = 2    WHEN '10' OR '11' OR '12'.
ENDCASE.

Yaroslav,
I_S_RKB1D-COMPID will never be filled for authorization user-exits (I_STEP = 0). Don't ask my why, I once raised this question to OSS and they replied it was never foreseen to work with authorization user-exits. God knows why, it's very unlogical and it wouldn't cost them a lot of work to get it working...
I could solve this problem by applying a little trick. In our queries we included a user-exit keydate variable. This will push the user-exit first in I_STEP = 1 mode where I_S_RKB1D-COMPID is filled. Then save the query name by exporting it to the ABAP-memory. Afterwards, the user exit with code for I_STEP = 0 will be processed and then you can import the query name from the ABAP memory.
I agree it sounds a little bit tricky but there is no better option I'm affraid.

User exit code does not execute

I'm having a problem with User exit code that does not execute yet seems to be set up correctly.
The User exit is implemented as FM "EXIT_SAPLIPW1_001" in function group XQSM.
I've tried everything I know of with the CMOD and SMOD transactions, and I suspect some sort of transport error.
The only clue I can find in comparing the development system (which works) with the test system (which does not work) is that running "Extended Check" in SE80 on function group XQSM fails with the following error:
"The namespace of program SAPLXQSM has the setting "C" and cannot be tested."
Has anyone any idea what could have happened?

Let us try to retrace the steps.
1. You created a Z project in CMOD and assigned the enhancement IQSM0001 and the component EXIT_SAPLIPW1_001 and activated the same. This is there in the transport.
2. You double clicked on the include in the user exit and created it. You activated the code and included it in the same transport.
If you did the above steps, then your user exit should be active in your test system.
Can you please go to SE10, and list out the objects in your transport? You should see entries in there like below(not necessarily a complete list)
R3TR CMOD <your project name>
R3TR PROG ZXQSMU01
See if you created any of the objects as local objects.
Srinivas

Brief about enhancements and user exits

hai,
can any one tell me what are enhancements and user exits in sap sd,
their signifcance & configuration
regards
sriram

hi,
an example of user exit
In case of Inbound DELINS IDOC (830 type) once there was a requirement of taking the Target *** Qty required and the Target *** Date for a specific customer who was not sending *** Qty Received by him.
So for that specific customer we used the search term and added the same in the Data 4 field of the IDOC under segment E1EDK09.
There was one user exit available in IDOC_INPUT_DELINS_START Function module of SAP. We triggered this logic by the search term of customer and reached the user exit where we had made some code changes. (User Exits are used to make code changes when we are running standard programs or reports or function modules). With this we were able to reach the desired point of calculating *** Issued and then find out the difference from Target *** Qty and get *** Qty Received for the scheduling agreement. We did not copy the standard function module into Z . Instead the same was done using a user exit.
<b>User exits in SD</b>
Menu Path:
SPRO- IMG- SD- System Modification- User Exists. User Exists are available in SD for the following processes:
User exits for price determination
User exits for partner determination
User exits for credit check & risk management
User exits in sales:
o User exits in sales doc processing
o User exits for contract processing
o User exits for product allocation processing
o User exits for availability checking
o User exits for component supply processing
o User exits for product selection
o User exits for billing plan
User exits for shipping
User exits for transportation
User exits for billing
User exits for general billing interface
User exits for sales support
User exits for lists.
The topic of user exits is a subject that concerns ABAP development & extensive experience in ABAP is required to understand and use the user exits.
A customer user exit is essentially a function module using a unique naming convention, in which set import and export parameters are defined to limit the data that can be manipulated. This is to protect certain data from being changed. This function module is attached to an enhancement that may contain other function modules. A user exit should only be used if the possibilities for customizing or application-specific user exits are inadequate.
NEW FIELDS IN PRICING:
To use a field in pricing, one creates a cond table. This cond table is created using the allowed fields from the field catalog. Should the fields one requires not be included in the list of allowed fields, one can add the fields from the list of available fields. However, one may find that a new field may not be in the list of available fields. For this reason, one must create new fields for pricing. The document & item data in SD is stored in data tables such as VBAK & VBAP (for the order transaction). Many of the fields from these tables are available in the field catalog.
The field catalog is a structure (KOMG) that consists of 2 tables (KOMK & KOMP). These tables contain the header & item data for pricing respectively. They are called KOMx because they are communications structures used to communicate the transaction data with the pricing procedure. Table KOMG contains the field KOMK & KOMP.
If you require a field that is not in KOMG, it means that it is not in KOMK or KOMP. This means that the field you require cannot be used in pricing because there is no communication of this field from the transaction to the pricing procedure via the communication structures.
To use a field not defined in the field catalog, you need to add this field to KOMK or KOMP structures, and then write the ABAP code to transfer the data in the field from the transaction tables to the communication structure. Follow these steps:
Create the field in the KOMK (header data) & KOMP (item data) tables using the standard includes provided for this requirement.
Write the code in the user exit to read the transaction data & transfer it to the KOMx structures.
Menu Path:
SPRO- IMG- SD- System Modification- Create New Fields (using the cond tech)- New fields for Pricing.
Adding the field to KOMK & KOMP:
This process requires some knowledge of the ABAP dictionary & how to use the ABAP dictionary to create & change fields & tables. If the field is from the header table (for e.g. the order table: VBAK), you will need to add it to the include table KOMKAZ in the table KOMK. If the field is from the item table (for e.g. the order item table: VBAP), you will need to add it to the include table KOMPAZ in table KOMP.
Lets say you need to use the base material to define a price & the base material is no in the pricing field catalog. The base material is a field on the MMR basic data screen & is defined as MARA-WRKST. Since this relates to the material, it is at the item level, so you would add the field to KOMKAZ include table.
When you add a field to these tables, it must start with ZZ. Therefore, the field you add would be ZZWRKST. In ABAP, when you add the field, use the same domain as in the field in the original table MARA-WRKST.
After adding the field, generate the structure KOMP. This field is not available in the field catalog & can be used in condition tables.
Menu Path:
SPRO- IMG- SD- System Modification- User Exists. User Exists are available in SD for the following processes:
User exits for price determination
User exits for partner determination
User exits for credit check & risk management
User exits in sales:
o User exits in sales doc processing
o User exits for contract processing
o User exits for product allocation processing
o User exits for availability checking
o User exits for component supply processing
o User exits for product selection
o User exits for billing plan
User exits for shipping
User exits for transportation
User exits for billing
User exits for general billing interface
User exits for sales support
User exits for lists.
The topic of user exits is a subject that concerns ABAP development & extensive experience in ABAP is required to understand and use the user exits.
A customer user exit is essentially a function module using a unique naming convention, in which set import and export parameters are defined to limit the data that can be manipulated. This is to protect certain data from being changed. This function module is attached to an enhancement that may contain other function modules. A user exit should only be used if the possibilities for customizing or application-specific user exits are inadequate.
NEW FIELDS IN PRICING:
To use a field in pricing, one creates a cond table. This cond table is created using the allowed fields from the field catalog. Should the fields one requires not be included in the list of allowed fields, one can add the fields from the list of available fields. However, one may find that a new field may not be in the list of available fields. For this reason, one must create new fields for pricing. The document & item data in SD is stored in data tables such as VBAK & VBAP (for the order transaction). Many of the fields from these tables are available in the field catalog.
The field catalog is a structure (KOMG) that consists of 2 tables (KOMK & KOMP). These tables contain the header & item data for pricing respectively. They are called KOMx because they are communications structures used to communicate the transaction data with the pricing procedure. Table KOMG contains the field KOMK & KOMP.
If you require a field that is not in KOMG, it means that it is not in KOMK or KOMP. This means that the field you require cannot be used in pricing because there is no communication of this field from the transaction to the pricing procedure via the communication structures.
To use a field not defined in the field catalog, you need to add this field to KOMK or KOMP structures, and then write the ABAP code to transfer the data in the field from the transaction tables to the communication structure. Follow these steps:
Create the field in the KOMK (header data) & KOMP (item data) tables using the standard includes provided for this requirement.
Write the code in the user exit to read the transaction data & transfer it to the KOMx structures.
Menu Path:
SPRO- IMG- SD- System Modification- Create New Fields (using the cond tech)- New fields for Pricing.
Adding the field to KOMK & KOMP:
This process requires some knowledge of the ABAP dictionary & how to use the ABAP dictionary to create & change fields & tables. If the field is from the header table (for e.g. the order table: VBAK), you will need to add it to the include table KOMKAZ in the table KOMK. If the field is from the item table (for e.g. the order item table: VBAP), you will need to add it to the include table KOMPAZ in table KOMP.
Lets say you need to use the base material to define a price & the base material is no in the pricing field catalog. The base material is a field on the MMR basic data screen & is defined as MARA-WRKST. Since this relates to the material, it is at the item level, so you would add the field to KOMKAZ include table.
When you add a field to these tables, it must start with ZZ. Therefore, the field you add would be ZZWRKST. In ABAP, when you add the field, use the same domain as in the field in the original table MARA-WRKST.
After adding the field, generate the structure KOMP. This field is not available in the field catalog & can be used in condition tables.
Pl reward if helpful.
Thanks
Sadhu Kishore

Enhancement for user exit

hello
can you please let me the know the enhancement for user exit:exit_sapliqs0_001
regards
anik

Hi,
these are teh enhancements that r available...u need to check each of them.
IWO10026 User check on setting status 'Do not perform'
IWO10027 User exit: Generate user-defined settlement rule
IWOC0001 Create PM/SM notification: Determine reference object
IWOC0002 PM/SM notification: Check whether status change is allo
IWOC0003 PM/SM authorization check of ref. object and planner gr
IWOC0004 Change single-level list editing PM/QM/SM ALV settings
Regards,
nagaraj

ENHANCEMENT QPAP0001 (User Exit 'EXIT_SAPLQPAP_001

HI all,
We are Using Variant Configuration, for this we have linked MIC's to Class character, When The Inspection Lot is created the Lower & Upper Limit in the specification comes as the character Value.it does not takes in to consedration the tolerance key assigned to it. For E.g. Charater Dia has value 20, & in the Tolerance key for 20 +/- 0.10 is maintained, when the Inspection lot is created the Upper & lower Limit comes as 20-20 instead 19.9 - 20.1
I have gone through SAP Note 210658, the sample code provided in note is for "Material Specification" I have tried the same with minor code correction the specifications in the lot comes as desired i.e. specifications in the lot consider the tolerance key.
Our Requirment is of task list, in the same not EXIT for task list is also mentioned but no souce code is provided, when we are using the above program (Used for Material Specification) after doing the desired changes, & when we run in de-bugging mode it shows all the calculations are being done, but finally in the lot specification appear as the charater value ( 20-20) & in the inspection lot One first MIC comes it delete's all other MIC's assigned in the Plan.
Has any body worked on this requirment, please let me know how to do the same, & if any body has used EXIT_SAPLQPAP_001 (Enhancement QPAP0001.)Plese provide me with the soution if any one has worked on it.
Thanks & Regards
Gaurav Behl

Hi,
these are teh enhancements that r available...u need to check each of them.
IWO10026 User check on setting status 'Do not perform'
IWO10027 User exit: Generate user-defined settlement rule
IWOC0001 Create PM/SM notification: Determine reference object
IWOC0002 PM/SM notification: Check whether status change is allo
IWOC0003 PM/SM authorization check of ref. object and planner gr
IWOC0004 Change single-level list editing PM/QM/SM ALV settings
Regards,
nagaraj

Wt are different ways to find enhancement spots(User Exits) in ECC 6.0??

Hi Friends,
How are you all doing??
Friends relevant answers are awarded points. Pls give solutions..
What are the different ways to find the enhancement spots (i mean user exit points) in ECC 6.0??
I want to find the enhancement spot in sale order transaction (va01/va02) after save happening or else after commit happen. In that i need to call the badi method on_costing_component. So friends could you give solution for this.

Hi
You can see this document for knowing the Userexits for a given Trxn.
<a href="https://www.sdn.sap.comhttp://www.sdn.sap.comhttp://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/com.sap.km.cm.docs/library/abap/abap-code-samples/userexits%20in%20a%20transaction.doc">Listing UserExits in Transactions</a>
Regards
Raj

F110 - Enhancement spot / USer exit

Hi ,
I need to add some coding logic, once the idocs are generated after execution of transaction F110.
I found an enhancement point in program RFFOEDI1,(which is called by this transaction).
But when i create a new enhancement in it. If i write any piece of code, it gives me an error saying "Statement not accessible".
1)Could someone tell why this error appears.
2) Is there some other way to meet the requirement.
Thank you!!

Hi,
Could be that the ehnancement point that you are using is not getting triggered or the implementaiton that you have created is not properly activated.
You can try other implicit and explict enhancement points also we have some user-exits go to transaction SMOD press F4 in the enahncement name and enter FBZ as development class and hit enter you would get a list of enhancement.
Also if you could share the more info on what enh point you are using would be easier to ans.
Regards,
Himanshu

How to find enhancement RSAP0001 user exit EXIT_SAPLRSAP_001 project CMOD

Hi,
I need to find in one system the project in cmod that contains the enhancement RSAP0001 with user exit EXIT_SAPLRSAP_001.
How do I proceed?
Thanks a lot

Simon,
Goto CMOD and enter * and select F4 so that you will get the list of packages. Most of the clients we have naming terminology with BW. Pick one of them and go for components there you can see the interface.
Double click on that you will see four classes. Select any one of them and write your logic.
If you provide what exactly your are trying to do enhancements, so that will provide better solutions.
Thanks
Ganesh reddy.

EDI - IDoc - User Exit - Code - Problem - Help - Wanted

Hi EDI Experts,
I have extended ORDERS05 IDOC twice.
ZVKSEG1 is the the segment under extended idoc ZVKORDRS05. This is for one partner.
Z1DATESH01 is the segment under extended idoc Z1ORDER05. This is for another partner.
I have completed the configuration thing in WE82 for both the extensions.
Now the requirement is, whenever a PO is created for the first partner - 100290, the IDoc generated should contain the extra segment ZVKSEG1 and whenever PO is created for the second partner - 10099,the Idoc generated should contain the extrasegment Z1DATESH01.
Using WE20, i have added the extended IDoc type in both the partner profiles under ORDERS message type.
Now i've written the user exit for this using EXIT_SAPLEINM_002.
tables: edidc.
data: z_edidd like edidd occurs 0 with header line.
data: y1dath01 like z1datesh01.
data: yvkseg1 like zvkseg1.
if edidc-rcvprn = '10099'.
z_edidd[] = int_edidd[].
loop at z_edidd.
if z_edidd-segnam = 'E1EDK01'.
read table z_edidd with key segnam = 'Z1DATESH01'.
if sy-subrc <> 0.
y1dath01-DELDATE = sy-datum.
clear z_edidd.
z_Edidd-sdata = y1dath01.
z_Edidd-segnam = 'Z1DATESH01'.
append z_edidd.
endif.
endif.
endloop.
int_edidd[] = z_edidd[].
elseif edidc-rcvprn = '100290'.
z_edidd[] = int_edidd[].
loop at z_edidd.
if z_edidd-segnam = 'E1EDK01'.
read table z_edidd with key segnam = 'ZVKSEG1'.
if sy-subrc <> 0.
yvkseg1-name1 = 'ZVK Chemicals'.
clear z_edidd.
z_Edidd-sdata = yvkseg1.
z_Edidd-segnam = 'ZVKSEG1'.
append z_edidd.
endif.
endif.
endloop.
int_edidd[] = z_edidd[].
endif.
Could you please go through the code and tell me where did i go wrong. The extra segments are not being created for both the partners.
I created PO using ME21n once for each vendor.
Please help me out guys.
Thanks,
Matt

I myself fixed this problem. I made use of XLFA1-LIFNR to manipulate the partner numbers.
Thanks

Excluding idoc processing from user exit code

Hi all,
In a user exit (for VA01 Create Sales Order) we are currently excluding certain order types by hardcoding the document type in the code. This is because some orders are created by IDoc and in this case the IDocs fail if they use the eser exit code (because the code creates pop-up messages intended for online users only). Not the best solution.
Does anybody know if we can use different code so that this part of the user exit does not get triggered by IDocs?
Thanks,
Mike

I've figured out another solution - you can do a test on the field IDOC_NUMBER. If it is filled, then the sales order is created/changed via an Idoc.

FB60 Enhancement - BADI / User Exit / Substitution

I have the following requirement:
<b>When an invoice is posted using transaction FB60, based on GL Account entered, the line item text should be populated with the vendor name/number.</b>
I searched the forum and found that some of you have recommended to use 'substitutions'. But I am not familar with those and I am not sure if that will provide me a solution. An user exit or BADI would be great. Please help me out!
Thanks,
Sam

Hi
Just I said you have to define an exit like this:
- Define LIFNR as global data
DATA: LIFNR TYPE LIFNR.
FROM Z001.
DATA NAME LIKE LFA1-NAME1
IF BSEG-KOART = 'K'.
LIFNR = BSEG-LIFNR
ELSE.
IF NOT LIFNR IS INITIAL.
SELECT SINGLE NAME1 FROM LFA1 INTO NAME
WHERE LIFNR = LIFNR.
CONCATENATE LIFNR '/' NAME INTO bseg-sgtx
ENDIF.
ENDFORM.
In this case use SYST-TCODE = FB60 as prerequisite, so when the item is Vendor item you'll store the Vendor Code and if it's G/L item you'll create the text.
You can also create an substitution at the complete document, in this case:
FROM Z001 bool_data TYPE gb002_015.
DATA: LIFNR LIKE LFA1-LIFNR,
NAME LIKE LFA1-NAME1.
LOOP AT bool_data-bseg INTO bseg where KOART = 'K'.
LIFNR = BSEG-LIFNR.
EXIT.
ENDLOOP.
IF NOT LIFNR IS INITIAL.
SELECT SINGLE NAME1 FROM LFA1 INTO NAME
WHERE LIFNR = LIFNR.
LOOP AT bool_data-bseg INTO bseg where KOART = 'S'.
CONCATENATE LIFNR '/' NAME INTO bseg-sgtx
MODIFY bool_data-bseg FROM BSEG.
ENDLOOP.
ENDIF.
ENDFORM.
Max

USER EXIT CODE In BEX

Friends,
In Bex query for an ODS,I need to create a report
-In the selection screen user has to enter one date value.(DATE1 Varible)
I need to get the values in the report based on following condition
==>DATE1 < DATE2.
As user defined variable can be used in one charcteristics only,I unable to include Date1 variable in DATE2 Restriction Option.
I will have to write the user exist for this?.If so pls help me with the user exist code.
Thanks in advance.
Soujanya

Hi,
Pls create a customer exit variable 'ZPDATE2' for DATE2(Clearing Date) with the code below and use it as apprpriate in the query together with DATE2.
What the code does is to transfer the value of the variable 'ZPDATE' to the variable 'ZPDATE2' (upon user entry of 'ZPDATE')
CASE I_VNAM.
WHEN 'ZPDATE2'. " Characterstic VARIABLE
    IF I_STEP = 2.
get variable value 'ZPDATE'
      LOOP AT I_T_VAR_RANGE INTO LOC_VAR_RANGE
                   WHERE VNAM = 'ZPDATE'. " Current fiscal Period.
        CLEAR : L_S_RANGE.
*--- fill value ranges
        MOVE : 'I' TO L_S_RANGE-SIGN,
               'LT' TO L_S_RANGE-OPT.
        APPEND L_S_RANGE TO E_T_RANGE.
        EXIT.
      ENDLOOP.
    ENDIF.    " for After pop-up
ENDCASE.
Hope this helps !

How to see user exit code

hi,
i have one user exit name with me like EXIT_SAPLVxxxxx. how can i see it's code.
thks

Those user exits are build as function modules. Just goe to transaction SE37, put in the name and there you go. Double click on the include in the FM and you'll see the code. If the include doesn't exist this user exit has not yet been implemented.
Regards,
Michael

0FI_AR_4 Extractor Enhancement without user exit code Question

Similar Messages

Maybe you are looking for