IP_MESSAGE_PARAMETER for inbound

Hi,
Am using B2B for Inbound messages when i send the message from outside to B2B,am getting following error
weblogic.work.j2ee.J2EEWorkManager$WorkWithListener@1025142] [userId: <anonymous>] [ecid: 0000ITYFXry7MAYVLqBT8A1Bb^1000002I,0] [APP: soa-infra] Error -: B2B-50083: Document protocol identification error.[[
at oracle.tip.b2b.engine.Engine.identifyDocument(Engine.java:4203)
at oracle.tip.b2b.engine.Engine.processIncomingMessageImpl(Engine.java:1850)
at oracle.tip.b2b.engine.Engine.processIncomingMessage(Engine.java:1395)
at oracle.tip.b2b.engine.Engine.incomingContinueProcess(Engine.java:3216)
at oracle.tip.b2b.engine.Engine.handleMessageEvent(Engine.java:2960)
at oracle.tip.b2b.engine.Engine.processEvents(Engine.java:2706)
at oracle.tip.b2b.engine.ThreadWorkExecutor.processEvent(ThreadWorkExecutor.java:540)
at oracle.tip.b2b.engine.ThreadWorkExecutor.run(ThreadWorkExecutor.java:200)
at oracle.integration.platform.blocks.executor.WorkManagerExecutor$1.run(WorkManagerExecutor.java:77)
at weblogic.work.j2ee.J2EEWorkManager$WorkWithListener.run(J2EEWorkManager.java:183)
at weblogic.work.DaemonWorkThread.run(DaemonWorkThread.java:30)
[SRC_CLASS: oracle.tip.b2b.system.DiagnosticService] [APP: soa-infra] [SRC_METHOD: log] class oracle.tip.b2b.metric.B2BMessageProperties[[
fromTP : null
toTP : null
DocumentProtocol : null
DocumentProtocolVersion : null
DocumentType : Acknowledgement
Agreement : null
MessageSize : 12095.0
MessageState : ERROR
FromEndpoint : http://192.168.200.30:8080/as2/HttpReceiver
FromEndpointProtocol : HTTP
FromEndpointStatus : CONNECTED
ToEndpoint : http://192.168.200.188:8001/b2b/httpReceiver
ToEndpointProtocol : HTTP
ToEndpointStatus : CONNECTED
Application : null
Application : null
Composite : null
CompositeVersion : null
Service/Reference : null
So my question is how can i set the above parameter for inbound files.
This is an urgent,please help on this.
Thanks,
Arun Jadhav

Hi Dheeraj,
I am using custom document type.
Am trying to send one document from the AS2 server to B2B, but on B2B am getting document protocol Error.
I have also created the channel for my trading partner which in address of AS2 server
In above mention error log you can see that B2B is not getting the required parameter values.
How does the B2B know that particular message is for any of the document type created in B2B.
Thanks,
Arun Jadhav.

Similar Messages

SAP System inconsistency for Inbound delivery / MIGO and a "sap note"

Hello Friends ,
After following SAP instruction on how to remove the inconsistency between posting GR through MIGO (Inv. mang.) and the reflection of the goods movement status in the inbound delivery document - done that using sap note 570991
the problem is that the system start behaving in a weird way throwing unjustified Error messages for any suggested goods receipt using MIGO with reference to inbound
for example after creating an inbound delivery document and trying to post it via migo , an error will pop up
- Inbound delivery storage location cannot be changed to here Message no. VLA316
the thing is i didn't even maintain any storage location entry up to that point and yet i cannot post any stock !!
also another error like
- Inbound delivery batch cannot be changed to *** here
which doesn't make any sense because there is not batches in the inbound document !!
i think this behavior is coming from the "Document Flow Update for Stock Postings" inbound indicator at the shipping parameter at client level customization
i need help on how to overcome this annoying SAP Bug/Problem specially i am in a post go live critical situation

Hi,
The messages you mentioned were introduced to avoid inconsistency between inbound delivery and IM, through the note: 1050944 - GR for inbound delivery using inventory mgmt as of ECC 6.00
If the messages are issued incorrectly, then you may check for SAP notes (I couldnt find anything relevant) or raise an OSS ticket to SAP.
Regards,
AKPT

Automatic TO Creation for Inbound Deliveries

I would like to have TO created automatically for Inbound delivery for PO.
1) I have set the Automatic TO = A in Mvmt Type 101 for my warehouse in transaction OMKZ.
2) I have set Immediate TO Creation and Mail Control = A for Mvmt Type 101, Mvmt Indicator =B, Mvmt Type 101, TR Create =X for my warehouse in transaction OMKX
3) I have assigned Routine #32 to Application E1 in transaction VOFM
4) I have created output conditon WMTA for delivery type EL with Medium =8 and Date/Time =4.
Tranfer order is not created when the delivery is created via transaction VL34. The output determination analysis indicates that WMTA was ignored because requirement 032 not fulfilled. What am I missing?
Thank you.

Hi Julie Simonds
I believe you are working with Inbound delivery with Item catagory as ELN.
Please check if Relevant for putaway is checked.
Path for your refernce :
SPRO > LE > Shipping > Deliveries > Define Item catagory for deliveries.
Thanks,
Mahesh

New Condition TAble for Inbound Delivery

Hello
i want to maintain a new Condition table for the Inbound delivery picking with the combination of _Delivery type/Plant
so that the Inbound created for the particular plant alone uses the particular output type.
Where in IMG can i configure the new Condition table for this combination for the Inbound delivery ?

Hi,
Go to SPRO > Logistics Execution > Shipping > Basic Shipping Functions > Output Control > Output Determination > Maintain Output Determination for Inbound Deliveries > Here perform following;
- Define Condition Table for Inbound Delivery
- Define Output Types for Inbound Delivery
- Define Access Sequence for Inbound Delivery
- Maintain Output Determination Procedure
- Assign Output Determination Procedures

IDOC for inbound delivery

Hi Gurus,
Pls help me to understand this functionality:
Shipments destined for a Distribution Center will generate ASNu2019s(advance shipping notification) to alert the Distribution Center to the upcoming receipt.
There are two variations of the transaction that will initiate the ASN:
u2022 Receipt of an ASN from a vendor to a Distribution Center will result in the creation of an Inbound Delivery. That Inbound Delivery must be sent to WM via IDOC.
u2022 Shipments from Distribution Center to DC will create an Outbound Delivery from the u201CClose Loadu201D process in Warehouse M. Creation of the Outbound Delivery to another DC is the trigger for the IDOC to WM.
The IDOC to be used could be a variation of the DELVRY03.
My doubts includes:
1. can I use one idoc for both the scenarios?
2. both are outbound idocs or not?
3. Any suggestions how to do this?
Thanks..
SD

>
Shibu David wrote:
> My doubts includes:
> 1. can I use one idoc for both the scenarios?
Yes you can use IDOC DELVRY03 for both scenarios
>
Shibu David wrote:
> 2. both are outbound idocs or not?
No.
ASN sent to DC will be outbound message.
ASN received by DC, which creates Inbound delivery is inbound message.
>
Shibu David wrote:
> 3. Any suggestions how to do this?
As far as I know message type used in SAP for ASN is DESADV.
For inbound ASN use process code DELS and for outbound use DELV

Confirmation control key check for inbound delivery creation

Hi,
Currently, in the Client's company, the process of receiving goods from purchase orders looks like that (SAP-wise):
- create a purchase order,
- receive goods using MIGO and automatically create an inbound delivery,
- pack the delivery and post goods receipt.
Recently, some patches have been installed, including one described by note 1602047 (which basically enforces checking confirmation control keys if goods receipt assignment and goods receipt relevance are activated for inbound deliveries). Note says that it only affects two-step stock transfer and creation of automatic inbound deliveries using SPED output but it seems it also affects other basic processes like PO receipt in MIGO.
Now, when using the old control key (that had MRP-Relevant and GR-Relevant fields checked), the system is unable to automatically create an inbound delivery after the goods receipt is posted with MIGO (with message VL148 - Not possible to create an inbound delivery). I learned that this is because the "GR Assignment" field must be checked in the confirmation control key so it's possible to automatically create aninbound delivery after receiving a purchase order in MIGO.
After changing the confirmation control key to have the missing field checked it's not possible anymore to receive goods from PO in MIGO as the PO requires shipping notification in order to be processed in MIGO thus requiring of manual creation of an inbound delivery.
Is there any way to skip this check so the process would remain the same (this model has been working fine for few years in the Client's system) and the inbound delievery would be created automatically after posting the receipt in MIGO?
Thanks in advance,
Piotr

Hi,
don't know if you found a solution, but we received the following message from SAP:
The advent of the new version requires some attention to the users. It
was necessary to avoid inconsistencies which in the past version the
system was susceptible.
Main Program SAPMM07M
Source code of MM07MLVS
sy-msgid VL sy-msgty E sy-msgno 148
I have checked the process and through debugged I could confirm the
following information SAP is providing to all similar incidents reportedfor us:
Error message VL 148 is issued if in the confirmation control key used
in the purchase order, the fields for MRP-relevance (T163G-KZDIS),
GR relevance (T163G-WEREL) and GR assignment indicator (T163G-WEZUO)
are not set.
The correction of note 1602047 was necessary to avoid inconsistencies
(table EKES) in the purchase order. Without having the GR assignment
(T163G-WEZUO) set, there is no unique reference created between the
purchase order history (table EKBE) and the inbound delivery
confirmation (table EKES) at goods receipt which leads to a problem if
several inbound deliveries exist for the same purchase order.
If you set T163G-WEZUO to 'X', this assures that, for an inbound
delivery, the confirmation record (EKES) belonging to this inbound
delivery (EKES-VBELN) is also accurately updated at goods receipt.
How to solve the issue?
Use a confirmation control key with the GR assignment indicator set
and then create the inbound delivery with VL31N. If you want to be able
to create the inbound delivery with reference to a certain line item in
the PO, use transaction VL34.
If you still want to use transaction MIGO, there is the following
workaround:
- Create a purchase order without any confirmation control key
- Create a goods receipt (GR) in transaction MIGO with reference to this PO and post the GR to a non-HU-managed storage location
- Create a transfer posting with MIGO using movement type 311 to
transfer the goods from the non-HU-managed storage location to the
HU-managed storage location.
As the transfer posting is an additional step for the user, the whole
process could be automated using a partner storage location
(T001l-PARLG) for the GR which then triggers (through a modification)
the BAPI 'BAPI_GOODSMVT_CREATE' to create the transfer posting without
user interaction.
I hope to have satisfied you on the reason why it is now happening and
also I believe you can explain to business that it is a new behavior
necessary done from SAP side to avoid worse situations, we are aware of
potential dissatisfaction it might cause. SAP Support is always
available to clarify any issue.
Sorry for not having a more positive answer.
I hope it helps!
Leentje

Issue at the time of creation of transfer order for inbound delivery

Hello,
I am facing one issue at the time of creation of transfer order for inbound delivery.
If I create inbound delivery for purchase order with account assignment as 'M' (Ind. cust. w/o KD-CO), inbound delivery is not updated. Also document flow for inbounde delivery s not updated. I can create N number of transfer orders for on inbound delivery. Need help to resolve issue.
If I create inbound delivery for purchase order with account assignment other than 'M' (Ind. cust. w/o KD-CO), inbound delivery and document flow is updated.
Thanks and Regards,
Nikhil

Hi
In OMS2 t-code
for your material type and plant ,you have to mark value based and qunaity based updation mark
Regards
kailas Ugale

Post Goods Receipt for Inbound Delivery using WHSCON IDoc

Dear All
Currently I am working on a big project dealing with EDI connections to our logistics partner for the Export business. The entire message flow between Lindt and our partner should be via EDI. Our SAP release is (still) 4.6c.
We will create two kinds of despatch advice messages, one for inbound deliveries and one for outbound deliveries for customers.
I would appreciate your support in the following problem that I am facing with the inbound delivery scenario:
We create stock transport orders (purchase orders, POs) for the goods intended to be delivered into the plant at our partner
We create a delivery (type NL = replenishment delivery) for this POs
As soon as we post the goods issue we send the despatch advice (as EANCOM D96A DESADV message) to our partner.
At this point the delivery is basically completed, i.e. packing status (PS) and goods movement status (GM / GS) are equal to 'C' (= completed).
Our logistics partner uses the same EDI message to send us the goods receipts data, e.g.:
We dispatched 50 units of a product => QTY:50:12
The partner received indeed 50 units => QVR:50:66
Please note that we do not use the QVR segment for the quantity difference (between despatched and received quantity) but it contains the received units. This way we avoid negative values in the QVR segment.
When the logistics partner sends back the DESADV message containing the received quantities (QVR segment) we want to make
the goods receipts for the products in the original stock transport order and
upate the message flow in the delivery
My idea was to transform the incoming DESADV message into a WHSCON.DELVRY03 IDoc based on the documentation in: [Delivery Interface|http://help.sap.com/saphelp_crm40/helpdata/en/e2/654b15a9f411d184ec0000e81ddea0/content.htm]
In the delivery header control E1EDL18 I used QUALF = 'PGI' (Post goods issue).
I prepared an inbound WHSCON IDoc according to the documentation mentioned below. I managed to get some feedback from the Idoc processing implying that the system tried to do the goods receipt in the PO but failed.
To make a long story short here are my questions:
Can an inbound WHSCON IDoc used for doing both the goods receipt in the PO and the update of the message flow in the delivery?
Does anybody have an example on how to fill the WHSCON IDoc?
Or is my approach a cul-de-sac ?
Kind Regards
Uwe
PS: A related question can be found here: Goods Receipt in PO AND Message Flow Update in Inb. Delivery using WMMBXY

Hi Uwe,
Can an inbound WHSCON IDoc used for doing both the goods receipt in the PO and the update of the message flow in the delivery?
The binary answer would be no. You should use WMMBXY or MBGMCR instead.
But if we are doing goods receipt against Inbound delivery then answer is YES with additionally E1EDL18-QUALF = 'PIC' populated. But please remember no partial receipt is possible against Inbound Delivery.
We should populate E1EDL20-VBELN with our Inbound delivery number and line item info should go to E1EDL24.
I have done a similar interface recently where we are doing receipt against Inbound delivery. But our case was a bit complex because we had to support against Inbound delivery. So we had to go for a custom solution on top of IDOC_INPUT_DELVRY.
Hope this helps. Let me know if you have more questions.
Regards,
Rudra

Goods Receipt for Inbound Delivery before Transfer Order

Hello Experts,
Below is the normal process in case of GR via inbound delivery.
PO -> Inbound Delivery -> TO -> Confirm TO -> Post Goods Receipt in Delivery.
My client wants as per the normal Purchase Order cycle as below.
PO -> Inbound Delivery -> Post goods receipt in Delivery -> TO - > Confirm TO.
I have found some config for this as per below path.
Logistics - General -> Handling Unit Management -> Basics -> Delivery -> Define Sequence of Transfer Order - Goods Receipt.
I have done these settings but still it is not working.
I have couple of questions here.
1. Are there some more settings required?
2. Why SAP has designed this process in such a way for inbound delivery.
Thanks in advance for your help.
Navin

Hi,
I am working with non HU managed storage location. Can I still use this settings & process for inbound delivery?
I am stuck with one more question. SAP is not allowing me to create Inbound delivery for QM active materials.
The message it is saying is ....
Material CH-1440 1000 cannot be used in inbound delivery because QM is active
Message no. L9528
Diagnosis
QM is active for material CH-1440 in plant 1000. As a result, the material cannot be used in an inbound delivery item because the item is relevant for picking and because WM is active for the item.
This process is not supported in the current release.
Procedure
Execute the putaway using a goods receipt posting with subsequent
putaway in the Warehouse Management system.
Can you please help me with this one also?

Creation of Transfer Order for Inbound Delivery

Hi,
I am using L_TO_CREATE_DN for creation of a TO for Inbound Delivery.
I am getting this message."""Item 180000166 000010 does not exist or is not relevant for picking"""
The delivery is having Ware House number so i think it is relevent for picking... It is having an item 10 also. I dont know why this message is coming.
Can anyone please let me know how to get rid of this error and create a TO for the inbound delivery.
Regards
Rakesh

Hi Rakesh,
Pad the delivery number with a 0 in front and check.
like, instead of 180000166, pass 0180000166.
Regards,
Ravi

Idoc - for inbound delivery order confirmation

Hi,
Can some body give me the idoc for Inbound SO Delivery Order Confirmation and if any BAPI method is there to create Delivery order confirmation.
With Regards
Vasu

Hi Vasu,
Below is the link to find out the IDOC name for ur Inbound IDOC scnario
http://help.sap.com/bp_bpmv130/Documentation/K17_BPP_EN_US.doc
Hope this willl help you.
Reward if helpful.

Goods Receipt for Inbound Delivery through MIGO

Hi All,
Can anyone pl. explain me in steps the process of GR for Inbound Delivery from MIGO transaction.
Also I need the process of reversing this goods receipt done.
For certain inbound deliveries a dump occurs in the program SAPLIE01 in 'EQUIPMENT_ADAPT_BUSVIEWS' fn module.
I need to analyse the reason for the dump. Here is the extract from the dump
<b>IF WA_EQUI IS INITIAL
keine Equidaten vorhanden => EXCEPTION
---> RAISE ERR_ADAPT_BUSVIEWS . ENDIF. </b>
Advance Thanks

Hi Sanjay and Srikanth,
Thank you for the correction. I was just wondering over this number.
Sanjay, regd the release level, it is 0017 for SAP_APPL.
In brief, when GR is done for an inbound delivery, a fn moudle equipment_adapt_busviews is called, in which if the equipment data of the material (wa_equi) is initial, it gives dump.
1. This fn module is called 3 or 4 times while the posting is done through MIGO
2. In the 4th call, the parameter wa_equi is initial - which gives the dump.
3. While debugging, when I reach this point,if I restart the debugging, I find that the posting is completed !!!! (so something happening after posting of GR gives the dump)
4. I have to reverse this GR for replicating the same again.
Any further clues !!
Regards
Aadarsh

Partner profile for INBOUND IDOC

Dear experts,
Need your help to define partner profile for inbound idoc to R/3 system. There is a third party (Non SAP) based application from which idocs need to be sent to the R/3 system. There is no need to send an outbound idoc from the R/3 system. Can some one please suggest what are the steps to be taken to b configure the partner profile in the R/3 system for the inbound idoc?
Thanks,
Priyanka

Hi
This is not the right location to post this question.
You got to post this query in Data transfers section of SDN ABAP Development forums
Now regarding your question,
You need to create a Logical System with the help of the transaction SALE.
Assign the created LS to the client with the help of same transaction
Go to WE20 and create the partner with the same Logical System name
Now..as you are recieving the Inbound Idoc from external Non-SAP System, you need to maintain the message type in the Inbound Parameters by clicking on ADD Icon over there.
Before doing the above step, you got to create the connection between SAP and Non-SAP System.
Use transaction SM59 to do this. Type of connection would be R/3 I guess
Thanks
Hope it helps.

Function Module / BAPI for Inbound Delivery from Purchase Order

Hi,
I need to create an inbound delivery from Purchase Order items and am looking out for some Function Module or BAPI for the same.
The requirement is that i should be able to specify selected line items from PO for delivery.
I tried the BDC method for VL31N , but the particular item selection is problem, since by default it shows all the items of PO and i want only selected items.
Do reply.
Thanks in advance.

check these and their documentations.
BAPI_INB_DELIVERY_CHANGE Change inbound delivery
BAPI_INB_DELIVERY_CONFIRM_DEC BAPI for inbound delivery verification from a decentralized system
BAPI_INB_DELIVERY_SAVEREPLICA BAPI Function Module for Replication of Inbound Deliveries
Regards
Prabhu

Standard IDoc Type for Inbound NonPO Vendor Invoices - FB60

What should be the perfect standard IDoc Type for Inbound NonPO Vendor Invoice posting. Tcode FB60.
I found IDoc Type FIDCCP02 but the Function Module 'IDOC_INPUT_FIDCC2' for FIDCCP02 is not released.
In the same way many other standard function modules like - IDOC_INPUT_ACLPAY, IDOC_INPUT_FIDCCH, IDOC_INPUT_ACC_INVOICE_RECEIPT and few more are not released.
My question : If at all I have to use standard IDoc Type, Message type and Function module (Released) for Inbound NonPO Vendor Invoices, then what should be the solution from SAP ?
Thanks,
Veeru.

Hi,
IDOC_INPUT_FIDCC2 for FIDCCP02 works for us in ECC6.0
If you want Automatic tax calculation functionality using FIDCCP02.. then FIDCC2 is not correct message type for you. In that case you should probably go for :
Msg: INVOIC
Basic type: INVOIC02
FM: IDOC_INPUT_INVOIC_FI
Process code: INVF
Thanks,
Kumar

IP_MESSAGE_PARAMETER for inbound

Similar Messages

Maybe you are looking for