User exit to populate BSEG field during billing doc release

Hi,
Can anyone identify for me a suitable user exit during Billing Document Release that will allow me to populate a field in bseg?
Many thanks,
Ross

I got it, thanks anyway.

Similar Messages

Find out user exits which should trigger while saving billing doc.(VA01)

Hi All,
please can u help me to find out user exits which should trigger while saving billing documents for VA01 transaction...I have already z report to find the user-exit for any transaction.I have tried in that also.
Reply
Ulhas

Hi
Try these
USEREXIT_NUMBER_RANGE (Module pool SAPLV60A, program RV60AFZZ)
The internal number range used in the standard system is specified
in the billing type table and can be changed in this user exit. This
user exit is only called when the billing documents is created.
USEREXIT_ACCOUNT_PREP_KOMKCV (Module pool SAPLV60A, program
RV60AFZZ)
In this user exit additional fields for account determination that
are not provided in the standard system are copied into
communication structure KOMKCV (header fields).
USEREXIT_ACCOUNT_PREP_KOMPCV (Module pool SAPLV60A)
In this user exit additional fields for account determination that
are not provided in the standard system are copied into
communication structure KOMPCV (item fields).
USEREXIT_NUMBER_RANGE_INV_DATE (Module pool SAPLV60A, program
RV60AFZC)
Depending on the number range, table TVFKD is used to set the
billing date (country-specific requirments in Italy).
USEREXIT_NUMBER_RANGE is automatically deactivated when this user
exit is being applied.
USEREXIT_FILL_VBRK_VBRP (Module pool SAPLV60A, program RV60AFZC)
This user exit is only called when the billing document is created.
It is used to provide the header and the item of the new billing
document with deviating or additional data.
USEREXIT_PRINT_ITEM (Module pool SAPLV61A, program RV61AFZB)
Printing the item line of a billing document can be supplemented or
changed.
USEREXIT_PRINT_HEAD (Modulpool SAPLV61A, Programm RV61AFZB)
Printing the header line of a billing document can be supplemented
or changed.
User exits in program RV60AFZD
Short descriptions of the user exits are contained in the program:
-   USEREXIT_RELI_XVBPAK_AVBPAK
-   USEREXIT_NEWROLE_XVBPAK_AVBPAK
-   USEREXIT_NEWROLE_XVBPAP_AVBPAK
e following user exits are available in report SAPLV60B for transfer
accounting (function group V60B):
EXIT_SAPLV60B_001: Change the header data in the structure acchd
You can use this exit to influence the header information of the
accounting document. For example, you can change the business
transaction, "created on" date and time, the name of the person who
created it or the transaction with which the document was created.
EXIT_SAPLV60B_002: Change the customer line ACCIT
You can use this exit to change the customer line in the accounting
document. This exit is processed once the ACCIT structure is filled
in with data from document header VBRK.
EXIT_SAPLV60B_003: Change the customer line in costing
The customer line is filled in differently for costing. You can use
exit 003 to influence the ACCIT structure.
EXIT_SAPLV60B_004: Change a GL account item ACCIT You can add
information to a GL account item (such as quantity specifications)
with this exit.
EXIT_SAPLV60B_005: User exit for accruals
Once all relevant data for accruals was entered in the GL account
item, you can add to this data with this exit.
EXIT_SAPLV60B_006: Change the control line ACCIT
You can use exit 006 to add information to the control line.
EXIT_SAPLV60B_007: Change the installment plan
You can use exit 007 to add information to the installment plan
parameters in the GL account item.
EXIT_SAPLV60B_008: Change the transfer structure ACCCR, ACCIT and
ACCHD
After the accounting document is filled in with data, you can use
exit 008 to change the document once again.
EXIT_SAPLV60B_010: Item table for customer lines
You can use exit 10 to influence the contents of customer lines
before they are created.
EXIT_SAPLV60B_0011: Change the parameter for cash account
determination or reconciliation account determination
You can use this exit to change inbound parameters in order to
influence account determination.
>
Thanks
Shiva

PPCO0007 User Exit for Changing Header Fields During Order (CO40)

.. Hi !!!!
I need your help or suggestions,
I need to change the standar order before to save, i found the user exit PPCO0007,
i assign the new value for the order, but when finish the fuction, EXIT_SAPLCOZV_001, the new values are
lost, and finally the system set the standard order.
Someona know how can change the order and the the batch.
Thanks
Noemí Huerta

Hi Noemi
You can use the enchancement PPCO0007 (exit when the production order is saved).
Use the function module EXIT_SAPLCOZV_001 (User Exit for Checking or Changing Header Fields During Order Save) to update the field priority starting the information in the material-customer info record.

User Exit for making the field Bill of Lading Mandatory in Delivery

Please suggest an User Exit for making the field Bill of Lading Mandatory in the Delivery document when we create an inbound delivery.

Hi,
I'm not sure, pls check these
USEREXIT_SAVE_DOCUMENT_PREPARE
EXIT_SAPLV46H_001
NOTIF_EVENT_SAVE
thanks
Mohanprabu C

User Exit to Populate Data in Uploading Point Field of Transaction MIGO

Hello.
I'm looking for a User Exit or any better way if possible, to populate data in Uploading Point at Transaction MIGO.
Basically my client do not want to enter directly information in this field, in order to avoid data entry errors.
That's why I'm looking for the user exit, to populate the information and my client selected from there.
I appreciate your help.
Hector

Hi
You can use the enhancement MB_CF001 includes a function module that is called up
immediately before the COMMIT WORK when a goods movement is posted.
All the material document data is passed on to this function module from
the following tables:
o   MKPF    (Material document header)
o   MSEG    (Material document items)
o   VM07M   (Update data)
This data can be passed on to other programs.
Regards
Antony

Service master user exit to populate work center description

Hi experts,
In IW31 work order, I need a user exit to populate the work center description to PR delivery address for control key PM03 with Service Master. I have tried and search in vain for other BADI or user exit but none works.
Is there anyone have solution on this?
Thanks.
Regards
PSK

My abaper has tried a few IWO1_PREQ_BADI, IW010009 and WORKORDER_UPDATE.
Operationally, user require the work centre address as the delivery address of the services due to the company has 24 physical workshop locations.
Anyway, will also try to create the fields in AUFK table as recommended.

Can i know the user exits which should trigger while saving billing docu

hi,
please can u help me to find out user exits which should trigger while saving billing documents.

A couple years ago I downloaded this program, I think from SAPFANS. I don't take any credit for it...Not sure who originally wrote it. Just type in the t-code and hit execute.
*& Report name          : Identify and Drill-Down to SAP User Exits.   *
*& Program name         : ZZ_FIND_USER_EXITS                           *
REPORT ZZ_FIND_USER_EXITS
NO STANDARD PAGE HEADING
LINE-SIZE 132
LINE-COUNT 65
MESSAGE-ID MM.
D A T A   D E F I N I T I O N                                        *
TABLES : TSTC,      " SAP Transaction Codes
         TADIR,     " Directory of Repository Objects
         MODSAPT,   " SAP Enhancements - Short Texts
         MODACT,    " Modifications
         TRDIR,     " System Table TRDIR
         TFDIR,     " Function Module
         ENLFDIR,   " Additional Attributes for Function Modules
         TSTCT.     " Transaction Code Texts
S E L E C T I O N   S C R E E N                                      *
PARAMETERS : P_TCODE LIKE TSTC-TCODE OBLIGATORY.
I N T E R N A L   S T R U C T U R E S   &   T A B L E S              *
DATA : GT_TADIR LIKE TADIR OCCURS 0 WITH HEADER LINE.
V A R I A B L E S                                                    *
DATA :
       GV_FIELD1(30) TYPE C,
       GV_DEVCLASS    LIKE TADIR-DEVCLASS.
C O N S T A N T S                                                    *
CONSTANTS:
           GC_F     LIKE TRDIR-SUBC   VALUE 'F',
           GC_R3TR LIKE TADIR-PGMID VALUE 'R3TR',
           GC_FUGR LIKE TADIR-OBJECT VALUE 'FUGR',
           GC_SMOD LIKE TADIR-OBJECT VALUE 'SMOD',
           GC_PROG LIKE TADIR-OBJECT VALUE 'PROG'.
R A N G E S                                                          *
RANGES:
GR_VKORK      FOR WKBP-VKORG.
E V E N T   P R O C E S S I N G                                      *
INITIALIZATION.
AT SELECTION-SCREEN.
SELECT SINGLE PGMNA
    INTO TSTC-PGMNA
    FROM TSTC
    WHERE TCODE = P_TCODE.
IF SY-SUBRC <> 0.
    MESSAGE E899(MM)
      WITH TEXT-E01    " Input Transaction Code is Invalid.
           TEXT-E02.   " Please Correct !!
ENDIF.
SELECT SINGLE TTEXT
    INTO TSTCT-TTEXT
    FROM TSTCT
    WHERE SPRSL = SY-LANGU
      AND TCODE = P_TCODE.
START-OF-SELECTION.
CLEAR GV_DEVCLASS.
SELECT SINGLE DEVCLASS
    INTO GV_DEVCLASS
    FROM TADIR
    WHERE PGMID = GC_R3TR
      AND OBJECT = GC_PROG
      AND OBJ_NAME = TSTC-PGMNA.
IF SY-SUBRC <> 0.
    SELECT SINGLE SUBC
      INTO TRDIR-SUBC
      FROM TRDIR
      WHERE NAME = TSTC-PGMNA.
    IF TRDIR-SUBC = GC_F.         " Function Group
      SELECT SINGLE FUNCNAME
        INTO TFDIR-FUNCNAME
        FROM TFDIR
        WHERE PNAME = TSTC-PGMNA.
      SELECT SINGLE AREA
        INTO ENLFDIR-AREA
        FROM ENLFDIR
        WHERE FUNCNAME = TFDIR-FUNCNAME.
      CLEAR GV_DEVCLASS.
      SELECT SINGLE DEVCLASS
        INTO GV_DEVCLASS
        FROM TADIR
        WHERE PGMID    = GC_R3TR
          AND OBJECT   = GC_FUGR
          AND OBJ_NAME = ENLFDIR-AREA.
    ENDIF.
ENDIF.
SELECT *
    FROM TADIR
    INTO TABLE GT_TADIR
    WHERE PGMID = GC_R3TR
      AND OBJECT = GC_SMOD
      AND DEVCLASS = GV_DEVCLASS.
FORMAT COLOR COL_POSITIVE INTENSIFIED OFF.
WRITE:/(19) 'Transaction Code - ',
          20(20) P_TCODE,
          45(36) TSTCT-TTEXT.
SKIP.
IF NOT GT_TADIR[] IS INITIAL.
    WRITE:/(95) SY-ULINE.
    FORMAT COLOR COL_HEADING INTENSIFIED ON.
    WRITE:/1 SY-VLINE,
           2 'Exit Name',
          21 SY-VLINE ,
          24 'Description',
          95 SY-VLINE.
    WRITE:/(95) SY-ULINE.
    SORT GT_TADIR BY OBJ_NAME.
    LOOP AT GT_TADIR.
      SELECT SINGLE MODTEXT
        INTO MODSAPT-MODTEXT
        FROM MODSAPT
        WHERE SPRSL = SY-LANGU
          AND NAME = GT_TADIR-OBJ_NAME.
      FORMAT COLOR COL_NORMAL INTENSIFIED OFF.
      WRITE:/01 SY-VLINE,
             02 GT_TADIR-OBJ_NAME HOTSPOT ON,
             21 SY-VLINE,
             22 MODSAPT-MODTEXT,
             95 SY-VLINE.
    ENDLOOP.
    WRITE:/(95) SY-ULINE.
    DESCRIBE TABLE GT_TADIR.
    SKIP.
    FORMAT COLOR COL_TOTAL INTENSIFIED ON.
    WRITE:/ 'No of Exits:' , SY-TFILL.
ELSE.
    FORMAT COLOR COL_NEGATIVE INTENSIFIED ON.
    WRITE:/(95) 'No User Exit exists'.
ENDIF.
AT LINE-SELECTION.
GET CURSOR FIELD GV_FIELD1.
IF GV_FIELD1(8) = 'GT_TADIR'.
    SET PARAMETER ID 'MON' FIELD SY-LISEL+1(10).
    CALL TRANSACTION 'SMOD' AND SKIP FIRST   SCREEN.
ELSE.
    MESSAGE I899(MM)
      WITH TEXT-I01    " Click on the Exit Name to Drill-Down
           TEXT-I02.   " to SAP Enhancement Information.
ENDIF.
END-OF-SELECTION.
TOP-OF-PAGE.
S U B R O U T I N E S                                                *
E N D   O F   R E P O R T ****************************************

User exit to populate data

Hii ,
I have to send IDOC ORDERS05 to be extended to add custom fields and code an appropriate user exit . Is there any user exit to populate data ??
They have told me to use RSEOUT00 program to send the orders05 idoc . My main concern is which user exit will I use to populate data ??what are the basic steps to populate data and send the idoc Please let me know .
Thank you

Hi,
Please note that user exits provided in the function module IDOC_OUTPUT_ORDERS.
Use T/Code SE80 and explore function group "XVED". This will give you all the user exit functions in IDOC_OUTPUT_ORDERS.
You can write your code in Zinclude programs .
Ex: ZXVEDU03
CASE SEGMENT-SEGNAM.
    WHEN 'E1EDK01'.
      CLEAR: WK_PLANT, WK_EQUNR, WK_BNDDT,WI_WERKS.
      CLEAR: WK_PLANT_DONE, WK_PRICE_DONE, WK_EQUNR_DONE, WK_BNDDT_DONE.
      CLEAR: WK_BAAN_LINE_PRICE_DONE.
      CLEAR: WK_BAAN_HEAD_PRICE_DONE.
      PRICING_CTR = 3.
    WHEN 'E1EDK14'.
      MOVE SEGMENT-SDATA TO E1EDK14.
      PERFORM Z_EXIT_E1EDK14.
    WHEN 'E1EDP19'.
      XVBAP = DXVBAP.
      MOVE SEGMENT-SDATA TO E1EDP19.
      PERFORM Z_EXIT_E1EDP19.
      DXVBAP = XVBAP.
and soon....

BADI / USER-EXIT FOR DEFAULTING THE FIELD VTTK-TNDR_ACTC IN TCODE VT01N

Hi,
I require a BADI / USER-EXIT for defaulting the field VTTK-TNDR_ACTC(Currency of Actual Shipment costs) to 'EUR' in transaction VT01N(Shipment Transaction) .
Please could anyone help me with this .
Regards,
Sushanth H.S.

Hi!
User Exits in Transportation
In Transportation, there are enhancements that you can use with transaction CMOD.
For a detailed description of the individual enhancements, see the documentation on the individual enhancements or function modules in transaction SMOD.
You can display all enhancements that are available for the area of transportation by choosing F4 in the Enhancement field. Enter V56* in the Enhancement field and choose Execute. Enter V54* to get a list of all enhancements for the area of shipment cost processing.
Business Add-Ins in the transports
Business add-ins (BADIs) are predefined user exits. They enable businesses, partners, and customers to add additional softward to the SAP source code. The linkup of SAP's New Dimension Products, such as APO and BW, to the standard system is thus possible.
Customer-specific functions can be executed before the save time and after the database update.
The following methods are available for the BADI with the definition name 'BADI_LE_SHIPMENT':
AT_SAVE: BADI is called up at the time of the save. Checks and return to dialog are possible.
BEFORE:_UPDATE: BADI is called up right before the data is saved to the database, that is, when all the data is available (for example, internal ly assigned shipment number).
IN_UPDATE: BADI is called up after the database update.
Standard Settings
Creating a BADI method:
Call up transaction SE19. Enter a name of your choice. Choose "create" and in the dialog box enter the definition name 'BADI_LE_SHIPMENT'. Afterwards, enter a short text for implementation. Save the BADI.
On the tab page 'Interface', choose the method for implementation by double-clicking on it. Now you can enter your customer-specific program code. Save and activate the code. You can acess the transmission parameters entered in the BADI definition. With the method ***_AT_SAVE you can initiate the exception ERROR_WITH_MESSAGE (description 'An error message has occurred' ) if you wish to return to the dialog.
Afterwards, go to the heading and activate the interface.
Regards
Tamá

How to find user exits for a specific field

hi,
    How can we find a user exit for a specific fields .
as i know Three ways to search user-exits
1. SE80 look includes in a packages with name user-exits
2. by zreport which will fetch user-exit in a T-CODE
3. SMOD
but what if we have to find a user-exit for particular field for e.g bupla(bussiness place) in MIRO.
Please suggest me.
Thanks and Regards ,
Rahul Singh.

Hi Rahul,
Here is the procedure to create field exits.
Step by step procedure for creating Field Exits
There are eight steps to creating a field exit:
Step 1: Determine Data Element
Step 2: Go To Field Exit Transaction
Step 3: Create Field Exit
Step 4: Create Function Module
Step 5: Code Function Module
Step 6: Activate Function Module
Step 7: Assign Program/Screen
Step 8: Activate Field Exit
Step 1: Determine Data Element
u2022     Before you can begin adding the functionality for a field exit, you must know the corresponding data element.
Step 2: Go To Field Exit Transaction
u2022     The transaction to create field exits is CMOD.
u2022     You can use the menu path Tools -> ABAP/4 Workbench -> Utilities -> Enhancements -> Project management.
u2022     From the initial screen of transaction CMOD, choose the Text enhancements -> Field exits menu path.
u2022     After choosing this menu path, you will be taken to the field exits screen. From here, you can create a field exit.
NOTE : Even though you use transaction CMOD to maintain field exits, you do not need to create a project to activate field exits.
Step 3: Create Field Exit
u2022     From the field exit screen of transaction CMOD, choose the Field exit -> Create menu path.
u2022     After choosing this menu path, a dialog box will prompt you for the appropriate data element .
u2022     Enter the data element name and click the u2018Continueu2019 pushbutton.
u2022     Now, you will be able to create the function module associated to the data elementu2019s field exit.
Step 4: Create Function Module
u2022     You will automatically be taken to the Function Library (SE37) after entering a data element name and clicking the u2018Continueu2019 pushbutton.
u2022     In the u2018Function moduleu2019 field, a function module name will be defaulted by the system based on the data element specified. This name will have the following convention:
FIELD_EXIT_<data element>
u2022     You can add an identifier (an underscore followed by a single character ).
u2022     The first function module for a data elementu2019s field exit must be created without an identifier.
u2022     To create the function module, click on the u2018Createu2019 pushbutton, choose menu path Function module -> Create, or press u2018F5u2019.
u2022     After choosing to create the function module, you will get the warning: "Function module name is reserved for SAP". This message is just a warning so a developer does not accidentally create a function module in the field exit name range. By pressing u2018Enteru2019, you will be able to go ahead and create the function module.
u2022     Before coding the function module, you will have to specify the function modules attributes -- function group, application, and short text.
Step 5: Code Function Module
u2022     From the function moduleu2019s attributes screen, click on the u2018Source codeu2019 pushbutton or choose the Goto -> Function module menu path to the code of the function module.
u2022     Here you will add your desired functionality for the field exit.
u2022     Remember that field exitu2019s function module will have two parameters -- one importing parameter called "INPUT" and one exporting parameter called "OUTPUT". These parameters will be set up automatically by the system.
u2022     You must remember to assign a value to the OUTPUT field. Even if the value does not change, it must be moved from the INPUT field to the OUTPUT field.
Step 6: Activate Function Module
u2022     After coding the function module, you must remember to activate it.
u2022     Use the Function module -> Activate menu path to activate the function module.
u2022     At this point, you can return to the field exit transaction.
u2022     You should be able to 'green arrow' back to this transaction.
u2022     When you return to the field exit transaction, you will see an entry for the newly created field exit.
u2022     At this point, the field exit is global. That is, it applies to all screens that use a particular data element. On any screen that uses the data element, the corresponding field exit function module will be triggered, once it is active.
u2022     Also, the field exit will not be triggered yet because it is inactive.
Step 7: Assign Program/Screen
u2022     This step is only needed if you want to make a field exit local.
u2022     To make a field exit local, select the field exit and click on the u2018Assign prog./screenu2019 pushbutton.
u2022     In the dialog box , indicate the appropriate program name and screen number.
This information indicates that the field exit is local to the specified screen in the specified program.
u2022     In the dialog box, you determine which function module gets executed for the field exit by specifying the identifier in the u2018Fld. Exitu2019 field.
u2022     If this field is left blank, the function module triggered will be 'FIELD_EXIT_<data element>'.
u2022     If a single-character identifier is entered into the field, the function module triggered will be 'FIELD_EXIT_<data element>_<identifier>'.
Step 8: Activate Field Exit
u2022     The field exit must be active for it to be triggered by the system.
u2022     Activate the field exit by choosing the Field exit -> Activate menu path.
u2022     After assigning the field exit to a change request, its status will change to u2018Activeu2019 and it will be triggered automatically on the appropriate screen(s).
NOTE : In order to activate the field exit the profile parameter abap/fieldexit = YES must be set on all application servers
Execute the transaction SE38 with PROGRAM NAME - RSMODPRF
Then give the Data Element Name for which field you want to create the exit(Just cross check with your field data element) and execute.
then it takes you to SE37 with the function module name FIELD_EXIT_<DATA ELEMENT NAME> and then create the same function module.
and in the coding part, You can write your logic to display the output of that field. and activate it.
once you complete the above,
Again execute SE38 transaction with program RSMODPRF and again click on Execute button without any Data Element Name. Now you select the data element which you have created and click on Assign prog/ Screen button and assign the program name and screen number of the filed and click on the menu Field Exit and Activate.
Hope it helps.
Regards
Radhika
Edited by: Radhika Pande on Nov 26, 2009 7:58 AM

MIGO User Exit/BADI to disable field

Hi,
I would like to disable a specific set of fields in MIGO (fields under the GOITEM structure). Is there a BADI (or user exit) I can use to implement this functionality ?
Thanks.

Hi,
My understanding is this BADI is used for modifying the value of the field itself. My requirement is to disable the field (user should not be able to edit the value). Whenever I add the LOOP AT SCREEN statement on this BADI, the screen field GOITEM-CHARG is not processed.
I am actually looking for a BADI/user exit where this screen field can be read.
Thanks.

Field Exit or User Exit for Maintenance Order field.

Dear All,
we need an field exit or an user exit for order(AUFNR)field in PM module.
The Client wants that the value of this field should be validated and for certaion condition an error message should be given while saving an invoice for this order.
Kindly provide the user exit ..
Its urgent.
Thansk in advance ..
regards
Ajay.

Implement Field Exit within program
For this example I am using dta element 'EBELN' from table EKKO.
Step 1: Execute program 'RSMODPRF', entering the data element of the field
Step 2:Create function module when prompted, and add you code to the source section using the parameter 'INPUT' as the field value you are checking
Step 3:      Save and activate Function and execute transaction 'CMOD'.
Step 4:      Choose option: Goto-> Text Enhancements->Data elements->New DE cust docu.
Step 3:      Save and activate Function and execute transaction 'CMOD'.
Step 4:      Choose option: Goto-> Text Enhancements->Data elements->New DE cust docu.
Step 5:      Enter data element
Step 6:      Save and activate
Step 7: Execute program 'RSMODPRF' again but this time leave data element field blank. Step 8: Select the checkbox for the data element you have just created and choose option: Field exit->Activate This will now be active for all instances of this data element, but you can assign specific program and screen combinations by pressing the 'Assign prog./screen' button. You can also change the code you entered in the field exit function module by pressing the 'Edit FM' button.
regards
vinod

User Exit to Populate Document number and latest Version in ME21N

Hi,
I am looking to populate :
Document Type (DRAW-DOKAR)
Document Number (DRAW-DOKNR)
while creating Purchase order (ME21N).
I know the tables DRAD and DRAW can be used to get Document Info by populating EKPO-MATNR as Object key.
But is there a user exit to populate it at the time of PO creation.
Found a BADI Document_Number01 but that does not take EKPO-MATNR as input parameter.
Any inputs are really appreciated.

hi,
check these exits.
MM06E003                                Number range and document number
M06B0004                                Number range and document number
M06B0003                                Number range and document number
also check these badi's.
ME_PROCESS_PO_CUST                      Enhancements for Processing Enjoy Purchase Order: Customer
ME_PURCHDOC_POSTED                      Purchasing Document Posted

How can I have a checkbox that a user checks and populates a field with read only text, then if another checkbox is checked it will allow user text input

Hi
How can I have a check box that a user checks and populates a field with read only text, then if another check box is checked it will allow user text input into that same field, her is my javascript
var a ="Not Applicable"
if (this.getField("Do").value == "Yes")
a=""
if (this.getField("DoNot").value =="Yes")
a=a + ""
event.value=a
say if the "Do" cb is checked, Not Applicable would populate the text field, and if the "DoNot" cb is checked it would allow user input into the same text field, the javascript I have will not allow user input,
thanks for any help I am new to javascript

Are these fields mutually exclusive?

Tax invoice not show in assignment field of billing doc & ref doc of FI doc

Dear Gurues
Does anyone know how to able to display Tax invoice numbering at the assignment field of Billing doc and reference doc header field in FI doc generated by posting billing doc. Also post through POS IDoc?
I have change SD config to correct the existing non vat billing to be able to record vat billing. The result seem ok when I enter regular billing, system generate FI doc with Psk01 customer, Psk50 Revenue acc, output tax. This shows Tax invoice number at reference doc header and assignment field at output tax line item. Assignment field of billing doc is also display.
But when entering to billing with a dummy article (same meaning as material master) that was set up to GL acc, I found that the FI doc after posting billing show a billing doc number instead of Tax invoice number at reference doc header field. This result is same when post thru POS IDoc as well. (FI doc is Psk40 Cash on hand, Psk50 Revenue acc, output tax)
Out put tax acc has sort key as 009 - external doc number
Your suggestion is mostly appreciated.
Yours sincerely,
Kulsri K.

OK I can clear it now. Just set tax category to Dummy Article to be Full tax then Tax sequence number is running.

User exit to populate BSEG field during billing doc release

Similar Messages

Maybe you are looking for