IDOC Message type 'ORDCHG' - Sales Order Delete funcanility

Dear Guru's,
I have a requirement for a client where client is sending a EDI message to change & Delete a Sales order. I have mapped change option with IDOC message type 'ORDCHG' and basic message type 'ORDERS05'. Change option for the sales order is working fine.
Can any one tell me with message type 'ORDCHG'. how to delete a Sales Order. In EDI, client is passing only Header segments with Summary details.
Your reply will of greate help to me.
With Best Regards,
M. Rajendran.

Hi Ram,
Thanks a lot for sharing the link, but this dint solve my purpose. I have a different case all to geather.
My client is passing only Header segment and summary segment in the EDI. Thru ORDCHG i need to cancle/Delete entire sales order.
But i found that in standard IDOC Message type 'ORDCHG' only line item deletion/Cancle is availble but i wanted to delete/cancle entire sales document.
Any possibilites available in ORDCHG. Your reply will be much appreciated.
Thanks in Advance.
With Best Regards,
M. Rajendran.

Similar Messages

What is the IDOC Basic Type for sales order creation

Hi Experts,
Can anyone tell me Idoc Basic type for sales order creation.
Thanks
Prashant

Hi,
The basic types for creating the order are:
1.Orders01
2.Orders02
3.Orders03
4.Orders04
5.Orders05.
The basic type for SIS order is:
SISCSO01.
Regards,
Krishna.

Output Type on Sales Order delete

Is it possible to activate Output Type, sending iDoc, on Sales Order deletion?
On Sales Order create, change it works well, but not on delete.

hi,
this is Possible.
but it is not possible through Message Control ..
you need to write custom program..
that program read deletion data from CDHDR and CDPOS table and append data to idoc and post.
Prabhudas

New Message type for Sales orders

Hi,
We have the message type is ORDSRP(ORDERS05) and Function module IDOC_OUTPUT_ORDRSP for the sales orders.
We have lot of custom fields to be added to the IDoc.
Can any one suggst if it is better extending the current message of create a new one.
Thanks.
Rohita.

Hi Rohita,
Instead of changing the standard domain, You have to make the changes in the User Exit.
Say Qualifier 001,002,003 were already there in the domain.
001--Purchase Date
002--Delivery Date
003--Ordered Date
In the user exit u have to just add the segment and the qualifier without making any changes to the Standard Domain.
These Qualifiers are just like other variables and u can add whatever values to them that u want..
You can add Qualifier 004 for Trnasportation Date or Goods issue date and have to communicate the MiddleWare informing that date with this Qualifier will be Transportation Date and they will do the mapping to the corresponding field in other syste.
You can have as many message types as u want for the same IDoc type. There is no harm in having multiple message type. And u dont need to change the standard domain. It can be done without changing the domain.
If u analyse the FM closely u will realise that they have done coding for those values in the domain.
So instead of adding it to domain u just have to do the coding for this new qualifier.
Revert back if u need any help on it.
Thanks...
Message was edited by:
Utsah Garg

Idoc message type for open orders & Open JIT lines

Hi,
I need to send Open Purchase Order data and Open JIT lines data to supplier daily via Idocs.
Is there any standard messege type available for this data.
Regards

Hi Rohita,
Instead of changing the standard domain, You have to make the changes in the User Exit.
Say Qualifier 001,002,003 were already there in the domain.
001--Purchase Date
002--Delivery Date
003--Ordered Date
In the user exit u have to just add the segment and the qualifier without making any changes to the Standard Domain.
These Qualifiers are just like other variables and u can add whatever values to them that u want..
You can add Qualifier 004 for Trnasportation Date or Goods issue date and have to communicate the MiddleWare informing that date with this Qualifier will be Transportation Date and they will do the mapping to the corresponding field in other syste.
You can have as many message types as u want for the same IDoc type. There is no harm in having multiple message type. And u dont need to change the standard domain. It can be done without changing the domain.
If u analyse the FM closely u will realise that they have done coding for those values in the domain.
So instead of adding it to domain u just have to do the coding for this new qualifier.
Revert back if u need any help on it.
Thanks...
Message was edited by:
Utsah Garg

IDOC Message Type LOIPRO (Production order)

Hi All,
How I can setup Process code for inbound Production order (Message Type LOIPRO)
I receive idoc file from external SAP system I try to use "BAPP" , "ABI_AIDN_IN" , "APLI" it not work for
this message type. Idoc error message "Function module not allowed: APPL_IDOC_INPUTI"
Regards,

It should go with BAPI..have you tried that?

Inbound IDOC - ORDCHG - Sales Order

Hi,
I have to change both header and item of the sales order using IDOC message type - ORDCHG.
I'm passing Sales Order# to the E1EDK01-BELNR and E1EDK01-ACTION = '002' for orders header.
when i test using WE19, It's creating a new document instead of changing the existing sales order.
Am i doing something wrong here? any inputs from you guys?
Thanks,
Arun

What is the process code you are using in the partner profile? What is the FM assigned to that process code?
For change it should be calling IDOC_INPUT_ORDCHG, while it seems it is callingIDOC_INPUT_ORDERS, check that and you will be fine

Trigger IDoc when ever a Sales Order is rejected

Hello Experts,
How to trigger an IDoc when ever a sales order is rejected.
Thanks,
Srikanth

you have to define a message type that is triggered when the reason of rejection in not initial.
You can do it by a standard access sequence. Then issue the message with medium 6.
Best regards
Roberto Mazzali

IDOC message type and message code and function?

Hai...
anyone can explain with example what is IDOC message type and message code and function? how it is used?
regards,
prabakaran

Hi
An IDoc type can be implemented for various "logical" messages; one message can also be assigned to different IDoc types (m:n relationship).
The message is defined by the values for message type (required), message code (optional) and message function (optional). These three fields belong to the key fields in the partner profiles, which are used, for example, to determine inbound processing. If the 'Message type' field is not maintained (e.g. in the case of a control record from Release 2.1, in which MESTYP did not exist), the IDoc Interface uses the value from STDMES (EDI message type).
If possible, the descriptions of the message type should be linked to the corresponding EDI message type.
The message ORDERS (= message type) identifies purchase orders (outbound) and sales orders (inbound).
Message code or Process Code for Inbound Processing
Code which identifies a process type.
The process type determines which process is used to convert an IDoc to an SAP document.
Process code for outbound processing
Code which identifies the type of data which is to be sent via the IDoc interface.
Using the process code, the IDoc interface finds the application selection module which converts the SAP document into an IDoc.
The process code is only used with applications which perform outbound processing via Message Control (NAST).
Thanks & Regards
Kishore

Single idoc generation for multiple sales orders

Hi,
Pls let me know how do we generate single idoc for multiple sales orders.
Its not collecting idoc. As we know we can generate an idoc for one sales order correspondingly
my requirement is to generate single idoc number for multiple sales orders.
Do we need to write a program.

Amar,
To understand take HRMD_A04 as example. Root segment has Maximum 9999999999 defined.
Segm.type E1PLOGI
Minimum number 1
Maximum number 9999999999
Parent segment
Hier.level 2
This means that this IDOC types has capability to hold multiple HR Master data objects. PFAL program creates this IDOC and it has facility to mention the Objects per process, check selection screen.
I checked for INVOICE01/02 its not possible there. Hope this clarifies.

Inbound IDoc used for updating Sales order status

I have a requirements to set use standard IDoc to send out the Sales order to a non-SAP software as well as receiving Inbound IDoc to update the status of sales order in SAP. Could someone comment on my questions below:
1. What are the difference between all the ORDERSxx Idoc types?
2. What IDoc should be used for Inbound IDoc to update the sales order stataus in SAP?
3. Can the same IDoc type be used for both Inbound and Outbound with only the difference in the segment of Direction?
Thank you. Points will be awarded appropriately for helpful comments.

Hi,
1.Intially standard IDOC types "ORDERS01" is having limited
      segments. After few months the requirement got increased to
      add more fields to "ORDERS01".So,once you release the IDOC
      type you can not add any more fields .So SAP come up
      with "ORDERS02" with new fields.Like that all IDocs types have
      some more new seg ments.
2.You can use ORDER05
3. Yes you can use same IDOC type

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!

IDoc Message Type to create Inbound Delivery + Confirm + GR

Hi Experts,
I need IDoc message type which can create Inbound Delivery / Confirm / Create GR with Inbound Delivery as reference and i dont want to use DELVRY05
because I need to create Inbound Delivery / PICK / Confirm but not with Transfer Order Creation means Unnecessarily we dont want to create Transfer Orders. We need to exclude Transfer Orders and create GR.
Please do the needful.

Dear Kishore,
It's possible via writing code in enhancement spots of transaction code VL31N, MIGO_GR/MB01.
R,
Amala

Manual Condition type in Sales Order

Hi,
i need to enter a manual condition type in sales order which should come in % and the value should not come or it should come as zero, Is there any way to make that manual condition value as Zero in sales order.
Ragu

Raghu,
Pls check the OSS notes 392668, that will solve your problem.
The same pasted here for your reference. However, I advise you to download it and then read due to inconsistent formatting here.
Reward if this helps.
When you create documents in which the standard pricing is used to determine condition records as well as to calculate a pricing result, the display and entry of manual entries is not clear in the relevant condition screen (screen 6201 in the SAPLV69A or SAPMV61A programs for releases prior to 4.6A).
This note explains the interaction of manual entries with the attributes maintained in the pricing procedure and in Customizing of the condition type.
Other terms
KAUTO, V/06, V/08, KAEND fields, KOZGF, PRICING_CHECK, LV61AU08, XKOMV_ERGAENZEN_MANUELLE, LV61AA53, manual entries, MANU
Reason and Prerequisites
In the pricing Customizing, the following fields affect the manual entry of complete condition lines or individual condition rates:
Description        Technical name              Maintenance transaction in SD
Access sequence    KOZGF                  V/06 and V/07
'Manu'            KAUTO                  V/08
Depending on the characteristic of the mentioned fields, the pricing condition screen appears as follows:
KAUTO   | KOZGF    | Condition record existing on DB? | Result
Initial | Initial   | -                                | (1)
Initial | Existing | No                              | (2)
Initial | Existing | Yes                              | (3)
Set     | Initial   | -                                | (2)
Set     | Existing | No                              | (2)
Set     | Existing | Yes                              | (4)
Result (1)
A condition line is set for the relevant condition type [KSCHL]. The 'Condition rate' field [KBETR] does not contain a value, but is ready for input. The displayed line serves as an input help or a template for the manual entry.
Result (2)
No relevant condition line is set on the pricing condition screen, in other words, the condition type is missing.
If you enter the condition type manually without entering a condition rate in the same processing step, you get a 'template line' as described in (1).
Result (3)
A suitable condition record that exists on the database is set with amount (= normal, automatic determination).
Both the 'Condition origin' indicator [KHERK] and the 'Condition control' indicator [KSTEU] are set to 'A'.
If you create another line with this condition type and enter a condition rate not equal to zero, a line is set with this condition rate.
The 'Condition origin' indicator [KHERK] as well as the 'Condition control' indicator [KSTEU] has characteristic 'C'.
If, on the other hand, you create another line and enter a condition rate of zero (or do not enter any condition rate) and the condition record that exists on the database has a scale, the system sets the condition rate according to the achieved scale level. If zero is to be set as the condition rate even if scales exist, then use modification Note 179354. If no scale is maintained, then the system always sets zero as the condition rate.
In these cases, the 'Condition origin' indicator [KHERK] has characteristic 'C', the 'Condition control' indicator [KSTEU] characteristic 'A'.
Result (4)
No relevant condition line is set on the condition screen, even though a condition record suitable for the access sequence exists on the database. The pricing analysis displays the message "Manual condition (Condition record exists)". If you enter the condition type manually without entering a condition rate in the same processing step, the record that exists on the database is set. If a condition record has a scale, the system sets the condition rate of the first scale level independently of the achieved scale level.
In this case, the 'Condition origin' indicator [KHERK] has characteristic 'C', the 'Condition control' indicator [KSTEU] has characteristic 'A'.
Thus, the setting variant leading to result (4) serves to suppress the setting of automatically found condition records into a pricing result. However, you can add the maintained record to the already determined pricing result by entering the relevant condition key.

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

IDOC Message type 'ORDCHG' - Sales Order Delete funcanility

Similar Messages

Maybe you are looking for