Create IDOC (FIDCCP02) via LSMW

Hi,
i would like to create IDOCs (basic type FIDCCP02) via LSMW. How should source file look? Shall it be only one structure or more (header, items)? I need to create many IDOCs from one source file and IDOCs (FI documents) will have variable number of items. How can i do it?
Thanks, zd.

i would also want to know how can something be done via BAPI method in LSMW. one explaining the Idoc method can also pls. explain this.
Thanks in advance.

Similar Messages

Create IDoc FIDCCP02 / XMWST

Hi all,
I want to use standard IDoc processing (in stead of using program RFBIBL00 due to user requirement) via SAP XI. When using RFBIBL00 one can enter the markfield XMWST (calculate tax automatically) in header BBKPF and field NEWKO (Account or Matchcode for the Next Line Item). However, I can't find these fields in Basic Idoc type FIDCCP01 / FIDCCP02?
Does anyone know if there are any alternative fields in some of the IDoc segments?
Kind regards,
Micky.

Hi,
I could not find any segment available for XMWST (calculate tax automatically).
Do you have plan to use BAPI instead?
If you do, please check BAPI BAPI_INCOMINGINVOICE_CREATE and check the header data parameter.
Regards,
Ferry Lianto

Creating a sales order via lsmw.

Hi,
I am creating sales orders via lsmw. Each of these sales orders may contain any number of line items, i.e. sales order 1 might have 3 line items and the next sales order may have 10.
How do I cater for this in lsmw. Is there a way of saying: when last line item, then start next sales order record?
Any help appreciated.
Regards,
Warren.

HI, I create LSMW for sales order. It is working fine for 9 line items. IF more than 9 line item, other item is not updating. Pls provide me a solution. Thanks in Advance.
my email is [email protected]

Material variants via LSMW

Hello all,
Is it possible to create material variants via LSMW. Via the direct input (RMDATIND), I can't fill the necessary fields in the MRP 3 view and configure the variant. I tried to search for an other transaction to use and maybe create a batch input but for the moment no luck.
Thanks in advance
Best regards
Roel

Hi
Yes, u should use only one file with data of client-level and plant-level, so it means the data of client-livell will be the same for the same material code.
In this way u can create only one transaction for every materila/plant (i.e the BAPI will be called for every plant), if u use two files the system'll try to upload the data of two plants by the same transaction.
What u need to understand if u need to move the data client-level again as soon as you move the data of second plant.
Max

Master data upload via LSMW using IDoc method

Dear all,
I know this has been a topic of many discussions but I would like to ask you is to share your thoughts and possibly experience with the following scenario:
Interface between non-SAP system and SAP system has to be built whereby master data gets created in the non-SAP system and has to be uploaded into SAP. This is a process that needs to be performed on a constant basis and hence my question: is there a way that the MD upload takes place in the background via LSMW with IDoc? Or any other way, for instance, with a flat file, etc.?
Thank you very much for your input!
Regards,
Miro

Miro - It depends upon many factors
1. Number of source systems
2. Volumn of recorsds ( Data to be loaded)
3. Transformation needed or not needed from S to D ( source to destination), We may consider it as
business rules/mapping
Based on above you may segrigate the objects related to data, eventually you can shoose approach of loading in SAP,
As if straigt forward load for some 20k-30K records ( Just a file load on regular basis), one to one mapping then go for LSMW, if some complex transformation logic needed then go SAP data services implementation. best part here is if you multiple sources that can be handeled here.
Accordingly you can proceed ...
Hope it helps.
Best !
Deep

Creating Routings via LSMW

Hi all,
Can anyone give me some pointers when creating Routings via LSMW. I see there are two standard uploads in RCPTRA01 and RCPTRA02. However, the mapping structures seem to be different between the two.
I need to add PRT's material assignments and long texts to the routing.
Any help greatly appreciated.

Hi,
Use standard batch/Direct input : RCPTRA02
Source Fields
        MATERIAL_ROUTING          Material
            PLNAL                          C(002)    Group Counter
            MATNR                          C(018)    Article Number
            WERKS                          C(004)    Site
            OPERATION_ROUTING         Operations
                PLNAL                          C(002)    Group Counter
                VORNR                          C(004)    Operation/Activity Number
                STEUS                          C(004)    Control Key
                ARBPL                          C(008)    Work center
                WERKS                          C(004)    Site
                LTXA1                          C(040)    Operation short text
                MEINH                          C(003)    Quantity unit for operation (batch input)
                BMSCH                          C(017)    Base quantity (Batch input)
                LAR02                          C(006)    Activity Type
                VGE02                          C(003)    Unit for the standard value (batch input)
                VGW02                          C(011)    Standard Value (Batch Input)
                LAR03                          C(006)    Activity Type
                VGE03                          C(003)    Unit for the standard value (batch input)
                VGW03                          C(011)    Standard Value (Batch Input)
            COMPONENT_ROUTING         Components
                PLNAL                          C(002)    Group Counter
                VORNR                          C(004)    Operation/Activity Number
                POSNR                          C(004)    BOM Item Number
                MATNR                          C(018)    Article Number
                WERKS                          C(004)    Site
Field Mapping and Rule
       RC271_DS                       Work center structure for direct input (for datasets)
           Fields
               TCODE                        Transaction Code
                                   Rule :   Constant
                                   Code:    RC271_DS-TCODE = 'CA01'.
               STTAG                        Character Field Length = 10
                                   Rule :   Constant
                                   Code:    RC271_DS-STTAG = '18.03.2014'.
               AENNR                        Change Number
               REVLV                        Revision Level
               WERKS                        Site
                                   Rule :   Transfer (MOVE)
                                   Code:    RC271_DS-WERKS = MATERIAL_ROUTING-WERKS.
               PROFIDNETZ                   Profile
               PLNNR                        Key for Task List Group
               PLNAL                        Group Counter
                                   Rule :   Transfer (MOVE)
                                   Code:    RC271_DS-PLNAL = MATERIAL_ROUTING-PLNAL.
               STATU                        Status
                                   Rule :   Constant
                                   Code:    RC271_DS-STATU = '4'.
               VAGRP                        Responsible Planner Group/Department
                                   Rule :   Constant
                                   Code:    RC271_DS-VAGRP = 'KD1'.
               VBELN                        Sales Document
               POSNR                        Character field of length 6
               PSPNR                        Work Breakdown Structure Element (WBS Element)
MAPL_DI_DS                     Assign routing to article for direct input (for datasets)
    Fields
        ACTTYP                       Processing type for objects to be imported
                            Code:    MAPL_DI_DS-ACTTYP = 'H'.
        MATNR                        Article Number
                            Rule :   Transfer (MOVE)
                            Code:    MAPL_DI_DS-MATNR = MATERIAL_ROUTING-MATNR.
        WERKS                        Site
                            Rule :   Transfer (MOVE)
                            Code:    MAPL_DI_DS-WERKS = MATERIAL_ROUTING-WERKS.
        PLNAL                        Group Counter
                            Rule :   Transfer (MOVE)
                            Code:    MAPL_DI_DS-PLNAL = MATERIAL_ROUTING-PLNAL.
        LIFNR                        Vendor Account Number
        KUNR                         Account Number of Customer
        SUCHFELD                     Search Field for Customer-Specific Task List Selection
        VBELN                        Sales Document
        POSNR                        Sales Document Line Item (Batch Input Field)
        PSPNR                        Work Breakdown Structure Element (WBS Element)
PLKO_DI_DS                     Header structure for direct input (for datasets)
    Fields
        ACTTYP                       Processing type for objects to be imported
                            Code:    PLKO_DI_DS-ACTTYP = 'H'.
        PLNAL                        Group Counter
                            Rule :   Transfer (MOVE)
                            Code:    PLKO_DI_DS-PLNAL = MATERIAL_ROUTING-PLNAL.
        VERWE                        Use by user or system
                            Rule :   Constant
                            Code:    PLKO_DI_DS-VERWE = '1'.
        WERKS                        Site
                            Rule :   Transfer (MOVE)
                            Code:    PLKO_DI_DS-WERKS = MATERIAL_ROUTING-WERKS.
        STATU                        Status
                            Rule :   Constant
                            Code:    PLKO_DI_DS-STATU = '4'.
        PLNME                        Unit of measure for the task list (batch input)
                            Rule :   Constant
                            Code:    PLKO_DI_DS-PLNME = 'KG'.
        LOSVN                        From lot size (BTCI)
                            Rule :   Constant
                            Code:    PLKO_DI_DS-LOSVN = '0'.
        LOSBS                        To lot size (BTCI)
                            Rule :   Constant
                            Code:    PLKO_DI_DS-LOSBS = '999999999'.
        VAGRP                        Responsible planner group/department
                            Rule :   Constant
                            Code:    PLKO_DI_DS-VAGRP = 'KD1'.
        KTEXT                        Task list description
                            Rule :   Constant
                            Code:    PLKO_DI_DS-KTEXT = 'Article Routing'.
        TXTSP                        Single-Character Indicator
PLPO_DI_DS                     Routing/item structure for direct input (for datasets)
    Fields
        ACTTYP                       Processing type for objects to be imported
                            Code:    PLPO_DI_DS-ACTTYP = 'H'.
        PLNAL                        Group Counter
                            Rule :   Transfer (MOVE)
                            Code:    PLPO_DI_DS-PLNAL = OPERATION_ROUTING-PLNAL.
        PLNFL                        Sequence
                            Rule :   Constant
                            Code:    PLPO_DI_DS-PLNFL = '000000'.
        VORKN                        Node number (batch input)
        VORNR                        Operation/Activity Number
                            Rule :   Transfer (MOVE)
                            Code:    PLPO_DI_DS-VORNR = OPERATION_ROUTING-VORNR.
        UVOKN                        Node number (batch input)
        UVORN                        Suboperation
        STEUS                        Control key
                            Rule :   Transfer (MOVE)
                            Code:    PLPO_DI_DS-STEUS = OPERATION_ROUTING-STEUS.
        ARBID                        Object ID (batch input)
        OBJTY                        Object types of the CIM resource
        ARBPL                        Work center
                            Rule :   Transfer (MOVE)
                            Code:    PLPO_DI_DS-ARBPL = OPERATION_ROUTING-ARBPL.
        WERKS                        Site
                            Rule :   Transfer (MOVE)
                            Code:    PLPO_DI_DS-WERKS = OPERATION_ROUTING-WERKS.
        KTSCH                        Standard text key
        LTXA1                        Operation short text
                            Rule :   Transfer (MOVE)
                            Code:    PLPO_DI_DS-LTXA1 = OPERATION_ROUTING-LTXA1.
MEINH                        Quantity unit for operation (batch input)
                    Rule :   Transfer (MOVE)
                    Code:    PLPO_DI_DS-MEINH = OPERATION_ROUTING-MEINH.
UMREN                        Denominator for conversion from unit to base unit (BTCI)
                    Rule :   Constant
                    Code:    PLPO_DI_DS-UMREN = '1'.
UMREZ                        Numerator for converting from unit to base unit (BTCI)
                    Rule :   Constant
                    Code:    PLPO_DI_DS-UMREZ = '1'.
BMSCH                        Base quantity (Batch input)
                    Rule :   Transfer (MOVE)
                    Code:    PLPO_DI_DS-BMSCH = OPERATION_ROUTING-BMSCH.
ZMERH                        Break time (batch input)
ZEIER                        Unit for break time (batch input)
LAR01                        Activity Type
VGE01                        Unit for the standard value (batch input)
VGW01                        Standard Value (Batch Input)
LAR02                        Activity Type
VGE02                        Unit for the standard value (batch input)
                    Rule :   Transfer (MOVE)
                    Code:    PLPO_DI_DS-VGE02 = OPERATION_ROUTING-VGE02.
VGW02                        Standard Value (Batch Input)
                    Rule :   Transfer (MOVE)
                    Code:    PLPO_DI_DS-VGW02 = OPERATION_ROUTING-VGW02.
LAR03                        Activity Type
VGE03                        Unit for the standard value (batch input)
                    Rule :   Transfer (MOVE)
                    Code:    PLPO_DI_DS-VGE03 = OPERATION_ROUTING-VGE03.
VGW03                        Standard Value (Batch Input)
                    Rule :   Transfer (MOVE)
                    Code:    PLPO_DI_DS-VGW03 = OPERATION_ROUTING-VGW03.
PLMZ_DI_DS                     Article component allocation for direct input(for datasets)
    Fields
        ACTTYP                       Processing type for objects to be imported
                            Rule :   Constant
                            Code:    PLMZ_DI_DS-ACTTYP = 'H'.
        PLNAL                        Group Counter
                            Rule :   Transfer (MOVE)
                            Code:    PLMZ_DI_DS-PLNAL = COMPONENT_ROUTING-PLNAL.
        PLNFL                        Sequence
                            Rule :   Constant
                            Code:    PLMZ_DI_DS-PLNFL = '000000'.
        PLNKN                        Node number (batch input)
        VORNR                        Operation/Activity Number
                            Rule :   Transfer (MOVE)
                            Code:    PLMZ_DI_DS-VORNR = COMPONENT_ROUTING-VORNR.
        STLTY                        BOM category
                            Rule :   Constant
                            Code:    PLMZ_DI_DS-STLTY = 'M'.
        STLNR                        Bill of material
                            Rule :   Constant
                            Code:    PLMZ_DI_DS-STLNR = '00000005'.
        STLAL                        Alternative BOM
                            Rule :   Constant
                            Code:    PLMZ_DI_DS-STLAL = '01'.
        STLKN                        Node number (batch input)
        POSNR                        BOM Item Number
                            Rule :   Transfer (MOVE)
                            Code:    PLMZ_DI_DS-POSNR = COMPONENT_ROUTING-POSNR.
WERKS                        Site
                    Rule :   Transfer (MOVE)
                    Code:    PLMZ_DI_DS-WERKS = COMPONENT_ROUTING-WERKS.
BOMAT                        Article Number
                    Rule :   Transfer (MOVE)
                    Code:    PLMZ_DI_DS-BOMAT = COMPONENT_ROUTING-MATNR.
STLST                        Order level
STLWG                        Order path
STLTY_W                      BOM category
                    Rule :   Constant
                    Code:    PLMZ_DI_DS-STLTY_W = 'M'.
STLNR_W                      Bill of material
                    Rule :   Constant
                    Code:    PLMZ_DI_DS-STLNR_W = '00000005'.
STLAL_W                      Alternative BOM
                    Rule :   Constant
                    Code:    PLMZ_DI_DS-STLAL_W = '01'.
Map the extra fields according to your requirement. Hope you'll find the code helpful.

Create KANBAN control cycle (PK01) via LSMW

Hi,
Anybody perofrmed control cycle creation via LSMW using BAPI or IDOC method? I need to know the Business object (BAPI method) or Message type for IDOC menthod in LSMW for PK01 tcode.
Thanks.

you should enable the F4 search help in your LSMW.
I have it active and found Idoc PKHD5

Creating HR objects via IDoc HRMD_A05

Hi to all
I want to create HR objects via IDoc HRMD_A05 and want the objects numbered using INTERNAL number range.
The IDoc documentation says to pass an exclamation mark '!' to OBJID to make the system generate new number. However, the field is numeric and can not contain '!'.
Has anybody tried this way before and achieved to create objects numbered internally?
Thanks

Hi
I have told the issue to the SAP OSS and their feedback was:
"As explained in note 741165:
'There is no provision to carry out an internal number assignment using
ALE in the target system. Therefore, the numbers must be assigned when
the IDOCs are created in the source system.'
The documentation in the Interface Repository is wrong.
Regards
*--Serdar

Missing fields in IDoc FIDCCP02

Hello Experts ,
I am using FIDCCP02 IDoc to create a customer invoice.My item level data contains a field XMWST (Calculate Tax) which i can not find anywhere in the IDoc.Even BSEG-ANFBN ,BSEG-ANFBU,BSEG-ANFBJ,BSEZ-EGMLD,BSEG-HZUON fields are not present in the IDoc.I am mapping the above fields using LSMW.Please let me know how to map the above also it would be helpful if these fields are named differently in the above IDoc.
Thanks and regards,
Vijay Simha CR
Moderator message : Duplicate post locked. Continue with the earlier post [Missing fields in IDoc FIDCCP02|Missing fields in IDoc FIDCCP02].
Edited by: Vinod Kumar on Aug 31, 2011 5:45 PM

Hello Shafiq,
Thanks for your comment. I think it's a good idea to deactivate option to send IDocs immediately and create an own job to trigger it regularly. It would be great if according user exits would be triggered also only when the IDoc job starts. Otherwise I would have to create a copy of RSNASTED and enhance it to fill according values. Depending on the outcome I'll reward your anwser. Nevertheless thank you very much until then.
Eddy

Need to create Idoc using with BAPI in BP

Hi Experts,
Business Partners are created/changed in SAP either directly by using transaction BP or indirectly created from DTI or using the BAPIBUSISM007_CREATEFROMDATA BAPI for new customers and BAPIBUSISM007_CHANGE to change customers. When a business partner is created or changed via transaction BP an IDOC is generated when the create or change is saved. This IDOC is then sent to the appropriate DTI (Third party) clients to ensure the customers remain in sync.
Now issue is that creates and changes made using a BAPI do not generate an IDOC. Therefore, new customers and customer changes made by DTI clients do update ECC but are not being passed on to Ad Sales since an IDOC is not created. The same is true when a customer is created/changed by Ad Sales. The change is made in ECC via the BAPI but since no IDOC is generated the create/change doesn’t get moved to the DTI clients.
what the IDOC triggering mechanism is for generating IDOCS from the BAPIBUSISM007_CREATEFROMDATA BAPI and the BAPIBUSISM007_CHANGE BAPI. This mechanism should be some type of ALE Message that can be used in the partner profile setup to automatically generate the IDOC.
Any inputs about my issue.
Thanks,
Anji

Hi Experts,
Any updates or suggestions on this issue.
Thanks,
Anji

Doubt in creating idocs

Hi
I had created IDOCS by following this procedure
Step 1 Analyse Hierarchy Levels:
Analyse the data relationships being processed in the interface. Define the appropriate hierarchical Parent-to-Child relationships.
Navigate to transaction code WEDI
Transaction WEDI displays the IDOC main menu. This allows navigation around the various development and control areas to create a customised IDOC.
Step 2 Create a new segment:
via wedi : Development - IDOC Segments or Transaction code WE31.
Enter segment name and click on Create.
The name of the segment type must start with Z1 , and have a maximum of eight characters.
Enter description and enter the relevant field names and data elements.
The segment should represent a structure in the program so for each field in the segment a field name and a data element must be defined.
Save the segment and enter Person Responsible and Processing Person .
Go to Edit and Set Release.
Repeat this procedure for each new Segment in the IDOC.
Step 3 Create a new IDOC Type
via wedi Development - IDOC Types or Transaction WE30.
Enter segment name (starting with Z), click on Basic Type and then Create.
Create as new, enter Person Responsible and Processing Person and enter description.
On Create Basic Type screen decide where segments should be inserted and go to Edit/Create Segment.
Complete relevant fields in the Maintain Attributes screen:
From the relevant segments created in Step 2 enter the Segment type and if mandatory segment.
The Minimum and Maximum number of segments to be allowed in the sequence. (One minimum and one maximum if segment is mandatory).
The Parent Segment and Hierarchy Level will be automatically created depending on where in the IDOC tree you decided to create that particular segment.
Repeat this process for each segment needed in the IDOC type, deciding whether to add the next segments at the same level or as a Child.
When IDOC created return to initial screen. Go to Edit and Set Release.
Go to Transaction WE60 to view the IDoc Type you have created.
Step 4 Create new Message Type
via wedi Development - Message Types or Transaction WE81.
Display/Change and click on New Entries
Create a new Message Type and Save.
Step 5 Link Message Type to IDOC Type
via wedi Development - IDOC Type/Message or Transaction WE82.
Display/Change and then click on New Entries.
Enter Message Type, Basic Type (IDOC Type) and Release (46C) and Save.
Now my problem from this step
Step 6 Create an entry in EDP13 via transactions WE20 and BD64.
The partner profile for the Idoc must be set up and generated in the transaction BD64 and transaction WE20.
WE20 Add Message Type to appropriate Partner Type, Enter Message Type, Receiver Port and Idoc Type and Save.
BD64 Create a Model View, Enter Sender and Receiver Ports, Attach Message Type. Go to Environment on Menu and click on Generate Partner Profiles and generate (not save) profile.
From where i have to add message type to partner type
Can any one explain me clearly step by step after this step
Helpfull points will be surely rewarded
Regards
Pavan

Hi Pavan,
You have the Partner number? which is nothing but your Logical system name or vendor or customer. I think in your case, it is Logical system.
Select or create an logical system. If already exist, select the option LS in the left hand side and display it. IN WE20. Now, give you Message type and save it.
But, If we say in your case as ALE, Goto Tcode SALE, Nagivate and create logical system for sender and reciver.
2. Then assign these Logical system to the clients.
3. GOto Tcode SM59 and create RFC destination.
4.Tcode- BD64 , Display it and select create model view options. and save it.
5. Now, go for Assign message type and assingn the message type alon with your logical system name for recevier and sender.
6. Goto Status bar ENVIRONMENT and select generate partner profile. Automatically, a partner profile will be generated.
7.Now GOTO EDIT , Model view -
distribute.
Thanks
Manju.

Idoc FIDCCP02 posting skipping document number

I am using Idoc FIDCCP02 to post FI document. I have to enter value in field E1FIKPF-AWORG, otherwise it does not allow tax code to be used in certain conditions. Filling up filed E1FIKPF-AWORG is working fine and document is being posted. But the issue is that system is skipping one document number for each posting. If field E1FIKPF-AWORG is left blank, than this does not happen.
Any help please!

HI Dehra,
YOu can check if any customizing is done within the IDOC processing function module.
Or you can to analyse if populating the E1FIKPF-AWORG value creates any extra documents, which are consuming the number range.
Suggestion: You may get better responses in either FI Forums or ABAP forum.
Best Regards,
Ravikanth Talagana

Maintain Text in Infotype 0041 via LSMW

Hi,
Has anyone had success loading text into Infotype 0041 via lsmw?
I am trying to create an lsmw to maintain text in infotpye 0041. I follow the route PA30, then when in IT0041 I go to edit and maintain text.
The problem is that I get a syntax error because the field I am trying to update is RSTXP-TDLINE which is a length 0 and format type string. LSMW won't accept string fields so in the generated program for the lsmw the line reads: "tdline_01(000000) type c,". This obviously doesn't pass the syntax check.
Any help greatly appreciated.
Regards,
Warren.

Hi
I just tried to create a LSMW in my DEV environment. I didnt get any error when recording. I entered the text in IT41 without any issue. What I am getting in the source code is:
RSTXP-TDLINE(01) Abcde TDLINE_01 ABAP Source Line
Am I missing what you are seeing?
Cheers
Pramod

Extended Idoc FIDCCP02 - getting status code 02

Hello Friends,
I am extending Idoc FIDCCP02 with an custom segment. I have followed this steps
Created Segment - Created Extended Idoc with Custom Segment created - Released both Segment and Idoc - Attached Idoc to FIDDC2 message type - Added message type to model view - maitained partner Profiles with extended idoc - created port type 'G' - Added necessary code in user exit (I am able to view data in my custom segment)
The Problem is - If I do not maintain Extended Idoc in partner profiles - I get Idoc XML created in external system with status code 03
But once I add extended idoc to the partner profiles - I get Status Code 02 with error saying Error in passing data to HTTP Port 500 internal Server error
Kindly can some body help me if I am missing some steps.
Thanks for help.

Dear Vasu,
I am creating Z message type, when I am creating that idoc (I have used XML Port) its initially comes in status 30 (IDoc ready for dispatch (ALE service)).
Now when I process this idoc with tcode WE19 then it give status 02 (Error passing data to port). Please suggest where i am doing mistake.
Your help will be appreciated.
Regards, Vicky M. Khambhati

How to create Idoc Cond_a

Hi
I have to generate outbound Idoc...for COND_A.
1) I created new pricing via VK11.
2) I executed report RSEOUT00.
3) Partner Profile for Cond_a i tried with both "Create Immidiately: and "Collects"
But i have found idoc is not geting genrated.
I want to use RSEOUT00 for sheduling purpose.Any thg i m missing above??
I can create the same idoc via VK12-Send Condition record also but it doesn't fullfill my requirement
Please help me out
Regards
Subham

Hi,
First you need to distrubute the idoc. if you dont want to use VK12 for sending.
You can write a custom program using FM MASTERIDOC_CREATE_COND_A to distrubute / create COND_A
Then you should use RSEOUT00 to send the idocs once its created.If you are using COLLECT IDOCS option.
Hope it helps.
Shanmugavel Chandrasekaran

Create IDOC (FIDCCP02) via LSMW

Similar Messages

Maybe you are looking for