Issues during Contract creation using Inbound IDOC BLAORD03

Dear Experts,
We need to create Contract using Inbound IDOC BLAORD03.
I am facing following issues and need some one's help ASAP.
(1) Contract is generated without Header Texts and Item Texts through IDOC BLAORD03 .
(2) Not able to create CONTRACT for service masters using Inbound IDOC BLAORD03.
Is there any body who has implemented this scenario and able to guide ?
Looking forward to help ASAP.
Thanks in Advance,
Best Regards,
Mitesh Desai
[email protected]

Hi All,
I am also facing the same issue. I am trying to upload service outline agreements thru LSMW using idoc basiv type BLAORD03 ( FM->IDOC_INPUT_BLAORD).
Immediate help highly appreciated.
Thanks & Regards,
Vijender

Similar Messages

Creation of Inbound IDOC from a flat file.

Hi all,
I hav to create Purchse Order using inbound IDOC in which I hav to take data from a .xls or any flat file.
Can any one help me with this. i.e wat r the steps involed to do so.
Regards.
Rahul

Hello,
Why do u want to create a Idoc for creating PO from flat file - you can simply use BAPI. Ok if you want to create PO only using Idoc.
I think message type is ACC_PURCHASE_ORDER0.
I just made one sample program to you how to create a PO with Idoc method. Here i am doing for Material Master Creation. Let me know if want any clarification.
********Poorna********
TABLES : MARA, MAKT, EDP13.
DATA : I_EDIDC LIKE EDIDC OCCURS 0 WITH HEADER LINE,
      I_EDIDD LIKE EDIDD OCCURS 0 WITH HEADER LINE.
PARAMETERS : P_MATNR LIKE MARA-MATNR.
START-OF-SELECTION.
REFRESH I_EDIDC.
SELECT * FROM EDP13 WHERE MESTYP = 'ZMATMASTER'.
    MOVE-CORRESPONDING EDP13 TO I_EDIDC.
    I_EDIDC-IDOCTP = EDP13-IDOCTYP.
    APPEND I_EDIDC.
ENDSELECT.
READ TABLE I_EDIDC INDEX 1.
I_EDIDD-SEGNAM = 'ZMATMASTER'.
SELECT SINGLE * FROM MARA WHERE MATNR = P_MATNR.
SELECT SINGLE * FROM MAKT WHERE MATNR = P_MATNR
                              AND SPRAS = SY-LANGU.
I_EDIDD-SDATA+0(18) = MARA-MATNR.
I_EDIDD-SDATA+18(40) = MAKT-MAKTX.
I_EDIDD-SDATA+58(4) = MARA-MTART.
I_EDIDD-SDATA+62(1) = MARA-MBRSH.
I_EDIDD-SDATA+63(3) = MARA-MEINS.
APPEND I_EDIDD.
CALL FUNCTION 'MASTER_IDOC_DISTRIBUTE'
    EXPORTING
      master_idoc_control                  = I_EDIDC
   OBJ_TYPE                            = ''
   CHNUM                                = ''
    tables
      communication_idoc_control          = I_EDIDC
      master_idoc_data                    = I_EDIDD
EXCEPTIONS
   ERROR_IN_IDOC_CONTROL                = 1
   ERROR_WRITING_IDOC_STATUS            = 2
   ERROR_IN_IDOC_DATA                  = 3
   SENDING_LOGICAL_SYSTEM_UNKNOWN      = 4
   OTHERS                              = 5
COMMIT WORK.
IF sy-subrc <> 0.
MESSAGE ID SY-MSGID TYPE SY-MSGTY NUMBER SY-MSGNO
       WITH SY-MSGV1 SY-MSGV2 SY-MSGV3 SY-MSGV4.
ENDIF.

GR posting using inbound Idoc against Outbound delivery

Hi,
We are doing SAP ISR integration with third party POS and there we have a scanario where we have to post GR against outbound delivery using inbound Idoc. Can anybody help me out, how can we do it.
In SAP processing would happen using MIGO against outbound delivery number and movement type 101. We tried the same with Idoc WMMBXY message type but not suceed.
Looking for positive reply.
Regards
Vikrant pathak

Hi,
You can never do a GR against an outbound delivery, but where as you can do a GR against PO with reference to corresponding sales order with special stock indicator.
That means when the GR is done the goods what ever you have received is going to be blocked against the corresponding sales order and when you do the outbound delivery against the sales order stock is already available and the goods issue will happen smoothly without any errors.
We have implemented the same in my earlier project.
Thanks,
Mahesh.

Issue during automatic Creation of Work Order from Notification

Hi,
I have a issue during automatic Creation of Work Order from Notification.
BADI implemented: NOTIF_EVENT_POST
BAPI called in BADI: BAPI_ALM_ORDER_MAINTAIN
I am able to create Work Order successfully but after that i need to update notification header with created work order number.
But i am unable to update the same (VIQMEL-AUFNR).
Can anybody provide solution for the same!
Thanks,
Kumar.

Hi,
Any inputs on above posted issue!
Thanks in advance.
Thanks,
Kumar.

Automating Goods issue during Delivery creation

Hi all,
We have a requirement to automate the Goods issue creation for certain type of orders when the Delivery is getting created. The orders that need to be automatically Goods issued during delivery creation are identified based on certain plants. These plants are linked to certain output type and in the output type routine is the standard program RVADEK01 with one additonal code for automating the Goods Issue creation.
We have a custom table that holds the status of orders and there is a code in user exit userexit_save_document_prepare which changes the status of the order as closed when the goods issue is done.
But when the delivery is saved, in this case when an automatic goods issue needs to happen, when the flow reaches this user exit, the output type code dosenot get executed and the Goods issue is not done and so the custom table will not be updated with the closed status. So we are in need to findout a place where we can update the status of the order in that table.
The output type code is not executed even before the other user exit userexit_save_document. The output type code gets executed and goods issue is done after the this userexit_save_document when the COMMIT statement is executed in the subroutine BELEG_SICHEN_POST in the include FV50XF0B_BELEG_SICHERN.
I need help in finding out if any user exit or badi is called after this commit statement, so that I can add my code to close the status of the order in my custom table. Just after this commit the Goods issue happens and the VBFA table gets updated with the 'R' records for goods issue.
Please let me know if anyone has any idea on this. The ultimate goal is to find some place after the goods issue is done to update the status of the order as closed in the custom table we have.
Thanks,
Packia

Dear Siva,
As informed yesterday I changed the language from DE to EN, to match the other shipping points settings in table V_TVST, this did not bring the solution.
Please let me summarize, I am really desparate here:
This is only IM related, Not WM.
Picking lists are not printed for any Shipping Point from this warehouse, this is just a small subsidiary of my customer in Finland.
Issue is not Aut. PGI.
VP01SHP has not been configured for any shipping points, still there we do get the PR except for the new shipping point.
In the deliveries of correct processed shipping points I do not find any picking output type.
Item category in new shipping is equal to Item category in already existing shipping points, so no need to config here.
There is no picking block active.
PR creation happens once I enter the pick qty in the delivery in VL02N. This is the part that we need to have automated.
Can you please try to help me out?
Tnx & regards,
Chris

Purchase Order triggering Sales Order using Inbound Idocs

Hi All,
Can any one explain the flow of Purchase Order triggering Sales Order using Inbound Idocs..??
Thanks & Regards
Anoop

Use search tool to find sample like Integrating MM & SD Modules in Same Client to Create Sales order in Supplying Company Code Using PO raised in Receiving Company Code By I-Doc Message Type ORDERS Part1, Part 2 and Part 3.
Regards,
Raymond

I can create material using inbound Idoc of type MATMAS01, but not MATMAS05

I can create material using inbound Idoc of type MATMAS01 in WE19, but MATMAS05 failed. In fact I used same data ( different material number), and same inbound function, but got different result.
What is different between MATMAS01 and MATMAS05? Is there some configuation need for MATMAS05?
My system is ECC5.0. Thanks.

Hi, nagaraj
this is inbound IDoc, not outbound IDoc, so we can't assign Basic type in WE20, only can assign Message type.
In WE82, there are 5 records about Messagetype MATMAS:
     Message type   Basic type     Release
      MATMAS         MATMAS01        30A
      MATMAS         MATMAS02        30D
      MATMAS         MATMAS03        40A
      MATMAS         MATMAS04        46C
      MATMAS         MATMAS05        470
   I think it should be ok.
In WE57, there 2 records are exist:
   FM_name                 BasicType       MessageType
IDOC_INPUT_MATMAS01       MATMAS01         MATMAS
IDOC_INPUT_MATMAS01       MATMAS05         MATMAS
so I think all configurations should be ok.
Message was edited by:
        liu bin

Update EKKO Z field using Inbound Idoc

I have an requirement where I have to update Z field in EKKO while creating PO using inbound Idoc.
Basic Idoc Type: PORDC103
Function module: BAPI_PO_CREATE1
Extended POHEADER and EKKO with z field.
I am using exit EXIT_SAPL2012_001 to populate Z field while creating PO as below.
poheader-zfield = '123'.
extensionin-structure = 'Z_HEADER'.
extensionin-valuepart1 = '123'.
APPEND extensionin.
PO is getting created but z fields is not populated. Do i need to add any thing else apart from the above steps?.
Any help appreciated.

Rajitha,
Add your Z field in structure BAPI_TE_MEPOHEADER and a corresponding flag in BAPI_TE_MEPOHEADERX.
extensionin-structure = 'TE_MEPOHEADER'.
extensionin-valuepart1 = '__________123' "'10 spaces than value for the field'.
APPEND extensionin.
extensionin-structure = 'TE_MEPOHEADERX'.
extensionin-valuepart1 = '__________X' "'10 spaces than X.
APPEND extensionin.
You don't need to implement/use any exit for filling the custom fields.
Regards,
Diwakar

How to Create a Return Order wrt a Standard Order using Inbound IDOC Orders

HI,
We have a scenario :
Standard Order - is exiting in System with 2 line items :
Item 10
Qty 20
Item 20
Qty 30
Is it possible create a Return Order With Reference to this standard order for Line Item 20 only using inbound IDOC Orders?
If yes what should be the mapping in the IDOC about the Standard Order, Item and QTY ?
Regards
Anurag

hi,
try using this bapi.
/AFS/BAPI_SALESORD_CREATEFDATA.
thanks,
satish

Create credit memo request using inbound IDOC

Hi Experts,
I want to create credit memo request using inbound IDOC, currently I am using GSVERF03 basic type and process code GSVE, I am getting below error:
No records exist in T661W for vendor XXXXX, plant, unloading point
Anyone suggest me is this correct message type to create credit memo request or suggest me the correct one. because we are working with customer sales order and invoice not with vendor purchase order.
Thanks for your help.

ah, apologies i read outbound! I think you are using the correct message type i.e. GSVERF.
Can you not simply create the missing entry in T661W? i.e. for the missing records?

Using Inbound IDOC from Java system creation of Outbound delivery

Dear Experts,
The scenario we are having is really very interesting. Hopefully its a good learning for me and also for others also.
The scenario is,
After sales order creation the details will be sent to one Non SAP system (Java) for performing some tasks related to forwarding agent decision, shipping date and etc. Once the details are finalized in that Java system then, the details needs to be transferred to SAP as "Inbound IDOC" process. For this proposed to use the SAP Jco middle ware.
Once the details transfered from Java system to SAP then, the outbound IDOC needs to get generated automatically. Assuming the stock for that sales order line item is available. Also one more complexity is, our client is using custom transaction (ZVl10C) for delivery creation.
Now Query is,
1. Which IDOC, message type and Functional module needs to be used for creating the delivery automatically..??
2. As per assumption, stock of that sales order line item should be available. Due to some business reason the stock was removed during inbound IDOC transfer then, what will happen to the IDOC..?. How to avoid this situation..??
3. As we told we are re going to use SAP Jco b/w SAP & Java system. In this case, how the data will get transfered from Java system to SAP..?
Thanks in advance for the replies I am going to get
Regards,
VEL

Thanks for the feedback. This question is resolved

IDOC transfer during Contract Creation

Hi All,
I have a requirement with the contract creation in SRM contract management.
Do you Know which IDOCs is/are transmitted to the ERP during a contract creation?
Thanks in Advance!
Martin.

Hi Martin,
To add further to Claudia's note, Message Types "BLAORD" & "COND_A" are set-up in ECC as incoming. There is no Mesage Type set-up for these (as OUTBOUND) on SRM side.
In SRM, Message Type "BLAREL" should be set-up as INBOUND. This carries the release information for the contract from ECC to SRM.
Cheers,
Akash

Inbound delivery creation using shipment Idoc details

Hi,
   My requirement is that I need to create inbound delivery using SHPMNT05 idoc sending from a different plant.
Below are the fields I am getting from the SHPMNT05 Idoc. So I need to create Inbound delivery in Receiving plant.
SAP - Field     IDoc Segment- Position - Field Name
LIKP-LFART     E1EDL21 001 LFART
LIKP-LIFEX     E1EDT01 001 VBELN
LIKP-LIFNR     E1EDT44 009 LIFNR
LIKP-MBDAT     E1EDL24 039 = ABRDT
LIPS-LFIMG     E1EDL24 013 LFIMG
LIPS-MATNR     E1EDL24 002 MATNR
LIPS-VGPOS     E1EDL41 006 POSEX
LIPS-PSTYV     E1EDL26 001 PSTYV
LIPS-VGBEL     E1EDL41 002 BSTNR
LIPS-VRKME     E1EDL24 014 VRKME
VEKP-EXIDV     E1EDL37 001 EXIDV
VEKP-VHILM     E1EDL37 017 VHILM
VEPO-MATNR     E1EDL44 007 MATNR
VEPO-POSNR     E1EDL44 003 - POSNR
VEPO-VBELN     E1EDL44 002 - VBELN
VEPO-VELIN     E1EDL44 001 VELIN
VEPO-VEMEH     E1EDL44 006 VEMEH
VEPO-VEMNG     E1EDL44 005 VEMNG
Could you please help me to find some workaround to solve this ?
Thanks in advance.
Regards.
Ranjith

Hi Ranjith,
I guess there is a BAPI " /SPE/INB_DELIVERY_REPLACE " which can be used to create an inbound delivery.
Documentation-
FU /SPE/INB_DELIVERY_REPLACE
Short Text
Create inbound delivery
Functionality
You can use this method to distribute inbound deliveries from an ERP system to a WM system.
The following parameters are required:
HEADER_DATA Inbound delivery header data
SENDER_SYSTEM System of the sender
HEADER_PARTNER Header data of the partners
HEADER_DEADLINES Header data of the dates
ITEM_DATA Item data of the inbound delivery
ITEM_ORG Organisation data of the inbound delivery
Notes
The required parameters have the following required fields:
Import parameter HEADER_DATA
INB_DELVRY_NO
DLV_TYPE
Import parameter SENDER_SYSTEM
SENDERSYSTEM
Table parameter HEADER_PARTNER
PARTN_ROLE = 'LF'   Vendor is required partner
PARTNER_NO
Table parameter HEADER_DEADLINES
TIMETYPE = 'WSHDRLFDAT' Delivery date
Table parameter ITEM_DATA
INB_DELVRY_NO
ITM_NUMBER
MATERIAL
DLV_QTY
SALES_UNIT_ISO oder SALES_UNIT
Table parameter ITEM_DATA_ORG
PLANT
Further information
HEADER_PARTNER
Since the partners in the delivery are not managed on an item basis, the ITM_NUMBER field in the BAPIDLVPARTNER segment is left blank and not analyzed.
HANDLING_UNIT_ITEM
If the BAPI is used as an external interface for an external system, the packing hierarchy should be described as usual by using external identification numbers for shipping materials (HDL_UNIT_EXID_INTO/HDL_UNIT_EXID).
Parameters
HEADER_DATA
SENDER_SYSTEM
TECHN_CONTROL
HEADER_DATA_SPL
HEADER_CONTROL_SPL
HEADER_PARTNER
HEADER_PARTNER_ADDR
HEADER_DEADLINES
ITEM_DATA
ITEM_ORG
ITEM_STOCK_TRANS
ITEM_CODING_BLOCK
ITEM_REF_PURCHASE_ORDER
ITEM_SERIAL_NO
ITEM_DATA_SPL
TEXT_HEADER
TEXT_LINES
HANDLING_UNIT_HEADER
HANDLING_UNIT_ITEM
HANDLING_UNIT_SERNO
HANDLING_UNIT_ITEM_SPL
HANDLING_UNIT_HEADER_CROSS
HANDLING_UNIT_IDENTIFIERS
EXTENSION1
EXTENSION2
RETURN
TOKENREFERENCE
Exceptions
Function Group
/SPE/INB_DELIVERY
Check if this helps.
Reward helpful answers.
Regards
Parag

Outbound delivery creation with inbound IDOC transfer from Java system

Dear Experts,
       The scenario we are having is really very interesting. Hopefully its a good learning for me and also for others also.
The scenario is,
               After sales order creation the details will be sent to one Non SAP system (Java) for performing some tasks related to forwarding agent decision, shipping date and etc. Once the details are finalized in that Java system then, the details needs to be transferred to SAP as "Inbound IDOC" process. For this proposed to use the SAP Jco middle ware.
             Once the details transfered from Java system to SAP then, the outbound IDOC needs to get generated automatically. Assuming the stock for that sales order line item is available. Also one more complexity is, our client is using custom transaction (ZVl10C) for delivery creation.
Now Query is,
               1. Which IDOC, message type and Functional module needs to be used for creating the delivery automatically..??
               2. As per assumption, stock of that sales order line item should be available. Due to some business reason the stock was removed during inbound IDOC transfer then, what will happen to the IDOC..?. How to avoid this situation..??
               3. As we told we are re going to use SAP Jco b/w SAP & Java system. In this case, how the data will get transfered from Java system to SAP..?
Thanks in advance for the replies I am going to get
Regards,
VEL

Didn't get any feedback from experts for long time. So we are closing the question

Sales Order Creation using LSMW IDOC method.. ( Custome Interface)

Hi ABAP'rs,
                 Please provide me LSMW steps for creating Sales Order using IDOC method.
                        Thanks and Regards,
                                              Param.

LSMW-IDOC in General
LSMW Step by Step Guide: Legacy System Migration Workbench is an R/3 Based tool for data transfer from legacy to R/3 for one time or periodic transfer.
Basic technique is Import data from Spreadsheet / Sequential file, convert from source format to target format and import into R/3 database. LSMW not part of standard R/3, if we need this product email [email protected]
Advantages of LSMW:
Most of the functions are within R/3, hence platform independence.
Quality and data consistency due to standard import techniques.
Data mapping and conversion rules are reusable across projects.
A variety of technical possibilities of data conversion.
Generation of the conversion program on the basis of defined rules
Interface for data in spreadsheet format.
Creation of data migration objects on the basis of recorded transactions.
Charge-free for SAP customers and partners.
Working With LSMW:
Use TCODE LSMW
Objects of LSMW:
Project ID with max of 10 char to Name the data transfer project.
Subproject Used as further structuring attribute.
Object ID with max of 10 Characters, to name the Business object .
Project can have multiple sub projects and subprojects can have multiple objects.
Project documentation displays any documentation maintained for individual pop ups and processing steps
User Guide: Clicking on Enter leads to interactive user guide which displays the Project name, sub project name and object to be created.
Object type and import techniques:
Standard Batch / Direct input.
Batch Input Recording
   o If no standard programs available
   o To reduce number of target fields.
   o Only for fixed screen sequence.
BAPI
IDOC
o Settings and preparations needed for each project
Preparations for IDOC inbound processing:
Choose settings -> IDOC inbound processing in LSMW
Set up File port for file transfer, create port using WE21.
Additionally set up RFC port for submitting data packages directly to function module IDoc_Inbound_Asynchronous, without creating a file during data conversion.
Setup partner type (SAP recommended US) using WE44.
Maintain partner number using WE20.
Activate IDOC inbound processing.
Verify workflow customizing.
Steps in creating LSMW Project:
Maintain attributes choose the import method.
Maintain source structure/s with or without hierarchical relations. (Header, Detail)
Maintain source fields for the source structures. Possible field types C,N,X, date, amount and packed filed with decimal places.
Fields can be maintained individually or in table form or copy from other sources using upload from a text file
Maintain relationship between source and target structures.
Maintain Field mapping and conversion rules
For each Target field the following information is displayed:
o Field description
o Assigned source fields (if any)
o Rule type (fixed value, translation etc.)
o Coding.
o Some fields are preset by the system & are marked with Default setting.
Maintain Fixed values, translations, user defined routines Here reusable rules can be processed like assigning fixed values, translation definition etc.
Specify Files
o Legacy data location on PC / application server
o File for read data ( extension .lsm.read)
o File for converted data (extension .lsm.conv)
Assign Files to defined source structures
Read data Can process all the data or part of data by specifying from / to transaction numbers.
Display read data To verify the input data being read
Convert Data Data conversion happens here, if data conversion program is not up to date, it gets regenerated automatically.
Display converted data To verify the converted data
Import Data Based on the object type selected
Standard Batch input or Recording
o Generate Batch input session
o Run Batch input session
Standard Direct input session
o Direct input program or direct input transaction is called
BAPI / IDOC Technique:
IDOC creation
o Information packages from the converted data are stored on R/3 Database.
o system assigns a number to every IDOC.
o The file of converted data is deleted.
IDOC processing
o IDOCS created are posted to the corresponding application program.
o Application program checks data and posts in the application database.
Finally Transport LSMW Projects:
R/3 Transport system
o Extras ->Create change request
o Change request can be exported/imported using CTS
Export Project
o Select / Deselect part / entire project & export to another R/3 system
Import Project
o Exported mapping / rules can be imported through PC file
o Existing Project data gets overwritten
o Prevent overwriting by using
Import under different name
Presetting for Inbound IDOC processing not transportable.
Reward if useful.
regards
santhosh reddy

Issues during Contract creation using Inbound IDOC BLAORD03

Similar Messages

Maybe you are looking for