IDOC message type LOIPLO not triggering

Hi Friends
Our client want to send firmed planned orders to External system through outbound IDOC LOIPLO
So we are using MF50 to firm the planned orders.
The idoc message type LOIPLO is not triggering.
How to trigger IDOC message type LOIPLO . What are the settings we have to do.
Regards,
Srihari.M

dear friend,
Message Type : LOIPLO
Basic Type : LOIPLO01
You need not create any custom IDOC type as we are having a standard IDOC type available within SAP, but you need to write a custom function module to read the data from the IDOC segments and then call the below BAPI to post the Planned Order.
Check the input parameters of BAPI and gothrough the documentation of the Basic Type in WE60 transactions, whether all the necessary input parameters of the BAPI are covered in the standard IDOC type, if not then we need to customize the standard basic type to meet the requirements.
Bapi which needs to be used is BAPI_PLANNEDORDER_CREATE
good luck!

Similar Messages

IDOC message type WMMBXY not including Serial numbers in GR material documents when created with reference to an Inbound delivery

Hello,
We currently have an inbound ALE process (message type WMMBXY and basic type WMMBID02) to post GR's against inbound delivery. If the inbound delivery item is maintained with serial numbers, we want those serial numbers to be pulled into the goods movement material document (and stored in SER03).
Currently segment E1MBXYJ is maintained with the inbound delivery number in field VLIEF_AVIS and Inbound delivery item number in field
VBELP_AVIS. In segment E1MBXYI, no purchase order is assigned and the fields EBELN and EBELP are blank. The movement indicator (KZBEW) has the value 'B'.
Even after making the above settings, the serial number(s) maintained on the Inbound delivery item do not get saved to the material document.I did look at OSS note 833603 (Solution for 2 - GR for Inbound delivery) and we have followed the same settings. This works when there is no serial number in the Inbound delivery. However if we have serial numbers, the IDOC posts successfully, however the material documents in MB03 do not have any serial numbers copied over from the Inbound delivery where the serial numbers are definitely assigned.
Any help you can provide is greatly appreciated!
Thanks,
Ashvin
P.S
If we manually create the GR via MIGO, the serial numbers are automatically applied to the GR material document. This is what we want to accomplish via the above IDoc process.

Hi
Try with enhancement MWMIDO08. See note 833603 - EDI: Goods receipt for stock transport order for further information.
I hope this helps you
Regards
Eduardo

URGENT! Idoc Message Type FIDCC2 Not Posting CO Documents

Hi Everyone,
Our company is just about to begin using message type FIDCC2 to post entries through FB60/FB65 and FB50. When you manually enter an entry through any of these transactions, an FI, CCA and PCA document are all created simultaneously. However, when posting an identical entry through message type FIDCC2, only an FI document is created. Why are the other documents not being created and is there something that I am missing from configuration or some sort of trigger that is supposed to create the other entries? Please assist as this is extremely urgent.
Thanks to all that can assist,
Pete

Hi Peter,
Is your company uses any of the profitability segment fields as well? If so how are you updating this information on to the FIDCC2 idoc and how are you generating any COPA document simultaneously. I am in the same situation and my FIDCC2 idoc updates the FI, CO, PCA components but not the COPA. I am not sure where to populae the Profitability segments on the FIDCC2 type. Please share if you have same issues in your company.
Regards
Elphick

Idoc Message Type FIDCC2 Not Posting CO Documents

Hi Everyone,
Our company is just about to begin using message type FIDCC2 to post entries through FB60/FB65 and FB50. When you manually enter an entry through any of these transactions, an FI, CCA and PCA document are all created simultaneously. However, when posting an identical entry through message type FIDCC2, only an FI document is created. Why are the other documents not being created and is there something that I am missing from configuration or some sort of trigger that is supposed to create the other entries? Please assist as this is extremely urgent.
Thanks to all that can assist,
Pete

Hi Peter,
Is your company uses any of the profitability segment fields as well? If so how are you updating this information on to the FIDCC2 idoc and how are you generating any COPA document simultaneously. I am in the same situation and my FIDCC2 idoc updates the FI, CO, PCA components but not the COPA. I am not sure where to populae the Profitability segments on the FIDCC2 type. Please share if you have same issues in your company.
Regards
Elphick

Message type is not triggered in SAP when PO copied from eSHOP

Hi,
We are creating PO in eShop and sending to SAP.
POs are correctly getting copied from eShop to SAP.No issues.
We have set condition record for Message type to trigger in SAP for those POs as EDI Medium.
No message is getting triggering in SAP.
Whether it is standard one ? or any further enhancement required ? If so please suggest the BAPI.
Thanks

Hi Dhina
What is the application eSHOP?.
for example
In SAP SRM - Technical scenario - Extended Classic.
Purchase orders were created in SRM -EBP and replica of Purchase Orders were replicated to ECC system. In the above scenario messages are created in SRM not ECC.
The PO messages are out puted to vendor from SRM itself.
So please clarify what is meant by eShop. so others can help you further ..
Muthu

Output Type is not triggering

Hi,
We have created routine in output determination(VOFM) to trigger the output type (for IDoc) when ever Sales Order is created and we have configured correctly. Access Sequence containes KOMKBV1, KOMPBV1, etc.
When I checked in development system, I am getting values in KOMKBV1, KOMPBV1, etc and it is serving my purpose,
But when i tested same in quality system, KOMPBV1 structure is not getting values and this is not serving my purpose ( i.e output type is not triggering) .
Could any one please suggest me why it is happening.
Regards,
Aditya.

There is no problem with Access sequence
Below are the fields for the accesss sequence.
Sales document type KOMKBV1     AUART
Sales organization      KOMKBV1     VKORG
Distribution channel     KOMKBV1     VTWEG
Division                        KOMKBV1     SPART
Customer group 5        KOMKBV1     KVGR5
Plant                             KOMPBV1     WERKS
The same is working fine in Developemnt but not in quality.
I went to debugging mode while creating a sales order in both systems for checking where exactly KOMPBV1 is getting cleared.
I could find in
SAPMV45A
MV45AF0B_BELEG_BEARBEITEN_ENDE
FORM BELEG_BEARBEITEN_ENDE
Call function messaging
When the program is going in this..... the value for KOMPBV1 is getting cleared in Quality but the same this is working fine in Development...
Hope this coulld help you in understanding the problem better.
Edited by: Aditya K Ghanaria on Nov 30, 2010 4:13 PM

IDOC message type for "Site" in SAP Retail module?

Hi All,
We have the need to transfer master data (through master data change pointers) of Retail Sites within the SAP Retail module (transaction: WB01, WB02). Does anyone know if there's an IDOC message/type already associated with this? Thanks in advance for your help!
Cheers,
Matt

Hi,
please read SAP notes 892103 and 551035.
The correct IDOC type should be FIDCC1 / FIDCC2.
Best regards,
Andreas

Enhanced Fields in IDoc Message Type CRMXIF_ORDER_SAVE_M

Dear Experts,
I have enhanced the Business Transaction with EEWB and is used in Complaint Handling scneario. Now, I need to send the IDoc for the complaints. So, I have used the Message Type CRMXIF_ORDER_SAVE_M for this. But this message type does not have the Custom Fields which were enhanced. When I searched on the internet, I found the solutions to Re-generate the IDoc after adding fields in CRMXIF_CUSTOMER_H Segment. But when I try to do that it is asking for Access Key. I think there must be another way.
Please guide me.
Regards,
Sreenivas Raju.

Hey Sreenivas,
Standard provided Idoc will not have segments for Z fields that you add using AET/EEWB. How did you try to regenerate Idoc? You need to use transaction BDFG to generate a custom Idoc.
Follow the steps below.
1. Create a Z function group.
2. Run BDFG. Enter 'CRMXIF_ORDER_SAVE' in parameter for function Module and press enter. It will list the available message types including 'CRMXIF_ORDER_SAVE_M'
3. Press Create button in application toolbar. A popup will come. Give a name for new message type. Another popup will come, give names for inbound/outbound functions using the Z FG you created, suitable development class and press enter.
4. Now view your message type. Go to the idoc type and release it.
5. Finally selecting your new Z message type, go to menu Edit->Idoc Type and Segment Type->Release. Release your objects. There may be a few popups, respond accordingly.
6. Maintain partner profile settings. Process code will be APLI or APLM as per your need.
Voila!! You have your new message type having segments for Z fields.
Let me know the outcome.

Idoc/message type related to su01 tcode fields?

hi experts,
when i create a user in su01,an idoc should get triggered.
are there any standard idoc / message type having fields related to this.
thanks,
charu
Edited by: charudevrani on Jan 11, 2012 7:38 AM

Hi Charu,
You can use one of following IDoc types, depending on the action you want to perform on the user master record:
USERCHANGE     Change user
USERCLONE     Create User with Template in Another System
USERCREATE     BAPI to Create a User
Regards,
Marcin

Custom output type is not triggering automatically

Hi Experts,
We have created a custom output type for Delivery idoc processing.
it is working fine for all ship to patrys.
but from last 2 months onwards we are facing problem for one ship to party.
output type is not triggering automatically but for rest of ship to party's it is triggering automatically.
we have maintained conditions and also selected trigger immediately.
earlier it was working fine, but from last 2 months onwards we are facing this problem.
Thanks
Sai

Hi,
Goto the Delivery document and in the Output screen check the Determine analysis for output.
There it will clearly show what is missing .
Please check that and revert back if you need more clarification.
regards,
santosh

CRM: IDOC Message Type: CRMXIF_PARTNER_REL_SAVE_M

Hi,
I'm currently working on a CRM data migration project. I'm using the IDOC Message Type: CRMXIF_PARTNER_REL_SAVE_M to map data into contact relationship structures.
The problem I am having is the above interface works with SAP standard BUR001 type contact relationships. But a copy was taken of BUR001(is contact person for) => ZUR001 (former contact person of). This allows you to add a date range: DATE_TO - DATE_FROM. Using the above interface I am able to map these dates to the ZUR001 type relationships.
All the other data I try and map i.e Function, Telephone No, Fax No ect.. will not map. I'm at a loss as to why not?
note: running CRM 4.0
Any help with this would be greatly appreciated.
Regards,
Philip Johannesen

Thanks Saquib, the OSS note was very informative.
Do you know where I can find " In addition, you can find DXWB/LSMW examples under service.sap.com/CRM-Integration which you can install in a CRM system and use as models."?
I've looked under the new link "service.sap.com/crm-netweaver". But have been unable to find any examples.
I've awarded points as promised.
Regards,
Philip Johannesen

IDOC Message Type FIDCCP02 - Error RW029

Hi All,
We are trying to post a FB01 using a IDOC message type - FIDCC2 and struck at error message -
Accounting transaction not permitted for posting in FI/CO
Message no. RW029
When i try to post directly using the exact data in the IDOC, through FB01, there is no problem.
Debug showed that the error is in the following -
Include LRWCLF01
check business process
SELECT SINGLE * FROM t022 INTO ld_t022
WHERE activity = t_acchd-glvor.
IF sy-subrc IS INITIAL.
IF LD_T022-VORGTYP = 0 OR <---------
IF ld_t022-satztyp <> 0.
MESSAGE e029 WITH t_acchd-glvor.
ENDIF.
ELSE.
MESSAGE e029 WITH t_acchd-glvor.
ENDIF.
If this is not the right message type to use, can you suggest any other message type? FB01 we are trying to post is a simple GL posting, no tax, no withholding, etc. IDOC is just a 2 line posting.
Any help/advice is highly appreciated.
Many Thanks,
Shashi

Hi Shashi ,
This table is for Business Process t022 based on activity .
Check your customise settings .
There is no problem with message type .
Please reward if useful

IDOC Message type from XI

Hi,
I'm sending idoc type ORDERS05 from XI. Previously, I had set up message type ORDERS for this IDOC in the partner profile. But then I changed message type to ORDRSP, and process code ORDR for inbound idocs. I've also set message type ORDRSP for IDOC type ORDERS05 in WE82 message type - idoc type linking.
But for some reason, the IDoc is looking for message type ORDERS and not taking message type ORDERSP, and it is erroring in SAP, when I view the status of the IDoc it says that EDI Profile ORDERS Message type was not found.
So my question is - is this message type for an idoc type to be used passed somewhere from XI, do I have to make a change in XI side, or SAP side.

Hi,
I did all these changes, in the IDOC mapping in XI and also selected the option to select control record from payload in the idoc adapter. The messge in SXMB_MONI, I can see that EDI_DC40 has mestyp ORDRSP, but when I see SAP we02 IDOC transaction, it says that message type is ORDERS. Don't know why this is still happening? Any other option needs to be checked guys?
Regards,
Vijay
Message was edited by: vijay srikanth

IDOC Message type for FB01 transaction.

Hi,
I am going to get a file which I will pass through PI (XI) and bring into IDOC and post into SAP ECC 6.0.
I just wanted to know which IDOC message type / basic type I should use for posting an FI document i.e. FB01 transaction.
Rgds

Hi,
please read SAP notes 892103 and 551035.
The correct IDOC type should be FIDCC1 / FIDCC2.
Best regards,
Andreas

Contract creation in Backend with Idoc message type BLAORD

Hello,
We are creating Backend contracts from the Bidding engine functionality. We only want to create backend contracts and did the necesary configuration.
We activated BADI: BBP_DETERMINE_LOGSYS
Method CONTRACT_LOGSYS_DETERMINE.
We did not yet implement BADI:
BBP_CTR_BE_CREATE in SRM 5.0
In SAP R/3 Backend system (Version 46C) we see SAP is trying to create a contract via Idoc message Type: BLAORD.
In the trx BD87 in the backend we get status 51 :
Mesage number: 00 055
"Make an entry in all required fields"
In the segments of the Idoc however we do not see which field is missing!
How can we best analise this problem. Or maybe anyone can give us a a hint what is missing.
Thanks for any reply.
Aart

Hello RRK,
In ref. to your mentioning to change the backend configuration from WKK to MKK might not be as easy to do for organizations. As those configurations effect the overall creation of purchasing document types in R/3.
The Key issue is why the "Target Value" in the Header of the SRM GOA does not get transferred to the R/3 contract. That's why the issue is still there.
Were you guys able to figure out why that was missing? In the BLAORD IDoc the Target Value seems to not get transferred from SRM - its 0.00 if the IDoc is reviewed in WE19. This seems to be the problem.
Just wanted to know if you see the same issue in ur system.
Thanks.
Sunny.

IDOC message type LOIPLO not triggering

Similar Messages

Maybe you are looking for