Branch Allocation Field

Is there any way how I can suppress the branch allocation field in F110? It is a mandatory field when a thailand company code is involve but we don't want this branch allocation field. I hope there is a way that we can save our payment run for thailand without a value for the branch allocation field. Thanks!

Hello Kay Lim,
I assume table T042 for the Thailand Company code you mentioned has the XBPTR field filled with 'X'.
To change it, you should go in SPRO transaction, IMG (<F5> key) and the path:
Financial Accounting -> Accounts Receivable and Accounts Payable -> Business Transactions -> Outgoing Payments -> Automatic Outgoing Payments -> Set Up All Company Codes for Payment Transactions.
Hope it helps you.
Regards,
Daniel.

Similar Messages

Branch allocation in APP(F110)

Hi,
When i Run APP, in one Client(110) is asking Branch allocation, I find this Branch allocation in Paremeter tab.
and in other client(210) the field is not visble at all.
where to set this Branch allocation fields? so that it will appear/disappear in the F110 .
Thanks In Advance.

Hi,
The Branch account assignment must be active hence when you run F110, it is asking for branch allocation for that specific co code. Check in SPRO settings if branch assignments for automatic postings is activated.
The path is
SPRO - Financial Accounting - Accounts Receivable and Accounts Payable - Business Transactions - Interest Calculation - Interest Posting - Branch Assignment for Automatic Postings - Define Branch Assignment for Automatic Postings
hope this helps
regards,
radhika

Mandatory "Allocation" field in MRHR (SAP 4.0B)

Hi Guys !
I'm writting an application to post MM invoices using BDC for MRHR transaction. SAP Version 4.0B.
My problem is that for some PO items, field "Allocation" is required and for others NOT and I need to inform user (in my application) if "Allocation is mandatory or nor - before he presses "Post" button.
Problem looks like this.
I start MRHR and key in header data. "Allocation" field in header(vendor line) is optional.
When I select PO and PO item, and enter item data - MRHR takes me to to the screen (SAPMM08R/ 0200) :
"Enter invoice: Document overview in USD".
When I press simulate, I got the message "Required entry not made" and I'm taken to screen (SAPMM08R/ 0120)
"Enter Invoice: Individual Purchase Order Item" and field Allocation (BSEG-ZUONR) is highlighted.
In summary - I'm looking for a setting/configuration transaction - where "Allocation" field is defined as "mandatory"
I suspect it is related to "Account assignment category" (in this case - item acc. assingn. cat = "P") and I've checked OME9 already. Still - I don't know where this was configured.
I tried SDH0 for MRHR (but there are no variants defined).
I tried OB28, OBA5 and OBA7 - with no success.
Do you know where this configuration is maintained?
Thanks for help in advance.
Best regards
//Tomasz

Field status definition extremely inconvenient. You have to go through a couple of tables to get what you are looking for.
Thanks for hint

Allocation field in sort key

hi
what is allocation field in sort key?plz explain me that allocation field?
rgds
naagesh

Hi Nagesh,
As You might be aware the Sort key helps in filling the assignment number field while posting to a GL a/c. If we choose 000 or allocation number which is nothing but assignment field itself , the assignment field will eb left blank for those GL accounts which ahs sort key 000.
Allocation number is nothing but the assignment filed ZUONR itself.
so when we give 000 sort key we are giving an option to the user to enter their choice of data in teh assignement field.
Hope this is clear.(Pls assign points if its helpful)
Thanks,
vamsi

Allocation field catalog

Hi,
Is it possible to map a different field from ECC to the field in the APO field catalog for product allocation check ?
I am aware of addition of a custom field in APO catalog and mapping a field from ECC side with the same name, which worked suscessfully.
For example - The field in field catalog is 'ABC' and the field in the sales order is 'XYZ' so during allocation check the value in the field 'XYZ' should be passed into 'ABC' during allocation check.
Regards,
RS

Hi Y R,
This is really interesting, but as a standard SAP behavior system need to find same characteristics fields which are passed from ECC.
I am not eliminating the possibility of using some exit in between, which will be doing field mapping activity for system to understand, which field to be check against which field.
Rgds
Sourabh

Operation branch: Table for field VORNR1

Dear all:
In some routings (CA01, 02, 03) we have different sequences, namely parallel sequences. As you know, these sequences have normally an operation wherein the parallel sequences branches off, or where an "alternative sequence" somehow replaces the normal reference sequence vector. This operation is the operation branch.
I have a requirement where this "Branch operation" field must become empty instead of showing the applicable branch operation (namely 0020, 0040, whatever).
To do this, a possible approach is to select all sequences of all routings that have a branch operation determined. So I found that the field is VORNR1 and table is PLFLD. But then I find out that this is a structure.
My simple question, is in which table I can find this field "branch operation" so to search in this table (via SE11 for example) or do a query (SQ01) using tables MAPL -> PLKO -> PLFL or both processes and see what happens
Thanks in advance!

3 tables involved.
PLFL - Sequences, PLAS - Operation assignment, and PLPO - Operation.
1. In your task list type (PLNTY), task list key (PLNNR), group counter (PLNAL) and sequence number (PLNFL) = 0, you will get the reference sequence (BEZFL), reference node for start of sequence - Branch operation (BKNT1) and reference node for end of sequence (BKNT2).
2. Go to PLAS which is the link between PLFL (sequence) and PLPO (Operation). You will obtain internal counter (ZAEHL) by select task list type (PLNTY), task list key (PLNNR), sequence (PLNFL should equal reference sequence BEZFPL from step 1), and node (PLNKN should equal reference node of start seq. BKNT1).
3. Select PLPO with key PLNTY, PLNNR, PLNKN, ZAEHL.
Hope it helps.

Problem activating field exit

Dear Friends,
When i try to activate my field exit using program RSMODPRF, the following message appears.....
System is not configured for field exits (see long text)
Message no. ENHANCEMENT032
Diagnosis
The system is configured wrong. Field exit maintenance will have no effect.
System Response
The profile parameter abap/fieldexit is set to YES during screen generation. A screen load is generated that allows you to branch to field exits.
This parameter may only be set in the customer system.
Note: If the parameter has been set, you must check that, for each field, the system branches to the correct corresponding function module during screen generation. For performance reasons, you should not set this parameter during generation unless field exits have actually been created for your system.
Procedure
Set the abap/fieldexit parameter to YES in the system profile and restart your SAP system.
How to solve this problem....
Thanks & Regards,
Sudheer

Hi,
         go thourgh the documentation of the program RSMODPRF..
Short text
Field Exits for Data Elements
Description
Maintenance transaction for creating and activating field exits
As part of the extension concept, SAP allows you to install a field exit for each screen field. Similar to the conversion exit, the system branches at the field exit at DCI (DATA COMMUNICATIONS INPUT) to a function module, if the field is an input field and a function code was triggered. The function module must adhere to the following naming convention:
Prefix: FIELD_EXIT_
Infix: <Data element name>
Suffix: _0 to _9 (optional), _A to _Z
The interface is automatically generated during the creation of the function module, and has 2 parameters:
Import parameter: INPUT
Export parameter: OUTPUT
After a function code has been triggered the contents of the field are made available to the FB via the "INPUT" import parameter. You can edit this and, when changed, make it available to the ABAP/4 processor in "OUTPUT". The input field contents are usually passed on: you can simply write OUTPUT = INPUT.
If, e.g., you have activated the field exit for the data element 'PROGRAM', then the fields of all the screens, which refer to the data element 'PROGRAM', branch to the function module FIELD_EXIT_PROGRAM. This includes the field 'Program' of the initial screen SAPMS38M0100 in transaction SE38, for example.
If you do not want the function module to be accessed from all screens, assign particular screens to the data element PROGRAM. By allocating an exit number, it is also possible to branch to other function modules with the corresponding suffix _0 ... _Z.
Example: You have assigned screen SAPMS38M0100 and exit number 5 to data element 'PROGRAM'. The corresponding field on SAPMS38M0100 branches to FIELD_EXIT_PROGRAMM_5.
As soon as you activate an exit, the corresponding screens are invalidated.
Note: Field exits are only taken into account during screen generation if the parameter abap/fieldexit = 'YES' is set in the system profile.
Requirements
Set the profile parameter abap/fieldexit = 'YES' before system start.
Limitations
The following ABAP statements are not allowed in the function modules of field exits:
     BREAK-POINT,
     CALL SCREEN, CALL DIALOG, CALL TRANSACTION, SUBMIT,
     COMMIT WORK, ROLLBACK WORK,
     COMMUNICATION RECEIVE,
     EXIT FROM STEP-LOOP,
     MESSAGE I, MESSAGE W.
Note:
Field exits cannot be edited with the debugger.
You should not use any external Performs in field exits. The ABAP processor shares the table work areas of externally called programs with those of the first caller. This could lead to errors at field exits that can hardly be analyzed, as field exits are sometimes slipped into the flow of the program at unforeseen events.
Questions and answers on field exits
1. A field exit was created with the CMOD and activated, but it does not get executed when the screen is called.
Since the field exit is not executed until DCI, some action must occur in the screen (e.g. press Return, saving....).
Set the abap/fieldexit profile parameter to YES and start the system again.
After the FIELD_EXIT... function module has been activated and the field exit has been activated, the transaction in whose screen the field exit is to be executed must be terminated. The screen is not generated until it is called.
Do not work on different application servers, otherwise there may be a delay before the field exit becomes active.
The profile parameter must be set either on all application servers or on none.
If the field exit is to be active in certain screens only, then you should check whether you have selected the correct program and the correct screen number (Careful with SUBSCREENS Do not rely on the F1 information for the field!
2. How does setting abap/fieldexit affect the performance?
If a screen is generated and the profile parameter is set, then the system checks in 2 tables (TDDIR, TDDIRS) to see whether a field exit has to be generated for the field. In practice the screen load after a Put is not generated until the screen is called. The user will not experience a noticeable delay, since screen generation is extremely fast.
3. Can the contents of other screen fields be read in a field exit?
In principle all fields can be copied to global variables in the TOP or the function group. However, since the order in which the field exits are called is not guaranteed, this possibility should not be used.
4. How does the field exit work in step-loop fields?
After data input to DCI the field exit will be called as many times as fields are visible on the step-loop. The SY-STEPL system variable is incremented each time. If a new value is assigned to be field, then it will be visible in the module between LOOP. ENDLOOP. This module will also be called as many times as there are visible step-loop lines.
5. Can field exits be debugged?
No. Field exits have to be tested in isolation in the development environment. To analyze problems that occur only in the screen environment, the relevant variables can be written to the file system using TRANSFER... and can be analyzed there.
6. What should one do if the field contents are not getting transported to ABAP/4?
Check whether you have assigned a value to the OUTPUT field.
7. When does the field exit get called in the case that there is a conversion exit attached to the data element?
The field exit will be called after the conversion exit. This means that the INPUT field contains the data in the same form as that in which the ABAP/4 program also gets them.
rEGARDS

Filling alloction field for a subledger account by posting invoice by MIRO

Hi, at this moment I am struggling with a problem concerning filling the field Allocation at line item of an GL account. When I am posting invoice by MIRO, I want to see certain information on line item of an GL Account. When I am posting an invoice by MIRO, this field is for P&L accounts and balancesheet accounts filled with the value such a determined in FS00, tab Control data, field Sort Key. So therefore all my accounts has the sort key Purchase order. When posting invoices by MIRO, the posting in FI, is showing me on line item level the PO-number in the field Allocation.
However, when I am posting an invoce by MIRO on an reconcilliation account for asset, the allocation field is empty, MIRO is not filling this field automatically. Although the settings of the sort key is the same as for other balance or P&L accounts.
Has anybody an idea how the allocation field can be filled automatically for an reconcilliation account for assets

Hi
Run the program RM07CUFA
in SE38 Tcode and check the inconsistencies.
Also in FS00 go to details of the GL account and double click on field status group under create bank interest tab and then double click material management/additional assignments.
You can see the required or suppressed fields

FBL3N & FS10N missing Field Purc Order in upgrade

hi all,
I´m having a problem because in the 4.7 version we made the proper configuration to see the PO and material fields in Line items (FS10N and FBL3N) but after the upgrade to ECC 6 this fields do not appear even though the configuration is the same that 4.7
Do you have the same problem?? I am stilling looking for OSS notes and threads
_Thanks

FBL3N definitely is available - Purchasing doc.
Anyhow- you can get the fields which is not available by defaulting Sort key for GL account - which will be populated in Assignment field(old allocation field).
Check whether this way problem can be solved
FS10N - is balances and will not be available at all even in old versions and not expected to.

Erro display allocation in G/L account line items by FBL3

Helllo
I changed the line layout that add vendor no. and allocation field to dislpaly line items in FBL3,
the vendor no. is displayed ok as the "2****",but the allocation is displayed that "00002***" as same as the vendor no. ,and when I double click the line item into display document that allocation is ok not the "00002****" .
I have checked the inserted allocation field name is also ZUNOR,what happend? How can I correct this?
Tks a lot for your help!
Best Regards
Liu Jie

no repy

Sort Key JUR and allocation

When invoice sales tax items from the tax conditions are posting to GL tax account document in the allocation field it is always using the txjcd of the shipto but the rate and gl tax amount has been calculated on the plant. Therefore the two don't match and its a reporting nightmare
The sort key field is JUR.
Why would it not use the same txjcd the actual taxes are computed on.
Can any suggest a userexit in place or config?
Any help is rewarded.
Thanks
Richard

You can make a descending sorting for your key figure using the condition TopPercent (Top%) and take the value 100. To sort ascending, use the BottomPercent (Bottom%) condition on your key figure.
Then 100 % of the values of your key figure will be shown in a descending sorting by default in your query (without using a view).
I used the feature in the newest BEx Query Designer (7.x) and it works fine, I don't know if it's available in the older version (3.x).
Please assign points.
Kind regards,
Ben De Windt

Add additional field in the output list

Tcode(VL10G) .ie.out put list will not showing one new field.I want to add one more field to output list. field(VIKP-SDABW) In the SHP_VL10_ITEM and write the logic in the exit LV50R_VIEWG05----
>USEREXIT_PREPARE_LAYOUT_FILL.Plase explain me step-by-step.It is very uggent?Please help me.
Thanks & Regards,
sairam

Hi Sairam,
Go through this info.
/3 provides three "customization spots" that allow you to enhance FI/CO features without modifying the standard code. Although often collectively referred to as "user exits," two of the three have different names. SAP Enhancements are used to expand the standard functionality within SAP. Enhancements use function modules and are called from the standard SAP code. Each module in the system has a set of delivered enhancements that help companies expand the standard functionality where they need it. Enhancements were new in release 3.0.
The Open FI Interfaces or Business Transaction Events are also used to expand the standard functionality within SAP. These events are defined in the IMG. Business Transaction Events were new in release 4.0. They are not available for all modules and are not called on all integrated transactions into FI as of release 4.5B. This will change with each release and should be retested.The older User Exits in FI/CO are "Z" programs that are defined in table T80D for client-dependent user exits, and in table T80I for client-independent user exits. These are also used to expand the standard functionality within the FI/CO modules. These User Exits have been available since the early releases of SAP. All of these FI/CO User Exits are listed in this document in the Configuring User Exits (Older). The list is included because these User Exits are not a part of the Enhancements or Business Transaction Events and do not have an Info System for searching.
Benefits        Standard SAP functionality can be enhanced without modification to the standard code.
        Upgrades do not erase the functionality and it does not have to be re-transported or re-entered into the system. The enhancements should be thoroughly tested when upgrading to ensure the system will still work as implemented.
Configuring SAP Enhancements
Basic Steps in Configuring an Enhancement
        Find the appropriate Enhancement.
        Enter the ABAP code in the "Z" program within the function module.
        Create a project.
        Add the Enhancement to the project.
        Activate the project.
Example Business Scenario for Enhancements
Company A has a requirement to validate all customer master records created with a U.S. address. The U.S. entity reports on the industry field on the customer master. This is only a U.S. requirement and should not be required for the other countries, so the field status would not work. To accomplish this requirement, Company A will need to set up an Enhancement for the customer master transaction. The necessary steps are detailed below with screenprints. This example was configured in a 4.6C system.
Detailed Steps
1.    Tools   ABAP Workbench   Utilities   Enhancements   Definition   Utilities   List Enhancements
2.    Do not execute this without any parameters! There are too many Enhancements and it will probably time out. Youre searching for a customer master exit. Enter mast in the short text (see Figure 1). Youll start there. Searching for an exit can be tricky, so make sure you try several things before giving up.
3.    Execute the search.
Figure 1. Start Your Search for a Master Exit Here
4.    Look through the list until you find the Enhancement for User exits: Customer Master Data.
5.    Double-click on the enhancement SAPMF02D. This will take you to the details of the Enhancement and list the function modules included in the Enhancement.
6.    To continue, double-click on the function module EXIT_SAPMF02D_001
7.    This will take you to the source code for the function module. Click on the Import tab to review the tables/fields that are available for the Enhancement (see Figure 2).
Figure 2. The Tables That Are Available for the Enhancement
8.      To view the tables/fields that can be changed in the function module, click on the Export and Changing tabs. For this function module, these tabs are empty because you can only validate data. You cannot change any fields in this enhancement.
9.      Return to the Source Code tab.
10. Scroll down until you see the Include statement in the program. The "Z" program listed after the Include is where your code will be written (see Figure 3).
Figure 3. Your Program Will Begin After the Include Statement
11.   Double-click on the Include. You will be prompted to create the include. Click on Yes to create.
12.   At this point you will be prompted to enter a development class and to create a transport request. If you do not know which development class to use, please contact your technical team.
13. Enter the following ABAP code into the program (Figure 4):
User exit to ensure that all US customers have a group key
entered on the customer master.
if i_kna1-land1 = 'US' and
i_kna1-brsch = ' '.
message e001(F2).
endif.
Figure 4. The ABAP Code You Need to Enter
14.   Note that the table name matches the table name in the import tab tables.
15.   In this example you are using the standard message class F2 with message number 001. Normally, you will create your own message within your own message class. All customer message classes must begin with a "Z" and are created in transaction SE91.
16. Save the program.
17. The next step is to create the project. Go to transaction code CMOD or follow menu path: Tools   ABAP Workbench   Utilities   Enhancements   Project Management.
18. Enter the project name; begin the name with a "Z."
19. Click on the Create button.
Figure 5. Click on Create After You Type in the Project Name
20.   Enter in a description for the project.
21.   Click on the Enhancement Assignments button.
22.   You will be prompted to save the enhancement. Click on Yes.
23.   At this point you will be asked for a development class and to create a transport for the project. You may use the same one created when adding the ABAP code to the function module.
24. Enter the name of the enhancement SAPMF02D (see Figure 6).
Figure 6. Enter the Name of the Enhancement Here
25. Save the project.
26. Back out of the enhancement assignment.
27. Activate the project by hitting the Activate button.
The SAP Enhancement is ready to be tested! Try creating a customer with U.S. as the country and a blank group key. Be sure to test one with a group key to make sure the message is not displayed in error as well.
Configuring Business Transaction Events
Basic Steps in Configuring an Event
        Make sure the application is active for Business Transaction Events.
        Copy the sample interface function module into a "Z" function module.
        Enter the ABAP code into the source code section of the new "Z" function module. You may choose to create a "Z" program to enter the code into and then insert the "Z" program into your function module source code.
        Activate the function module.
        Assign the function module to the event, country and application.
Example Business Scenario for Business Transaction Events
Company A would like to copy the group key field from the vendor master into the allocation field on all the line items within a vendor invoice and payments, including the vendor lines. This requirement assumes only one vendor is posted to in a document.
To accomplish this requirement, Company A will use the Business Transaction Event 1130, Post Document: SAP Internal Field Substitution.
1.      IMG Menu Path: Financial Accounting   Financial Accounting Global Settings   Use Business Transaction Events   Environment   Infosystem (Processes).
2.      Find the correct Business Event. You are updating a field, so you select the Processes Info System instead of the Publish and Subscribe Info System.
3.      Execute the search with the defaults.
4.      Find the correct interface for updating a document: Post Document: SAP- Internal Field Substitution (see Figure 7).
Figure 7. Find the Correct Interface for the Business Event
5.      Put your cursor on the event and click on the Sample Function Module button.
6.      You are now in transaction SE37 Function Builder. This is the function module (sample_process_00001130) you will need to copy into a "Z" name function module for your coding (see Figure 8).
Figure 8. This Is the Function Module You Need to Copy Your "Z" Name Function Module
7.      Click on the Copy button.
8.      Enter the "Z" function module name in the To Function Module field (see Figure 9).
9.      Enter a Function Group. If you need to create a "Z" function group, go to transaction code SE37 and follow menu path: Go to   Function Groups   Create Group. A function group is a logical grouping of function modules, and the ABAP code is generated for function groups. You will be prompted for a development class and transport when creating the function group.
Figure 9. Enter Your "Z" Function Module Name Here
10. In Function Builder (transaction SE37), enter the new "Z" function module. Click on the Change button.
11. The system will default into the source code screen where you may enter your ABAP code.
12. Notice the tables available for the code. Additional tables may be declared if necessary.
13. Enter the following source code (see Figure 10):
tables: lfa1.
data: z_groupkey like lfa1-konzs.
z_groupkey = ' '.
loop at t_bseg.
check for vendor lines. If one is found, read the vendor master and
retrieve the group key field.
if t_bseg-koart eq 'K'.
select single konzs from lfa1 into z_groupkey
    where lifnr = t_bseg-lifnr.
endif.
Move the group key field into all line items allocation field.
loop at t_bsegsub.
t_bsegsub-zuonr = z_groupkey.
modify t_bsegsub index sy-tabix.
endloop. "t_bsegsub
endloop. "t_bseg
Figure 10. The Screen Where You Enter Your Source Code
14. Save the function module.
15. Back out to the main Function Builder screen by clicking on the green arrow button.
16. Activate the function module by clicking on the Activate button (see Figure 11).
Figure 11. Activate the Function Module from This Screen
17. Assign the function module to the event in the IMG: Financial Accounting   Financial Accounting Global Settings   Business Transaction Events   Settings   Process Function Modules   of an SAP Appl.
18. Hit enter past the warning messages that this is SAP data.
19. Click on the New Entries button.
20. Enter the process for your interface. In your example it is 00001130.
21. Enter the country the interface is valid for. If it is valid for all countries, leave this field blank.
22. Enter the application the interface should be called for. If it should be called for all applications, leave this field blank. Please note that not all integrated transactions are programmed to go through these interfaces! You will need to test to find out!
23. Enter the new "Z" function module (see Figure 12).
Figure 12. Enter Your New "Z" Function Module Here
24. Save the settings. At this point you will be prompted for a CTS number for the configuration change.
25. The Business Transaction Event is complete! You are ready for testing.
Configuring User Exits (Older)
Basic Steps in Configuring an User Exit
      Create a "Z" program for the User Exits and enter the necessary ABAP code.
      Enter the new program name into table T80D.
      Configure the application to call the User Exit.
List of User Exits
      Variable Field Movements
      Substitutions in FI, CO, PCA
      Validations in FI, CO, PCA
      Rollups in SPL
      Fixed Field Movements in SPL
      Cost Center Summarization on Detail Screen
      Sets Formula Variables
Example Business Scenario for User Exits
Company A would like to add a "Z" field in the Special Purpose Ledger to capture a Business Unit field for reporting. They have used all the standard SAP fields such as Business Area and Profit Center. The field will only be used for reporting and is only needed in the Special Purpose Ledger. You created a special ledger table (ZZSPL1) with field Z_BUNIT and need to populate this field based on a combination of G/L account, fund and functional area.
To accomplish this requirement, Company A will use the Variable Field Movement User Exit. To make maintenance easier, table ZZBUSUNIT was created with the G/L account, fund and functional area fields as key fields, and the business unit field as a non-key field. You generated the table maintenance so the table could be updated using transaction SM30. SAP users update the business unit determination rules in table ZZBUSUNIT by entering the G/L account, fund and functional area, and then the business unit that combination should be posting to. The User Exit will read table ZZBUSUNIT using the G/L account, fund and functional area from the posting transaction and determine the business unit. The steps for using the user exit are detailed below. This example was created on a 4.6C system.
1.      Copy the delivered template User Exit program RGIVU000_TEMPLATE into a "Z" program. Follow menu path Tools   ABAP Workbench   Development   ABAP Editor (transaction code SE38). In early releases, the delivered program was RGIVU000.
2.      You will be prompted for a development class and a transport. Please check with the technical team for the correct development class.
3.      At the initial ABAP Editor screen, enter your new "Z" program name, select the Source Code button and click on Change (see Figure 13).
Figure 13. To Enter Your New Code, Select Source Code and Click on the Change Button
4.      Enter the following code in the User Exit (Figure 14):
FORM E01_MVC USING FROM_FIELD TO_FIELD.
to_field = 'CORP'. "Set a default business unit.
read table zzbusunit to determine the business unit field.
select single z_bunit from zzbusunit into to_field
   where hkont = accit_glx-hkont and
    geber = accit_glx-geber and
    fkber = accit_glx-fkber.
ENDFORM.
Figure 14. Enter Your New Code at This Screen.
5.      Activate the program by clicking on the Activate button.
6.      Change the configuration in the User Exit table to point to your new "Z" program.
7.      Follow the IMG menu path: Financial Accounting   Special Purpose Ledger   Basic Settings   User Exits   Maintain Client Specific User Exits.
8.      The entry to maintain is application area GIMV: Variable Field Movement. Enter your "Z" program (see Figure 15).
Figure 15. Enter Your "Z" Program in the Application Area GIMV: Variable Field Movement
9.      Save the changes.
10. The final configuration step is to assign the User Exit in the variable field movement for your special ledger table. In the IMG: Financial Accounting ? Special Purpose Ledger ? Basic Settings ? Master Data ? Maintain Field Movements. Field movements control how the fields in a special ledger table are populated. They can be populated straight from other fields in a posting or through User Exits.
Figure 16. After You Assign the Business Unit Field and the G/L Account, the Exit Field Should Contain U01.
11. Assign the business unit field as a receiver and the G/L account as the sender. The Exit field should contain U01 (see Figure 16).
12. The User Exit number U01 calls User Exit E01_MVC form in the "Z" program.
13. Save the field movement.
14. You are ready to test your User Exit!
Rewords some points.
Rgds,
P.Naganjana Reddy

Use of partner assignement fields

Hi,
I would like to know the 'real' use of partner assignment fields. For instance, we could focus on the 'partner segment' field (the field segment is used as recommended in the standard: the segment is both the SAP field and the IFRS notion of business segment):
Use 1) the partner fields are storing the information of the trading parner : the 'partner segment' is the 'segment' of the 'trading partner'. This is useful when doing preconsolidation routines such as intercompany reconciliation : we reconcile data from company A Segment X with trading partner B partner segment Y
Use 2) the partner fields are storing the historical value of the allocated fields: e.g. when segment 99_TBD is allocated to segment 01, the partner segment field is used to store on line item the relationship between segment 99_TBD and segment 01.
This is useful to track the origin of the data flow for allocations (and for clearing account in document splitting)
Thank you for helping me!
Bernard
Edited by: Bernard Frédéric on Oct 2, 2009 3:28 PM

Business example
Those 2 uses of partner fields are not conciliable : here is a example that shows this inconsistency :
I have a relationship between two companies. On one company, the segment has to be allocated. I have to reconcile data by company code and segment.
Here is the posting in the company where its segment has to be allocated (from 99_TBD to 01):
Company A / Segment 99_TBD / Trading partner B / Partner segment 06 100
I would like to allocate segment 99_TBD to segment 01, so I would expect the following intercompany posting:
Company A / Segment 99_TBD / Trading partner B / Partner segment 06 (100)
Company A / Segment 01         / Trading partner B / Partner segment 06    100
=> Thus, the intercompany positions are:
Company A / Segment 01         / Trading partner B / Partner segment 06    100
This is the result I expected
But when running the allocation cycle, the following is the posted:
Company A / Segment 99_TBD / Trading partner B / Partner segment 01            (100)
Company A / Segment 01         / Trading partner B / Partner segment 99_TBD     100
=> Thus, the intercompany positions are:
Company A / Segment 99_TBD / Trading partner B / Partner segment 06             100
Company A / Segment 99_TBD / Trading partner B / Partner segment 01            (100)
Company A / Segment 01         / Trading partner B / Partner segment 99_TBD     100
This not what is expected: the allocation of company A should have no impact on the segment of company B
Can you help me understand this? How the field partner segment should be used?
Thanks

Leading zeros in the Product allocation characteristic combinations.

Hi All,
I am copying Characteristic combination from planning area to product allocation group, after i complete the transaction system is automatically preceding the zeroes to the product number.
I have one the following activities before copying CVC of planning area to product allocation group.
against all the Product allocation settings.
2.Created the MPOS with product (characteristic length of Product is 18), Customer and Allocation object.
3.Created planning area and planning book.
4.Copied cvc combination from planning are to product allocation group and also copied planning area values in to Product allocation group.
5.Tried to check in the ATP simulation mode, while I was doing system has given no characteristic combination found, when I checked Product is preceding zeros as per the filed MATNR length 40 and this MATNR is selected from the Product allocation field catalog, But when I add zeros to product system is performing Product allocations in simulation mode.
6.Tried triggering gATP Product allocations by creating Order in ECC, here also it has given same error No characteristic combination exists.
When I did initial R&D on this. I found that material number in the product allocation characteristic combination is leading by zeros for ex:- 000000000000000002200325.
Could any one please suggest me what to do on this.
Thanks and Regards,
T.Muthyalappa

Hi Muthyalappa ,
If i have understood your question properly , then my guess is you should be facing this problem only for numeric material codes. Try out the following things
1. Execute the same test condition for a non numeric material. I believe it will work perfectly .
2. For numeric material codes it is not working because of the difference in MATNR length between ECC and APO. In ECC the maximum possible MATNR length is 18 char whereas it is 40 chars in APO. So as per std SAP functionality the numeric materials get concatenated with leading zeros when you try to transfer it (or carry out any kind of processing ) from ECC to APO.
ex consider material 12345. In ECC it will be stored internally as 13 leading zero's followed by12345 . But in APO it will be stored as 35 leading zero's followed by 12345. Your issue is the system does not recognize the CVC that has this material as characteristic. At the time of cvc creation / change make sure your material characteristic ( especially for numeric material codes) totally has 40 chars . Pack it with leading zeros and make the material length 40.
Try this out and update me .
Thanks
Saradha

Product Allocation against STO

Hi,
This is regarding allocation check against stock transport order
1. As per SAP literature, Receiving plant (WERKS_TO) is available as a characteristic for stock transport orders:
(http://help.sap.com/saphelp_scm50/helpdata/en/27/31f938a1914358a9df1fcdc2b454ae/content.htm)
But in the product allocation field catelog, the above field is not present. So how to carry out the allocation check at this level?
2. What is the key figure to update incoming orders quantity. By default AEMENGE is available. Is the same key figure applicable for STO. If not, what is the key figure to update the incoming order quantity for STO. Where can it be added ?
Regards,
RS
Edited by: sap_apo31 on Jan 4, 2012 11:18 AM

Hi RS
1) Receiving Plant can be maintained as a customer with suitable Sales Area. Since customer is available as a characteristic in field catalogue, you can use the same. Alternately, you need to extend the structure (As Michael has advised). This is quite common requirement and your development colleagues will be able to help you.
2) Key figure will remain AMENGE irrespective of whether it is Sales Order or STO.
Thanks,
Prasun

Branch Allocation Field

Similar Messages

Maybe you are looking for