LSMW field relations and mappings

Hi,
In LSMW, I need to define multiple relationship to same structure, is that possible ,pls suggest.
The mappings needs to be done in IDOC type PORDCR101, from one field in header structure and another from line-item structure comes from flat file and maps to the same segment E1BPPAREX of the IDOC type PORDCR101,.
Pls suggest.
Thanks in advance
Regards
Anand

Sorry, only one source structure per target structure.
Study the generated conversion program, there is a clumsy workaround by manipulating the internal tables that the LSMW uses.
Thomas

Similar Messages

Re: Error in LSMW Field Mapping and Conversion Rules

Hi Friends,
In Step Field Mapping and Conversion Rules:
Am not able find the fields.
1. I checked the source structure relationship it is ok.
2. I have assigned the fields in recording too.
Please help me out.
Thanks in advance
vivek

hi ram,
I think u have gone wrong in the first step itself............
Do like this,
1) Goto Maintain Object Attributes
2) Select Batch Input Recording and Enter Ur recording Name
3) Then Select Recording Overview...
4) Thne Press DEFAULT ALL on ur Application Toolbar or Select EDIT-> DEFAULT ALL
5) All ur Source Fields will be mapped for Recording Fields......
6) Now u can see ur Fields in Field Mapping and Conversion Step......
I hope this will work u r doing with BATCH INPUT METHOD...
Reward me if useful.......
Harimanjesh AN

Maintain Field Mapping and Conversion Rules//LSMW

Hello Friends,
I want to add new fields in the step.no.5(Maintain Field Mapping and Conversion Rules).
Indetail i'm going to upload the GL balances, for DR and CR line item fields are same so system is not accepting the same field value, so i have added 1 for the CR line item fields like in the below example.
BSEG-WRBTR(Dr line item)
BSEG-WRBTR1(Cr line item)
but BSEG-WRBTR1(Cr line item) field not displaying in the step.no.5 to mapping to source field.
please let me know the solution for this.
thanks
swapna.

Hi,
I would like to ask few questions.
1. Are you using batch input recording or using any program for uploading. (through LSMW)
2. Whether all your debit or credit line items are same every transactions. I believe they should be same, because you are uploading the balances.
You should not have two similar fields for example, if it is WMBTR, then again WMBTR should not be there, it should WMBTR1 and WMBTR2. Make sure you have done the field mapping properly. When you have done the field mapping all the fileds must have been mapped. If any one of the fields are not mapped, then it will not be uploaded.
Please see the following LSMW sample guide:
http://www.scmexpertonline.com/downloads/SCM_LSMW_StepsOnWeb.doc
Maintain Object Attributes Do the recording - Make sure that you do not have two fields with the similar name. If you have two fields with the same name double click on the field name and add1 or 2 to differentiate between field names. Just Copy those fields and descriptions in excel sheet, delete the blank lines, then in excel data => text to columns, your field names and descriptions will be now in two columns. Copy them, then put your cursor on the next sheet, then edit => Paste Special => Transpose, all the columns will become your rows. Now your file structure is ready. Maintain Source Structures Give some unique structure name and description Maintain Source Fields Here you add the fields that are being used in EXCEL first sheet, just copy them and make all the fields as C (Constant) and then give length of 60 for all fields. Maintain Structure Relations Though structure relations are already created just go to this step, click on edit, then click on create structure relation, just accept the message stating that the structure relation has already been created. Maintain Field Mapping and Conversion Rules Do the field mapping for all the fields, all the fields willl be stretched and you will see five rows against each row. In case if there is any row that has NOT stretched means, there is something wrong in the mapping. Maintain Fixed Values, Translations, User-Defined Routines There is nothing to be done at this step. You can simply ignore this. Specify Files Make you must have saved your excel file as .txt (before saving make sure you have copied data from sheet2 to sheet 3 and then sheet 3 is saved at tab delimited file. Text (Tab delimited) Select your file, make SURE that you have select "TABULATOR" radio button and say OK. Assign Files Go to this step and click on Create assignment button and accept the message and say ok. Read Data Remove two check boxes and just click on execute button. See the log. Make sure you have number of entries (lines) in your excel file are matching with this. Display Read Data Display data give 1 to 999 lines and double click on one of the line and see whether fields are mapped correctly are not. Convert Data Execute and see the log match the number of entries. Display Converted Data Display converted data, give 1 to 999 and double click on one of the line and see whether fields are mapped correctly or not. Create Batch Input Session Check on Keep Batch Input sessions check box, then execute. If you select that check box, even after execution it will be there and you can analyze what happened. Run Batch Input Session (Takes you to SM35) Go to SM35 select the batch and click on process button (execute), make sure you have checked right hand side first three check boxes and FOREGROUND (because you want to save what it is creating) Say OK Keep on press ENTER on your key board in order to move the session further. If you follow these steps along with the guide, surely you should be successful. There may be small difference between the file and what I have explained but ultimately the purpose is same. Hope this is useful and let me know in case if you have any issues.
Regards, Ravi

Relation and field ( or relational field) between VBRP + VBAP

hi all,
can anyone pls tell me the relation and field ( or relational field)between VBRP + VBAP

Hi,
U can make use of VBFA (Sales document flow)table for this.
If you have the billing document number and item then provide them in the subsequent document (VBELN) and item(POSNN) fields of VBFA table and provide the preceding doc category as 'C' to get the sales order information.
Similarly if u have the sales order number and item then pass them to the preceding doc and item fields of VBFA and pass the subsequent doc category as 'M' so that u will get the billing doc number.
thasnks and regard

Field Symbols, Field String, and Field Group.

Hi,
Can you differentiate between filed symbols, field strings and field groups,
With regards,
Bharath Mohan B

Hi,
Field Symbols
Field symbols are placeholders or symbolic names for other fields. They do not physically reserve space for a field, but point to its contents. A field symbol cam point to any data object. The data object to which a field symbol points is assigned to it after it has been declared in the program.
Whenever you address a field symbol in a program, you are addressing the field that is assigned to the field symbol. After successful assignment, there is no difference in ABAP whether you reference the field symbol or the field itself. You must assign a field to each field symbol before you can address the latter in programs.
Field symbols are similar to dereferenced pointers in C (that is, pointers to which the content operator * is applied). However, the only real equivalent of pointers in ABAP, that is, variables that contain a memory address (reference) and that can be used without the contents operator, are reference variables in ABAP Objects.
All operations programmed with field symbols are applied to the field assigned to it. For example, a MOVE statement between two field symbols moves the contents of the field assigned to the first field symbol to the field assigned to the second field symbol. The field symbols themselves point to the same fields after the MOVE statement as they did before.
You can create field symbols either without or with type specifications. If you do not specify a type, the field symbol inherits all of the technical attributes of the field assigned to it. If you do specify a type, the system checks the compatibility of the field symbol and the field you are assigning to it during the ASSIGN statement.
Field symbols provide greater flexibility when you address data objects:
If you want to process sections of fields, you can specify the offset and length of the field dynamically.
You can assign one field symbol to another, which allows you to address parts of fields.
Assignments to field symbols may extend beyond field boundaries. This allows you to address regular sequences of fields in memory efficiently.
You can also force a field symbol to take different technical attributes from those of the field assigned to it.
The flexibility of field symbols provides elegant solutions to certain problems. On the other hand, it does mean that errors can easily occur. Since fields are not assigned to field symbols until runtime, the effectiveness of syntax and security checks is very limited for operations involving field symbols. This can lead to runtime errors or incorrect data assignments.
While runtime errors indicate an obvious problem, incorrect data assignments are dangerous because they can be very difficult to detect. For this reason, you should only use field symbols if you cannot achieve the same result using other ABAP statements.
For example, you may want to process part of a string where the offset and length depend on the contents of the field. You could use field symbols in this case. However, since the MOVE statement also supports variable offset and length specifications, you should use it instead. The MOVE statement (with your own auxiliary variables if required) is much safer than using field symbols, since it cannot address memory beyond the boundary of a field. However, field symbols may improve performance in some cases.
check the below links u will get the answers for your questions
http://help.sap.com/saphelp_nw04/helpdata/en/fc/eb3860358411d1829f0000e829fbfe/content.htm
http://www.sts.tu-harburg.de/teaching/sap_r3/ABAP4/field_sy.htm
http://searchsap.techtarget.com/tip/1,289483,sid21_gci920484,00.html
Syntax Diagram
FIELD-SYMBOLS
Basic form
FIELD-SYMBOLS <fs>.
Extras:
1. ... TYPE type
2. ... TYPE REF TO cif
3. ... TYPE REF TO DATA
4. ... TYPE LINE OF type
5. ... LIKE s
6. ... LIKE LINE OF s
7. ... TYPE tabkind
8. ... STRUCTURE s DEFAULT wa
The syntax check performed in an ABAP Objects context is stricter than in other ABAP areas. See Cannot Use Untyped Field Symbols ad Cannot Use Field Symbols as Components of Classes.
Effect
This statement declares a symbolic field called <fs>. At runtime, you can assign a concrete field to the field symbol using ASSIGN. All operations performed with the field symbol then directly affect the field assigned to it.
You can only use one of the additions.
Example
Output aircraft type from the table SFLIGHT using a field symbol:
FIELD-SYMBOLS <PT> TYPE ANY.
DATA SFLIGHT_WA TYPE SFLIGHT.
ASSIGN SFLIGHT_WA-PLANETYPE TO <PT>.
WRITE <PT>.
Addition 1
... TYPE type
Addition 2
... TYPE REF TO cif
Addition 3
... TYPE REF TO DATA
Addition 4
... TYPE LINE OF type
Addition 5
... LIKE s
Addition 6
... LIKE LINE OF s
Addition 7
... TYPE tabkind
Effect
You can define the type of the field symbol using additions 2 to 7 (just as you can for FORM parameters (compare Defining the Type of Subroutine Parameters). When you use the ASSIGN statement, the system carries out the same type checks as for USING parameters of FORMs.
This addition is not allowed in an ABAP Objects context. See Cannot Use Obsolete Casting for FIELD SYMBOLS.
In some cases, the syntax rules that apply to Unicode programs are different than those for non-Unicode programs. See Defining Types Using STRUCTURE.
Effect
Assigns any (internal) field string or structure to the field symbol from the ABAP Dictionary (s). All fields of the structure can be addressed by name: <fs>-fieldname. The structured field symbol points initially to the work area wa specified after DEFAULT.
The work area wa must be at least as long as the structure s. If s contains fields of the type I or F, wa should have the structure s or at least begin in that way, since otherwise alignment problems may occur.
Example
Address components of the flight bookings table SBOOK using a field symbol:
DATA SBOOK_WA LIKE SBOOK.
FIELD-SYMBOLS <SB> STRUCTURE SBOOK
DEFAULT SBOOK_WA.
WRITE: <SB>-BOOKID, <SB>-FLDATE.
Related
ASSIGN, DATA
Additional help
Declaring Field Symbols
FIELD GROUPS
are used to hold/handle large amount of data when the internal table are not useful
we use EXTRACT statement, HEADER structure in them
see the example
REPORT demo_extract.
NODES: spfli, sflight.
FIELD-GROUPS: header, flight_info, flight_date.
START-OF-SELECTION.
INSERT: spfli-carrid spfli-connid sflight-fldate
            INTO header,
          spfli-cityfrom spfli-cityto
            INTO flight_info.
GET spfli.
EXTRACT flight_info.
GET sflight.
EXTRACT flight_date.
END-OF-SELECTION.
SORT STABLE.
LOOP.
    AT FIRST.
      WRITE / 'Flight list'.
      ULINE.
    ENDAT.
    AT flight_info WITH flight_date.
      WRITE: / spfli-carrid , spfli-connid, sflight-fldate,
               spfli-cityfrom, spfli-cityto.
    ENDAT.
    AT flight_date.
      WRITE: / spfli-carrid , spfli-connid, sflight-fldate.
    ENDAT.
    AT LAST.
      ULINE.
      WRITE: cnt(spfli-carrid), 'Airlines'.
      ULINE.
    ENDAT.
ENDLOOP.
FIELD STRING is nothing but a string with one row of records.
Reward points if useful
regards
Anji

Re: field symbols and interna table

hi,
here is field symbol which is table type
FIELD-SYMBOLS: <gt_pos_data> TYPE table.
there is one internal table it_data.
how can move <gt_pos_data> to it_data.
please help me.
rgds

Hi
You can assign field wise:
like
<gt_pos_data>- field to to it_data-field.
Field Symbols
Field symbols are placeholders or symbolic names for other fields. They do not physically reserve space for a field, but point to its contents. A field symbol cam point to any data object. The data object to which a field symbol points is assigned to it after it has been declared in the program.
Whenever you address a field symbol in a program, you are addressing the field that is assigned to the field symbol. After successful assignment, there is no difference in ABAP whether you reference the field symbol or the field itself. You must assign a field to each field symbol before you can address the latter in programs.
Field symbols are similar to dereferenced pointers in C (that is, pointers to which the content operator * is applied). However, the only real equivalent of pointers in ABAP, that is, variables that contain a memory address (reference) and that can be used without the contents operator, are reference variables in ABAP Objects.
All operations programmed with field symbols are applied to the field assigned to it. For example, a MOVE statement between two field symbols moves the contents of the field assigned to the first field symbol to the field assigned to the second field symbol. The field symbols themselves point to the same fields after the MOVE statement as they did before.
You can create field symbols either without or with type specifications. If you do not specify a type, the field symbol inherits all of the technical attributes of the field assigned to it. If you do specify a type, the system checks the compatibility of the field symbol and the field you are assigning to it during the ASSIGN statement.
Field symbols provide greater flexibility when you address data objects:
If you want to process sections of fields, you can specify the offset and length of the field dynamically.
You can assign one field symbol to another, which allows you to address parts of fields.
Assignments to field symbols may extend beyond field boundaries. This allows you to address regular sequences of fields in memory efficiently.
You can also force a field symbol to take different technical attributes from those of the field assigned to it.
The flexibility of field symbols provides elegant solutions to certain problems. On the other hand, it does mean that errors can easily occur. Since fields are not assigned to field symbols until runtime, the effectiveness of syntax and security checks is very limited for operations involving field symbols. This can lead to runtime errors or incorrect data assignments.
While runtime errors indicate an obvious problem, incorrect data assignments are dangerous because they can be very difficult to detect. For this reason, you should only use field symbols if you cannot achieve the same result using other ABAP statements.
For example, you may want to process part of a string where the offset and length depend on the contents of the field. You could use field symbols in this case. However, since the MOVE statement also supports variable offset and length specifications, you should use it instead. The MOVE statement (with your own auxiliary variables if required) is much safer than using field symbols, since it cannot address memory beyond the boundary of a field. However, field symbols may improve performance in some cases.
check the below links u will get the answers for your questions
http://help.sap.com/saphelp_nw04/helpdata/en/fc/eb3860358411d1829f0000e829fbfe/content.htm
http://www.sts.tu-harburg.de/teaching/sap_r3/ABAP4/field_sy.htm
http://searchsap.techtarget.com/tip/1,289483,sid21_gci920484,00.html
Syntax Diagram
FIELD-SYMBOLS
Basic form
FIELD-SYMBOLS <fs>.
Extras:
1. ... TYPE type
2. ... TYPE REF TO cif
3. ... TYPE REF TO DATA
4. ... TYPE LINE OF type
5. ... LIKE s
6. ... LIKE LINE OF s
7. ... TYPE tabkind
8. ... STRUCTURE s DEFAULT wa
The syntax check performed in an ABAP Objects context is stricter than in other ABAP areas. See Cannot Use Untyped Field Symbols ad Cannot Use Field Symbols as Components of Classes.
Effect
This statement declares a symbolic field called <fs>. At runtime, you can assign a concrete field to the field symbol using ASSIGN. All operations performed with the field symbol then directly affect the field assigned to it.
You can only use one of the additions.
Example
Output aircraft type from the table SFLIGHT using a field symbol:
FIELD-SYMBOLS <PT> TYPE ANY.
DATA SFLIGHT_WA TYPE SFLIGHT.
ASSIGN SFLIGHT_WA-PLANETYPE TO <PT>.
WRITE <PT>.
Addition 1
... TYPE type
Addition 2
... TYPE REF TO cif
Addition 3
... TYPE REF TO DATA
Addition 4
... TYPE LINE OF type
Addition 5
... LIKE s
Addition 6
... LIKE LINE OF s
Addition 7
... TYPE tabkind
Effect
You can define the type of the field symbol using additions 2 to 7 (just as you can for FORM parameters (compare Defining the Type of Subroutine Parameters). When you use the ASSIGN statement, the system carries out the same type checks as for USING parameters of FORMs.
This addition is not allowed in an ABAP Objects context. See Cannot Use Obsolete Casting for FIELD SYMBOLS.
In some cases, the syntax rules that apply to Unicode programs are different than those for non-Unicode programs. See Defining Types Using STRUCTURE.
Effect
Assigns any (internal) field string or structure to the field symbol from the ABAP Dictionary (s). All fields of the structure can be addressed by name: <fs>-fieldname. The structured field symbol points initially to the work area wa specified after DEFAULT.
The work area wa must be at least as long as the structure s. If s contains fields of the type I or F, wa should have the structure s or at least begin in that way, since otherwise alignment problems may occur.
Example
Address components of the flight bookings table SBOOK using a field symbol:
DATA SBOOK_WA LIKE SBOOK.
FIELD-SYMBOLS <SB> STRUCTURE SBOOK
DEFAULT SBOOK_WA.
WRITE: <SB>-BOOKID, <SB>-FLDATE.
Related
ASSIGN, DATA
Additional help
Declaring Field Symbols
Reward points if useful
Regards
Anji

Add fields LGORT and WERKS in table KOMBE1

In case of inbound deliveries, I want to add fields LGORT and WERKS to structure KOMBE1.I want to create an (Header)access sequence that checks on this 2 fields in order to generate an output type.
So I will add this two fields in structure KOMBE1. Do you know if there is another structure In which I have to add this two fields and what is the user exit to use in order to populate this 2 fields.
PS: In case of outbound deliveries, in order to add fields in catalogue (Catalogue of fields to access conditions of output), we have to add the fields to structure KOMKBV2 and to structure KOMB.

Dear Omar
This is what the documentation says:
New Fields For Output Control
Basics of modification in output control
The following communication structures are relevant for output control:
KOMKBK1 (Output Determination Communication Area CAS Appl. K1)
KOMKBV1 (Output Determination Communication Area Header Appl. V1)
KOMKBV2 (Output Determination Communication Area Header Appl. V2)
KOMKBV3 (Output Determination Communication Area Header Appl. V3)
KOMKBV5 (Communication Structure for Output Control Groups Appl. V5)
KOMKBV7 (Output Determination Communication Area Shipment Appl. V7)
KOMPBV1 (Output Determination Communication Area Item Appl. V1)
KOMPBV2 (Output Determination Communication Area Item Appl. V2)
KOMPBV3 (Output Determination Communication Area Item Appl. V3)
KOMB     (Field Catalog for Condition Keys: Output Control)
New fields for output control are entered in the following INCLUDEs:
Sales activities: KOMKBZ1 (in KOMKBK1)
Sales document header: KOMKBZ3 (in KOMKBV1)
Delivery header: KOMKBZ4 (in KOMKBV2)
Groups header: KOMKBZF (in KOMKBV5)
Billing document header: KOMKBZ5 (in KOMKBV3)
Sales document item: KOMPBZ1 (in KOMPBV1)
Delivery item: KOMPBZ3 (in KOMPBV2)
Billing document item: KOMKBZ5 (in KOMPBV3)
Shipment: KOMKBZH (in KOMKBV7)
If you also want to use a new field for the setup of condition tables (key field) it must also be included in the structure KOMBZ (contained in KOMB).
The routines and user exits for assigning values to the new fields are found in the programs RVCOMFZZ, RVCOMFZ1, RVCOMFZ4, and LVCOMFZ1. It is also possible to copy partners here.
The following user exits exist in member RVCOMFZ1:
USEREXIT_KOMPBV2_FILL (item fields in delivery)
USEREXIT_KOMPBV2_PARTNER (item fields for partners in delivery)
USEREXIT_KOMPBV3_FILL (item fields in billing document)
USEREXIT_KOMPBV3_PARTNER (item fields for partners in billing document)
The following user exits exist in member RVCOMFZZ:
USEREXIT_KOMKBK1_FILL (header fields in sales activities)
USEREXIT_KOMKBK1_PARTNER (header fields for partners in sales activ.)
USEREXIT_KOMKBV1_FILL (header fields for sales documents)
USEREXIT_KOMKBV1_PARTNER (header fields for partners in sales documents)
USEREXIT_KOMKBV2_FILL (header fields in delivery)
USEREXIT_KOMKBV2_PARTNER (header fields for partners in delivery)
USEREXIT_KOMKBV3_FILL (header fields in billing document)
USEREXIT_KOMKBV3_PARTNER (header fields for partners in billing doc.)
The following user exit exists in member RVCOMFZ4:
USEREXIT_KOMKBV5_FILL (header field for groups)
The following user exits exist in member LVCOMFZ1:
USEREXIT_KOMPBV7_FILL (Shipment fields for header and stage)
USEREXIT_KOMPBV7_PARTNER (Shipment fields for partners)
In output determination, communication table KOMB contains all key fields that can be used for conditions for output determination.
When you create new fields for output determination, you can distinguish between two types of fields:
Fields that are used in condition tables
Fields that are only used to query conditions.
Both types of field have to be included in KOMKBV1. Fields which are only used to query conditions do not have to be included in KOMB and T681F or in the field catalog.
Note concerning name assignment
There are two possibilities for naming the field:
If the field is identical to the field in the communication table (e.g. VBAK), a value is assigned to it automatically by MOVE-CORRESPONDING. If SAP delivers the field in a subsequent system version, no generation errors will be caused.
If the field is not identical with the field in the communication table,you have to assign a value to it using the MOVE command. Begin the field name with the letters ZZ. This will avoid generation errors if the field is later delivered by SAP in a subsequent system version.
Example 1: Creating a new key field in output control
If, for example, you want to use the field ERNAM (name of sales employee) from the sales order (table VBAK) for output determination, proceed as follows:
1. Enter the field ZZERNAM in communication structure KOMKBV1 in INCLUDE KOMKBZ3 in the Data Dictionary.
By entering the field in KOMKBZ3, you automatically include it in communication table KOMKBV1.
2. Enter ZZERNAM in the communication table KOMB (in KOMBZ).
3. Assign values to the fields
Values are assigned to the fields in function module KOMKBV1_FILL. You have to enter the field and assign value to it manually in user exit USEREXIT_KOMKBV1_FILL. You will find the statements that you can use as a reference in the user exits.
Copying partner numbers is a special case and will be explained in Example 3.
4. Include ZZERNAM in the field catalog for the condition table for sales documents. The field catalogs must contain all the fields which you want to use to structure condition tables.
Example 2: Entering a condition field in the communication block
If you want to use condition field VBAK-AUDAT for output determination, proceed as described in Example 1. Remember that it is not necessary to include the new field in KOMBZ (KOMB) or to maintain table T681F or the field catalog.
Example 3: Entering a partner number in the communication block
Example 3 presupposes that there is a new partner function for buyer ZY in the sales document and that the number of this partner is to be copied.
When entering partner numbers in the communication block, proceed as described in the examples above. Partner function ZY is assigned to partner type AP in this example.
Remember to use a different routine to assign values to the new fields. If, for example, you want to copy the partner function ZY into the new field ZZEINKA, for example, the statement is:
USEREXIT_KOMKBV1_PARTNER
WHEN 'ZY'.COM_KBV1-ZZEINKA = COM_VBPA-PARNR.
The VBPA field used to assign a value to the new field depends on the partner function determined in the sales order. Each partner function is assigned to a partner type (e.g. partner function LF - partner type LI), which controls the assignment. Other source fields should be used for other partner types: COM_VBPA-KUNNR, COM_VBPA-LIFNR, COM_VBPA-PERNR and COM_VBPA-PARNR.
The following assignments exist:
KU => COM_VBPA-KUNNR
LI => COM_VBPA-LIFNR
PE => COM_VBPA-PERNR
AG => COM_VBPA-PARNR
<b>   Although i couldnt find any info related to Inbound deliveries.
   Am not really sure, but maybe you can give a try doing the following:
   1. Add fields to KOMKBE1.
   2. Add fields to KOMKBME.
   3. Try populating through user-exit:
USEREXIT_KOMKBME_FILL of include RVCOMFZZ.</b>
Kind Regards
Eswar

Maintain field mapping and conversion rule

hi
could you please tell me,
IN LSMW 5 th step, what is the role of maintain field mapping and conversion rule, please throw some light on it.
Thanks

it will set up the connection between your defined "source field" and the field which has been maintained by your import method .

FIELD RELATING TABLES

can anyone give me the fields relating EBAN, EKKO and EKPO

EBAN- it's the purchase requisition table
when u create a purchase requisition using ME51N it's saved to this table.
EKKO- Purchasing Doc Header
EKPO- Purchasing Doc Item
When u create a purchase order using ME21N, data go to these 2 tables.
as per relation is concerned if u generate a PO with respect to a PR then there is a relation between EBAN & EKPO
EKKO - EKPO mapped with EBELN
EKPO - EBAN mapped with BANFN & BFNPO
Reward if useful

LSMW field mapping

Hello,
I am doing Material master load using LSMW in 3loads.
First load is for basic data with matnr , mtart,mbrsh,maktx,meins,bismt,mtart.
wht should be the format of my input file, it should be like in the step " maintain field mapping and conversions" , because when in see the data in "display read data " and " display converted data ", its loading the records but its deleting some parts of it and after executing the last step its giving errors.
If LSMW is success, where can i see the output?
I would appreciate if some can help me , i am doing LSMW for the first time.
the problem is with field mapping and file format?
thanks.
Raghu

the file format is same as the field mapping and conversions, still its picking the values from the file in different order . I am saving the excel sheet in tab delimited form and mentioned it in the LSMW.if anyone done Material master load , if would appreciate if u can give the steps and file format..
points are rewarded..
thanks.

Billing experts: Combining order related and deliv. related

Hello Billing experts,
I am just wondering if it is possible at all to combine order related and delivery related to ONE billing document (one DMR and one delivery note with the same payer).
Or do we have to use Invoice List? I can't make it work.
Same payer, same Payment Terms and different pricing procedures(with RL00). What other fields that must have identical values, so the billing documents will be grouped in the invoice list?
Thanks alot in advance!
Best Regards,
Tuan Vo

Hi Tuan Vo
Since there are many other criteria, its not a viable Solution to combine, order related and delivery related to one billing document even though its possible in SAP.
The following prerequisites must be met for a Single Invoice from Delivers and/or orders:
1) the header data appearing in the billing document must agree
2) the split conditions specified do not apply
As you see, the Delivery related Invoice has always a pre-checking with the Goods Issue status where as Order related doesn't have to.
Hence Invoice lists is the option given by SAP.
However, with an intelligent Copy Control routines between the documents should do the trick.
The system combines documents with the same customer number, proposal billing type and sales organization, and attempts to include them all in the same billing document. If the preconditions are met, then a single invoice is created for the deliveries and/or orders.
Note that When creating several billing documents, user exits can be used to reset the header data, so that more can be combined than in the billing due list and later combine to single document.
There are other fields like Material Group, Billing Dates, Billing Document Type, Item categories which can force for an Invoice split.
Please let me know if it helps.
Best Regards
Ajay Kumar Veeranki

The new field blur and tilt shift filters have stopped working

The new field blur and and tilt shift filters worked a few times but are now greyed out in the menus. Any ideas why? Thanks.

Did you check the settings Chris mentioned? Your issue sounds like there might be a video card or driver issue, which can disable the GPU related features and give you a lesser version of the blur filters. See this link for some troubleshooting suggestions. See if issues with the video card have disabled - Edit>preferences>performance use graphics processor. Also check the advanced settings drawing modes. Be sure you have the current driver (system is updated and current on mac or go to the video manufacturer's website for pc) . That is often the cure.
You might want to copy your system information (photoshop help>system info) here for us to look at.
Pattie

How to get the table of value field? and can we expand the technical limits

Dear
I have created value field in COPA with KEA6. And now, I need the table which the value fields are saved. Yet, I have tried a lot to find it and get failure? Can any guy help me? Please tell me how to get the table of a value field.
And another question is that, can we extend the technical limits for the number of value field for ECC6.0?
We have a note for R.4.x Please see below:
OSS note 160892
You can display the length of a data record using Transaction KEA0 ('Maintain Operating Concern'). After you have navigated to the 'Characteristics Screen' or to the 'Value field Screen' choose menu path 'Extras -> Technical Limits'.
The maximum displayed here under 'Length in bytes on the DB' is the maximum length permitted by the Dictionary. The reserve required for the release upgrade must be subtracted from this value.
To increase the allowed number of the value fields, increase the value that is assigned to field ikcge-bas_max_cnt (FORM init_ikcge_ke USING fm_subrc, approx. line 165) in Include FKCGNF20. It specifies the number of the possible value fields. The corresponding part of the source code is attached to the note as a correction.
David Sun
Regards!

how to extend the limit of value numbers? please see the original question.

Field NAme and Table Name

Hi All,
I got some output values from the legacy system with me but need to know whats the actual field name and table name to which i need to transfer these values. How can i do it, since which theres is not field name or despcription given for the data.
Is there any way i can do it.
Points will be rewarded for all useful answers.
Regards
AB

if you know the transaction code you use to post the uploaded data in SAP, you just need to do BDC recording in using transation SM35. Record the whole process and create a program from the recording... and you wont even need to know the tables and field names-- almost everything will be done for you....
All you need to do is replace record data with upload data.
You can also try to look for a standard Function Module / BAPI which can do the processing for you and provide it with a table containing the upload data ...
Reward points if useful

How to populate fields "DocEntry" and "DocNum" in UDT? Those are not UDF.

I created a UDT with document type. When I populate the data, I don't know how to populate fields "DocEntry" and "DocNum". Those are not UDF. Here is my coding. Can somebody help me out?
Dim objUserTable As SAPbobsCOM.UserTable
                    objUserTable = objSBOAPI.oCompany.UserTables.Item("AIT_POSTRANS")
objUserTable.UserFields.Fields.Item("DocEntry").Value ="1000"
///////////// Error here "DocEntry" is not a UDF
                                       objUserTable.UserFields.Fields.Item("U_TrnsType").Value = "4"
                        objUserTable.UserFields.Fields.Item("U_CardCode").Value = objRecord.Fields.Item(0).Value
                        objUserTable.UserFields.Fields.Item("U_ShpBrnch").Value = objRecord.Fields.Item(1).Value.Replace("'", "")

Currently versions of the SDK (SBO2005A SP01, SBO2007A, SBO2005B, SBO2007B) does not support Data Support of UDO-tabeles using the DI-API... That means that you can only add data to such tables using the GUI,,,
This is currently a huge problem and the number one DI-API Development Request. The status with SAP is that this will become part of the SDK in SAP Business One 8.8 (the next major release), but 8.8 does not yet have a shipment date (My guess is that it will be 2009 before we even see it in rampup)...
I know some people have experimented with writing direct SQL to such tables and know it can be done, but be aware that SAP does NOT support it!... Personally I've never done it for that reason althoug it would have been nice to do if some situations...
Sorry I could not give anything better...

LSMW field relations and mappings

Similar Messages

Maybe you are looking for