LSMW Upload FI DOC POSTING data problem (FB013, RFBIBL01)

Hello,
I have to upload FI DOC POSTING data with LSMW.
I'm using a batch input with the program RFBIBL01.
In the step "Create batch input session", I get the following error:
FB006     Session 1 : Transferred client 00M differs from system client 500
FB015     ... Session record ...
FB014     ... BGR00-STYPE 0
FB014     ... BGR00-GROUP ###########5
FB014     ... BGR00-MANDT 00M
FB014     ... BGR00-USNAM ISCOB 0
FB014     ... BGR00-START 0000000X
FB014     ... BGR00-XKEEP /
FB014     ... BGR00-NODATA
FB013     ....Editing was terminated
Does anyone know how to solve this error?
Kind regards,
Mahnk

hi,
pls refer to the error message:
FB014 ... BGR00-GROUP ###########5
FB014 ... BGR00-MANDT 00M
FB014 ... BGR00-USNAM ISCOB 0
00M sounds strange for a client?!
here is a displacement!!!!
the 5 in group belongs to the mandant and the M to the usnam i think
so change structure BGR00
A.
pls reward useful answers
thank you!
Message was edited by: Andreas Mann

Similar Messages

Uploading customer invoice posting data from a flatfile(oracle) into FB01

Hi,
      i have to upload the customer invoice data from a flat file and post into FB01.
      if any body worked with this plz send me the sample code regarding customer invoice.i have the following fields
BLDAT-BKPF
BLART-BKPF
BUKRS-BKPF
BUDAT-BKPF
MONAT-BKPF
WAERS-BKPF
BELNR-BKPF
XBLNR-BKPF
BKTXT-BKPF
GSBER-BSEG
BSCHL-BSEG
HKONT-BSEG     Gl Account|
DMBTR-BSEG     Amount     |
HKONT-BSEG     GL Account
DMBTR-BSEG     amount
HKONT-BSEG
DMBTR-BSEG
HKONT-BSEG
DMBTR-BSEG
HKONT-BSEG
DMBTR-BSEG
HKONT-BSEG
DMBTR-BSEG
HKONT-BSEG
DMBTR-BSEG
HKONT-BSEG
DMBTR-BSEG
HKONT-BSEG
DMBTR-BSEG
HKONT-BSEG
DMBTR-BSEG
KOSTL-BSEG
PRCTR
SGTXT     Text
BSCHL-BSEG
LIFNR-BSEG     Vendor account(Employee No.)
                PART II
SAP TABLE     Field description
XBLNR-BKPF     Reference
GSBER-BSEG     Business Area
BLDAT-BKPF     Document Date
KUNNR-KNA1     Cusomer Number
AUFNR-COBL     Order Number
HKONT-BSEG     Gl Account
DMBTR-BSEG     Amount
for tax, insurace ,freight etc.,    a seperate Gl account is created.
regards
veni

hi,
use report rfbibl00:
1) look documentation with se38
2) use structures bgr00, bbkpf, bbseg
3) look sample-prg RFBIBLT0
A.
Message was edited by:
        Andreas Mann

Posting date problem

Dear cons
I made the goods receipt on 16.10.2007. I made the goods issue by mistake on 01.10.2007( instead of 01.11.2007). but the system accecpts it. so when I saw the stock on posting date(T-code mb5b) the system gives wrong information. How can I solve it. pl. give me all the details.
thanks
nirupama

Hi Nirupama,
Use Tcode:
MBST________MATERIAL DOCUMENT NO.
CANCEL IT.
AGAIN GO FOR A FRESH GOODS ISSUE.
REGARDS,
ASHOK

LSMW-Uploading G/l master Data

Hello,
we are migrating Data from R/3 4.6 to ECC 6.0.We need all the G/l from 4.6 exactly same way in ECC 6.0 without new G/l features.
Please let me which table I should use to extract g/l master data (SKA1or SKB1) from 4.6.I am going to do recording with Tcode FS00 at the time of uploading.
If any one is having document on G/l uploading please share with me.share the useful points relating to this.
Many Many Thanks
Moderator: Please, search SDN

Hi,
You will neet to extract data from both SKA1 and SKB1 and need to compile (via lookup etc.) to make a single file for uploding in LSMW.
Regards,
Gaurav

Lsmw Uploading cost center master data fields ERFNM,ERFDT at History tab

Hi Gurus,
I done uploading of cost center master data through LSMW.everything is fine but I have one issue.
I done Uploading from 4.6 now in 4.6 the cost center was created by some one else when I am doing in ECC 6.0 system automatically taking my name as default it means I can not enter in ECC 6.o that who originally created it and what was that date. Is there any way to solve it or system will take only mine name in Fields( ERFNM,ERFDT )at cost center History Data while creating Master data.
Many Many Thanks

Yes, system will take the creator name from the person who actually creates the cost center in SAP.
It will be filled automatically and you can not change the creator name.
This is to ensure better audit trail and tracability.
Regards,
Gaurav

Customer master LSMW: Upload of multiple tax categories problem

Hi All,
I am using standard batch input method (RFBIDE00) for creating Customer Master.
In Sales Area Data-> Billing Document tab-> TAXES there are two rows, one for tax category MWST and the other for ZPFS.
In each i need to fill the field TAXKD (TAX CLASSIFICATION) .
In my LSMW there is structure BKNVI which has got all the tax related fields:
Departure country (ALAND):
Tax category (TATYP):
Tax Classification (TAXKD):
Here I need to populate 2 tax categories and hence I have to call the structure BKNVI two times each time passing the tax details for 2 different tax categories.
Any pointers on how to do this.
When i go for LSMW this is the error i'm getting ....
ERROR:
Check tax classification; maintenance is incomplete
Message no. F2269
thanks,
Gaurav Joshi

I usually do it like this:
                    Code:    BKNVI = INIT_BKNVI.
STYPE                        Batch Input Interface Record Type
                    Rule :   Default Settings
                    Code:    BKNVI-STYPE = '2'.
TBNAM                        Table Name
                    Rule :   Default Settings
                    Code:    BKNVI-TBNAM = 'BKNVI'.
ALAND                        Departure country (country from which the goods are sent)
                    Source: INP_STRUCT_01-TAX_COUNTRY (Tax country)
                    Code:    BKNVI-ALAND = INP_STRUCT_01-TAX_COUNTRY.
TATYP                        Tax category (sales tax, federal sales tax,...)
                    Source: INP_STRUCT_01-TAX_CAT (Tax category)
                    Rule :   Transfer (MOVE)
                    Code:    BKNVI-TATYP = INP_STRUCT_01-TAX_CAT.
TAXKD                        Tax classification for customer
                    Source: INP_STRUCT_01-TAX_CLASS (Taxable Classification)
                    Code:    BKNVI-TAXKD = INP_STRUCT_01-TAX_CLASS.
Save for NO
                             TRANSFER_RECORD.
Save for SE
                             BKNVI-ALAND = 'SE'.
                             BKNVI-TAXKD = '1'.
                             TRANSFER_RECORD.
Then add for DK (Saved automatically)
                             BKNVI-ALAND = 'DK'.
                             BKNVI-TAXKD = '1'.
Regards
Roy Olav Johansen
TechWeaver

COGI - Diference between Error date, Creation date & posting date

Hi All,
While running COGI report, I could see columns " Creation Date" , "Error Date", But I could not get the meaning of this fields from the F1 Help. could anuone of you please help me with the relevancy of these columns.
Also the Posting date some time doesn't match either of the dates.
Thanks & reagrds
Mahesh

Mahesh,
I think I have interchanged the terminoly:
What Creation date is the date when the item was created in the COGI. Error date is the date when the error was first created. The error message might change then the date of new error message is the error date.
Example: When COGI was created it came due to deficit of stock. Now you have the stock but try to post you get the "Posting date problem". So the error date now is the latest date when the new error occured. But still the creation date is the original.
Sorry for confusing you.
Regards
Ram
Message was edited by:
Ramanujan Chitrakootam

Problem in Uploading sales order text data using LSMW

Hi All,
I am facing Problem in uploading open sales order data from legacy to SAP using LSMW.
We are trying to upload sales order data using LSMW Standard Batch/Direct input using program name RVINVB10 and program type D. We are not able to upload item text but have no problem in uploading remaining data.
the details we are passing to BTEXHKOM structure are......
BTEXHKOM-OLDNR = IHEADER-OLDORD_NO.
BTEXHKOM-LAISO = 'EN'.
BTEXHKOM-TDID = 'Z009'.
and the for structure BTEXLKOM
BTEXLKOM-OLDNR = IHEADER-OLDORD_NO.
BTEXLKOM-TXPARGRAPH = '/'.
CONCATENATE LITEM-DEPTID LITEM-DEPTNAME
INTO BTEXLKOM-TXLINE SEPARATED BY ' '.
we have three input source structures.
IHEADER Header structure
LITEM Line item structure ( Material data )
IPARTN Partners structure
The structure relationships are
BTEXHKOM <<< IHEADER.
BTEXLKOM <<< IHEADER.
Please let me know if I am doing some thing wrong or some thing else need to be done.
Thanks,
Chindam.

you can pass below values also
OLDNR : order number and item nuber
TXPARGRAPH : VBBK
TXLINE : your text.....

'Create' Push button is not working in BDC and LSMW while uploading G/L master data

Hello Experts:
I am facing the following problem:
While uploading G/L master data with the BDC program, 'create' push button is not working even after executing following lines.
PERFORM BDC_DYNPRO USING 'SAPLGL_ACCOUNT_MASTER_MAINTAIN' '2001'.
PERFORM BDC_FIELD USING 'BDC_OKCODE'
 '=ACC_CRE'.
Create G/L account screen is not coming in BDC. Please suggest me what to do.
Thanks !!

Re: 'Create' Push button is not working in BDC and LSMW while uploading G/L master data
Re: 'Create' Push button is not working in BDC and LSMW while uploading G/L master data
Hi Glen Anthony
Thank you for the reply Glen Anthony please take a look at the following code.
REPORT ZFI_BDC_FS00
 NO STANDARD PAGE HEADING LINE-SIZE 255.
*INCLUDE BDCRECX1.
TYPES : BEGIN OF STR,
 BUKRS TYPE GLACCOUNT_SCREEN_KEY-BUKRS, "Company Code
 SAKNR TYPE GLACCOUNT_SCREEN_KEY-SAKNR, "G/L Account Number
 KTOKS TYPE GLACCOUNT_SCREEN_COA-KTOKS, "G/L Account Group
 XPLACCT TYPE GLACCOUNT_SCREEN_COA-XPLACCT, "P&L statement account
 XBILK TYPE GLACCOUNT_SCREEN_COA-XBILK, "Indicator: Account is a balance sheet account?
 TXT20_ML TYPE GLACCOUNT_SCREEN_COA-TXT20_ML, "G/L account short text
 TXT50_ML TYPE GLACCOUNT_SCREEN_COA-TXT50_ML, "G/L account short text
 WAERS TYPE GLACCOUNT_SCREEN_CCODE-WAERS, "Account currency
 XSALH TYPE GLACCOUNT_SCREEN_CCODE-XSALH, "Indicator: Only Manage Balances in Local Currency
 MWSKZ TYPE GLACCOUNT_SCREEN_CCODE-MWSKZ, "Tax Category in Account Master Record
 XMWNO TYPE GLACCOUNT_SCREEN_CCODE-XMWNO, "Indicator: Tax code is not a required field
 MITKZ TYPE GLACCOUNT_SCREEN_CCODE-MITKZ, "Account is reconciliation account
 XOPVW TYPE GLACCOUNT_SCREEN_CCODE-XOPVW, "Indicator: Open item management?
 XKRES TYPE GLACCOUNT_SCREEN_CCODE-XKRES, "Indicator: Can Line Items Be Displayed by Account?
 ZUAWA TYPE GLACCOUNT_SCREEN_CCODE-ZUAWA, "Key for sorting according to assignment numbers
 FSTAG TYPE GLACCOUNT_SCREEN_CCODE-FSTAG, "Field status group
 XINTB TYPE GLACCOUNT_SCREEN_CCODE-XINTB, "Indicator: Is account only posted to automatically?
 END OF STR.
DATA : ITAB TYPE TABLE OF STR WITH HEADER LINE,
 IT_BDCDATA TYPE TABLE OF BDCDATA WITH HEADER LINE,
 TXT(4096) TYPE C OCCURS 0,
 MSG TYPE STRING,
 COUNT(5) TYPE N.
SELECTION-SCREEN : BEGIN OF BLOCK B1 WITH FRAME TITLE TEXT-001.
 PARAMETERS : MY_FILE TYPE RLGRAP-FILENAME.
SELECTION-SCREEN : END OF BLOCK B1.
AT SELECTION-SCREEN ON VALUE-REQUEST FOR MY_FILE.
CALL FUNCTION 'F4_FILENAME'
EXPORTING
 PROGRAM_NAME = SYST-CPROG
 DYNPRO_NUMBER = SYST-DYNNR
* FIELD_NAME = ' '
IMPORTING
 FILE_NAME = MY_FILE
CALL FUNCTION 'TEXT_CONVERT_XLS_TO_SAP'
 EXPORTING
* I_FIELD_SEPERATOR =
* I_LINE_HEADER =
 I_TAB_RAW_DATA = TXT
 I_FILENAME = MY_FILE
 TABLES
 I_TAB_CONVERTED_DATA = ITAB[]
EXCEPTIONS
 CONVERSION_FAILED = 1
 OTHERS = 2
IF SY-SUBRC <> 0.
* IMPLEMENT SUITABLE ERROR HANDLING HERE
ENDIF.
START-OF-SELECTION.
COUNT = 0.
LOOP AT ITAB.
*PERFORM OPEN_GROUP.
REFRESH IT_BDCDATA.
PERFORM BDC_DYNPRO USING 'SAPLGL_ACCOUNT_MASTER_MAINTAIN' '2001'.
PERFORM BDC_FIELD USING 'BDC_CURSOR'
 'GLACCOUNT_SCREEN_KEY-BUKRS'.
PERFORM BDC_FIELD USING 'BDC_OKCODE'
 '=ACC_CRE'.
*PERFORM BDC_FIELD USING 'BDC_CURSOR'
* 'GLACCOUNT_SCREEN_KEY-BUKRS'.
PERFORM BDC_FIELD USING 'GLACCOUNT_SCREEN_KEY-SAKNR'
 ITAB-SAKNR. "'5'.
PERFORM BDC_FIELD USING 'GLACCOUNT_SCREEN_KEY-BUKRS'
 ITAB-BUKRS. "'TATA'.
PERFORM BDC_DYNPRO USING 'SAPLGL_ACCOUNT_MASTER_MAINTAIN' '2001'.
PERFORM BDC_FIELD USING 'BDC_OKCODE'
 '=2102_GROUP'.
PERFORM BDC_FIELD USING 'BDC_CURSOR'
 'GLACCOUNT_SCREEN_COA-KTOKS'.
PERFORM BDC_FIELD USING 'GLACCOUNT_SCREEN_COA-KTOKS'
 ITAB-KTOKS. "'GL'.
PERFORM BDC_FIELD USING 'GLACCOUNT_SCREEN_COA-XPLACCT'
 ITAB-XPLACCT. "'X'.
PERFORM BDC_DYNPRO USING 'SAPLGL_ACCOUNT_MASTER_MAINTAIN' '2001'.
PERFORM BDC_FIELD USING 'BDC_OKCODE'
 '=2102_BS_PL'.
PERFORM BDC_FIELD USING 'BDC_CURSOR'
 'GLACCOUNT_SCREEN_COA-XBILK'.
PERFORM BDC_FIELD USING 'GLACCOUNT_SCREEN_COA-KTOKS'
 ITAB-KTOKS. "'GL'.
PERFORM BDC_FIELD USING 'GLACCOUNT_SCREEN_COA-XPLACCT'
 ITAB-XPLACCT. "''.
PERFORM BDC_FIELD USING 'GLACCOUNT_SCREEN_COA-XBILK'
 ITAB-XBILK. "'X'.
PERFORM BDC_DYNPRO USING 'SAPLGL_ACCOUNT_MASTER_MAINTAIN' '2001'.
PERFORM BDC_FIELD USING 'BDC_OKCODE'
 '=TAB02'.
PERFORM BDC_FIELD USING 'GLACCOUNT_SCREEN_COA-KTOKS'
 ITAB-KTOKS. "'GL'.
PERFORM BDC_FIELD USING 'GLACCOUNT_SCREEN_COA-XBILK'
 ITAB-XBILK. "'X'.
PERFORM BDC_FIELD USING 'BDC_CURSOR'
 'GLACCOUNT_SCREEN_COA-TXT50_ML'.
PERFORM BDC_FIELD USING 'GLACCOUNT_SCREEN_COA-TXT20_ML'
 ITAB-TXT20_ML. "'G/L ACCOUNT'.
PERFORM BDC_FIELD USING 'GLACCOUNT_SCREEN_COA-TXT50_ML'
 ITAB-TXT50_ML. "'G/L ACCOUNT'.
PERFORM BDC_DYNPRO USING 'SAPLGL_ACCOUNT_MASTER_MAINTAIN' '2001'.
PERFORM BDC_FIELD USING 'BDC_OKCODE'
 '=TAB03'.
PERFORM BDC_FIELD USING 'GLACCOUNT_SCREEN_CCODE-WAERS'
 ITAB-WAERS. "'INR'.
PERFORM BDC_FIELD USING 'GLACCOUNT_SCREEN_CCODE-XSALH'
 ITAB-XSALH. "'X'.
PERFORM BDC_FIELD USING 'GLACCOUNT_SCREEN_CCODE-MWSKZ'
 ITAB-MWSKZ. "'*'.
PERFORM BDC_FIELD USING 'GLACCOUNT_SCREEN_CCODE-XMWNO'
 ITAB-XMWNO. "'X'.
PERFORM BDC_FIELD USING 'GLACCOUNT_SCREEN_CCODE-MITKZ'
 ITAB-MITKZ. "''.
PERFORM BDC_FIELD USING 'BDC_CURSOR'
 'GLACCOUNT_SCREEN_CCODE-ZUAWA'.
PERFORM BDC_FIELD USING 'GLACCOUNT_SCREEN_CCODE-XOPVW'
 ITAB-XOPVW. "'X'.
PERFORM BDC_FIELD USING 'GLACCOUNT_SCREEN_CCODE-XKRES'
 ITAB-XKRES. "'X'.
PERFORM BDC_FIELD USING 'GLACCOUNT_SCREEN_CCODE-ZUAWA'
 ITAB-ZUAWA. "'1'.
PERFORM BDC_DYNPRO USING 'SAPLGL_ACCOUNT_MASTER_MAINTAIN' '2001'.
PERFORM BDC_FIELD USING 'BDC_OKCODE'
 '=SAVE'.
PERFORM BDC_FIELD USING 'BDC_CURSOR'
 'GLACCOUNT_SCREEN_CCODE-XINTB'.
PERFORM BDC_FIELD USING 'GLACCOUNT_SCREEN_CCODE-FSTAG'
 ITAB-FSTAG. "'G019'.
PERFORM BDC_FIELD USING 'GLACCOUNT_SCREEN_CCODE-XINTB'
 ITAB-XINTB. "'X'.
*PERFORM BDC_TRANSACTION USING 'FS00'.
CALL TRANSACTION 'FS00' USING IT_BDCDATA MODE 'E' UPDATE 'S'.
COUNT = COUNT + 1.
*PERFORM CLOSE_GROUP.
ENDLOOP.
CONCATENATE COUNT ' RECORDS UPDATED SUCCESSFULLY' INTO MSG.
MESSAGE MSG TYPE 'I'.
FORM BDC_DYNPRO USING PROGRAM DYNPRO.
 CLEAR IT_BDCDATA.
 IT_BDCDATA-PROGRAM = PROGRAM.
 IT_BDCDATA-DYNPRO = DYNPRO.
 IT_BDCDATA-DYNBEGIN = 'X'.
 APPEND IT_BDCDATA.
ENDFORM.
* INSERT FIELD *
FORM BDC_FIELD USING FNAM FVAL.
* IF FVAL <> NODATA.
 CLEAR IT_BDCDATA.
 IT_BDCDATA-FNAM = FNAM.
 IT_BDCDATA-FVAL = FVAL.
 APPEND IT_BDCDATA.
* ENDIF.
ENDFORM.

Lsmw date problem

hi friends,
i am trying to upload po using lsmw by direct input method.
only problem is it is not taking delivery date properly.
at the end error message is 'plz enter valid delivery date'.
can any one tell me why it is happning.
thanks
sonu

and this also
BAPI method
http://****************/Tutorials/LSMW/BAPIinLSMW/BL2.htm
Check out this thread
LSMW - Using a BAPI
http://help.sap.com/saphelp_erp2004/helpdata/en/d4/0a43a124e8924ea890cf0855860db5/content.htm

DTW Good Receipt Doc. date and Posting Date

Dear Professional,
I have tried to use the DTW Good Receipt Template (oInventoryGenEntry) to unpload the initial open on-hand inventory into B1.
However, no matter the DocDate (Posting Date) and TaxDate (Doc. Date) I have entered into the Document Template, the system still set "Today" as both Posting Date and Doc. Date after completed uploading the inventory on-hand, is there anything can help to solve or something I missed ??
Thank,
Deckard

Dear Deckard,
When I did the this DTW, I found the same issue. B1 probably not allow to import back dated Good Receipt transactions by DTW.
Thanks,
Gordon

LSMW upload - data doent not reflect in transaction

Hi ALl,
I have an LSMW upload... where i upload data into a transaction.. once a transaction is complete it displays message as successful but when i go into that transaction it doesnt reflect data....... what can be the problem???

I dont have this transaction in my system as we dont use extended WM.
However, what you wrote is a kind contrary within :
when fresh records are uploaded hrough LSMW then they are uploaded...but when we go to that tcode
then records are not there.
. but when we manully entering these records then error msg comes that these records are already exists
is this /SCWM/RSRC transaction a transaction that does display, create and change in one transaction?
so that you cannot get your data when doing display but get the error when clicking create?
or do you use a different transaction to create the records?
you are saying you loaded with batch input in LSMW, was this batch input a recording, or a standard given SAP method ?

Goods Receipt and Goods Issue - Posting Date and Document Date Problem

Hi All,
I was using SDK to build own add on to insert Posting Date and Document Date under Inventory> Inventory Transactions> Goods Receipt and Inventory> Inventory Transactions> Goods Issue, but the UI Screen Posting Date and Document Date shown current date.
My SAP Business One version was 2007A SP00 PL42 and alreadly upgrade to SP05.
End up result still the same.
Is there someone can help me?
Thanks you.
Best Regards,
danny

Hi there,
I already solve it by myself.
Actually is i call the initialization twice:
Company.GetBusinessObject(SAPbobsCOM.BoObjectTypes.oInventoryGenEntry)
Thats what make this problem happened.
Sorry.
Best Regards,
danny

Difference between doc date,posting date and invoice date

hi bw guys
can someone give a brief on the difference between doc date,posting date and invoice date.and the invidual definitions
thank you

Hi,
Posting Date: Date which is used when entering the document in Financial Accounting or Controlling. The posting date can differ from both the entry date and the doc date.
Document Date: The document date is the date on which the original document was issued. Ex: Inv date, Bill date etc.,
Invoice Date : Usually the date when goods are shipped. Payment dates are set relative to the invoice date.
-Vikram

LSMW Upload SalesOrder Creation:problem in assigning Partner type SH and SP

Hi
I'm trying to upload sales order creation data using LSMW -BAPI Method
Business Object : BUS2032
Method : CREATEFROMDAT2
Message type : SALESORDER_CREATEFROMDAT2
Basic Type : SALESORDER_CREATEFROMDAT202
and I'm passing the following header data
Sales Order Type, Sales organisation, Distribution Channel, Division, Sold To Party, Ship To party,
Purchase order number, PO Date, Requested delivery date, Order Reason, Payment terms, Incoterms part1, Incoterms part2, Document Currency.
and the following item data
MATERIAL NUMBER
Order quantity
Storage Location
Item Category
Item Usage
Reason for Rejection
Plant
Net Weight
Gross Weight
Condition Type
Amount
Internal Order Number
I'm assigning the header data to structure E1BPSDHD1
and Item data to E1BPSDITM,E1BPSDITM1
and Partner data to structure E1BPPARNR.
When I am assigning Partner data to the structure E1BPPARNR, I want to assign both sold-to-party and ship-to-party ,(because I have two source fields of this type) but there is only target field related to the partner data , here I am assigning partner type as SP and partner number as sold-to-party, still there is an unassigned field ship-to-party, for this field I am unable to find a relevant target field so please help me how can I assing These two flat file fields (sold-to-party,ship-to-party)
Looking for further more information : if there is many sold-to-party's and many ship-to-party's how can I go that in this situation i.e maintaining Many to Many relationship using LSMW tool
Thanks in advance
regards
Rajasekhar

Here is what you have to do.
In field mapping, double click on the field PARTN_NUMB (or any field of that structure) in change mode. This opens up the code editor. There just enter the following code. I am assuming you are doing only these fields. But if you are mapping more fields of this structure, you have to map them here.
E1BPPARNR-PARTN_NUMB = ORDERHEADER-KUNAG.
E1BPPARNR-PARTN_ROLE = 'AG'.
E1BPPARNR-ITM_NUMBER = '000000'.
*-- add more field mappings here, if needed
TRANSFER_RECORD.
*-- Now pass the Ship-to record
E1BPPARNR-PARTN_NUMB = ORDERHEADER-KUNWE.
E1BPPARNR-PARTN_ROLE = 'WE'.
E1BPPARNR-ITM_NUMBER = '000000'.
*-- Add more partners if needed by copying the above code.
Remember, you need to do TRANSFER_RECORD only that many times as you have the partners. There will be one 'TRANSFER_RECORD' at the end of this structure, so keep that in mind.
Srinivas

LSMW Upload FI DOC POSTING data problem (FB013, RFBIBL01)

Similar Messages

Maybe you are looking for