Issue with Message Type Triggering during Inbound Delivery Creation

Hi Experts,
Hi Experts,
Currently we are facing issue with message type triggering during inbound delivery creation:
In NACE transaction for Inbound delivery we have 3 custom output types:
Pricing Procedure Used is standard one -> E10001
Z140 Inbound Delivery Create (This should get triggered when IB delivery is created)
Z141 Inbound Delivery Change (This should get triggered when IB Delivery is changed)
Z142 Inbound Delivery Delete(This should get triggered when IB Delivery is deleted).
At present if i check delivery in VL33 -> Extras -> Delivery Output
Both Z140 and Z141 are being triggered during IB delivery creation. While it should be only Z140.
Could you please suggest that are we missing any configuration in SPRO or we need to create any custom routine (requirement) to handle this?
Thanks

Hi,
There is no fine-tuned control for inbound delivery messages as for Purchase order. Hence I guess to meet your above requirement, you have to go for a custom solution similar to the PO fine tune control settings.
Thanks,

Similar Messages

Check amount of transition stock during inbound delivery creation

I want to move stock between plans, therefore I have the following steps:
1. Stock Transfer Order (STO), e.g. 500 pieces
2. Sending plant: MIGO (GI for STO) with MT 351 to post to transition stock, e.g. 100 pieces
3. Receiving plant: Inbound Delivery with reference to STO VL31N
4. process Inbound delivery in warehouse (SAP-WM)
The question is:
During step 3, when accessing VL31N the system proposes the full order quantity (e.g. 500 pc.)
I can change the amount to any amount I like, e.g 240 pieces.
How can I tell SAP, that Inbound delivery creation is only possible for the amount
which has been posted to stock in transition (100 pieces)
I want an error/warning message in case user wants to create Inbound delivery quantity higher than the amount that has been posted to transition stock.
Any ideas?

MIGO in sending Plant?
How it is possible? MIGO means, Goods receipt. This should be in Receiving plant.
Sending plant should do the PGI
MIRO in receiving plant
Billing in sending plant
Payment from Receiving palnt and clearing in sending plant
Correct me if i am wrong
Thanks

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

Dump during inbound delivery creation with VL34

Hi,
when I try to create a inbound delivery for a Purchase order item with account assignment Q (project stock) I get the following dump
Runtime Errors         SAPSQL_ARRAY_INSERT_DUPREC
Except.                CX_SY_OPEN_SQL_DB
Date and Time          28.07.2010 17:37:10
Short text
     The ABAP/4 Open SQL array insert results in duplicate database records.
What happened?
     Error in the ABAP Application Program
     The current ABAP program "SAPLV05I" had to be terminated because it has
     come across a statement that unfortunately cannot be executed.
Error analysis
     An exception occurred that is explained in detail below.
     The exception, which is assigned to class 'CX_SY_OPEN_SQL_DB', was not caught
      in
     procedure "SD_PARTNER_UPDATE" "(FUNCTION)", nor was it propagated by a RAISING
      clause.
     Since the caller of the procedure could not have anticipated that the
     exception would occur, the current program is terminated.
     The reason for the exception is:
     If you use an ABAP/4 Open SQL array insert to insert a record in
     the database and that record already exists with the same key,
     this results in a termination.
     (With an ABAP/4 Open SQL single record insert in the same error
     situation, processing does not terminate, but SY-SUBRC is set to 4.)
Missing RAISING Clause in Interface
     Program                                 SAPLV05I
     Include                                 LV05IU15
     Row                                     1
     Module type                             (FUNCTION)
     Module Name                             SD_PARTNER_UPDATE
Trigger Location of Exception
Program                                 SAPLV05I
    Include                                 LV05IU15
    Row                                     480
    Module type                             (FUNCTION)
    Module Name                             SD_PARTNER_UPDATE
When I try to create the inbound delivery with VL31N it works fine. I also tried a couple of BAPIs/FMs which gave me the same dump as VL34.
Thanks in advance!!
br
Walter

I also failed to find any OSS note relevant to this.
If you are not using any exits / BADI, there's no standard modification, you should contact SAP AG and their responsibility is to correct the error.
But it may happen that you are using your own logic (via user exit, BADI, standard modification), in this case you have to find out what causes the problem. If the error is becasue of your develoments, then you cannot ask SAP AG to correct the error, if the error is not caused by your developments then it's SAP AG's responsibility.
Please read OSS note 575667 which says that:
The most common cause for this runtime error is an incorrect logic in USEREXIT_SAVE_DOCUMENT_PREPARE or USEREXIT_SAVE_DOCUMENT in include MV50AFZ1.
For this, read also notes 178328 and 415716.
Edited by: Csaba Szommer on Nov 3, 2010 8:49 AM
Edited by: Csaba Szommer on Nov 3, 2010 8:50 AM

Error during inbound delivery creation for some times not always

Hi,
I'm getting the following error when i'm trying to create an inbound delivery for PO.
                                                                                Diagnosis
The system attempted to find the reference movement type for
     the Warehouse Management system. A corresponding entry is
     missing in table 156S with the argument 101/X/X/ / /X/.
     The argument consists of:
     o   IM movement type
     o   Indicator: Value update
     o   Indicator: Quantity update
     o   Special stock
     o   Movement indicator
     o   Access indicator
     o   Indicator: Consumption
Can someone help me to resolve it? as it is not happening always
Appreciates everyone time and help.
Thanks and regards,
Siva

Hi,
Thanks for the response and yes i did maintained IM/WM mvt types for 101 in both places.
If the movement type is maintained well why SAP says it is not?
SPRO > LE > WM > Interfaces > IM > Define Movement Types - "Assign WM Movement Type References to IM Movement Types'
Related tabel is V_156S_WM
If you check your configuration you will see that there are many entries with 101, and there are several other parameters...
First you should check what you are doing in IM, what parameters that mvt has (qty, value update, special stock, etc) > after that you should check whether it is maintained well in WM customizing - see steps in my previous email.
Regards,
Csaba

Error during Inbound Delivery creation by Idoc DELVRY05

Hi,
We are trying to consolidate ASNs and creating an inbound delivery for the same. Thus we have more than one PO information in the idoc.
It processes fine and creates an inbound delivery if all the line item nos are different.
But the issue is, when there are articles which have the same line item no. even if the articles are different and they are on different POs. It gives the following errors.
1) "Delivery item cannot be exactly determined
Message no. HUFUNCTIONS313"
I tried to debug the above error and found that while packing it looks to the lips-vbeln/posnr & not the PO nr./PO item.
I am not sure if this could be handled by some config. Please advice.
2) "V51VP - item was not found - process cancelled
Message no. HUGENERAL056"
Any hints or comments on the above would be appreciated.
Thanks & Regards,
Akshay

Hi Raghavendra,
It has been a long time. But, as far as I can remember we had made coding adjustments in the customer-exit EXIT_SAPLV55K_004, include ZXTRKU12 to fetch the correct item and fill the idoc segment fields.
This resolved the issue.
Best Regards,
Akshay

Outbound delivery with Inbound IDOC DELVRY06 with Message type SHPCON

Hi Friends
I am trying to pack outbound delivery with Inbound IDOC DELVRY06 with Message type SHPCON.
But IDOC has error Specification of destination HU missing.
Could you please help us to resolve the issue to Pack the outbound delivery with the IDOC.
Thanks
SR

HI Ian Kehoe
Sorry for delay in reply
Thanks you very much
I solved that problem .
Could you please advice test data for IDOC DELVRY06 packing hierarchy (multi level packing) to pack SAP outbound delivery.
Thanks
Ravi

Issue: "No Authorization to send Idocs with message type Orders" - IDX5

Hi All,
I am working on a File to IDoc(Orders.Orders05) scenario. The sender is PI Server and the receiver is the SAP ISR system. A technical system has been created in PI SLD for the ISR system and a Business system is added to that. The logical system created in ISR system using Tcode BD54 is added to the business system in PI. A new RFC destination is created in PI system to connect to the ISR system.
On the ISR system Partner profile is created using TCode we20 with the same logical system name already created using Tcode BD54.
When sxi_monitor is executed on the PI system, It shows checked flag on the Inbound side and Red flag on the Outbound side. And when idx5 is executed, it shows the new Idoc number and when it is double clicked, it shows the Status Text as
"No Authorization to send IDocs with message type Orders".
All authorizations have been provided on the Sender side.
Please let me know if any authorization need to be provided on the ISR system or Is this an error on any settings.
Thanks in Advance.
Stalin S.

Hi,
Check this Thread which deals with the Authorization Issue
RFC Adapter
And also check this how to check whether u have sufficient authorization to send the Idocs or not
To test the Authorization check
Double click the RFC Destination that u have created in XI towards R/3 in SM59
Select UtilitiesTestAuthorization test
By this you can come to know whether your user is having the propper authorization or not
REgards
Seshagiri

Inbound Idoc Type / Message Type / Process Code for Delivery via Tcode VL0N

Guys,
I need to to Idoc Type and Message type for to create Delivery ( Tcode VL01N ) for a sales order.
I tried Idoc Type DELVRY03 and Message Type DESADV, but this is for Purchase Order ( VL31N ).
Kindly help me.
Regards
Srikanth M

Guys
I could not use above message type/idoc type as they are not released in SAP.
So i am again back to where i have come from. I am trying to use DESADV01 and Mess Type DESADV.
Regards
Srikanth M

Inspection lot problem during inbound delivery

Hi,
I am facing following issue during inbound delivery.
I have activated inspection type 01 in material master for a packing material. Created a PO for the material through ME21N. PO created. Now I am creating inbound delivery through VL31N with reference to PO no and vendor. When I am entering the storage location I am getting the below error..
Upon investigating the issue system is creating the inspection lot
But inspection lot is not showing in QA32/QA02.
checked various threads but not of much use. I am not able to proceed further.
Kindly help.
Thanks
Kumar

Hi Kumar,
Plz check in PO history, if GRN is done. If yes then plz check in GRN quantity tab, if inspection lot is created. IN QA32, in dynamic selection enter the inspection lot and click on 'select all inspection lot' and check if it is created in system. If lot is prepared then as per the error message someone from your department must be processing it.
In Your inbound delivery screen check your tab status overview if it is A: GR not made or C: GR completed.
Also during inbound delivery storage location is picked up in inbound delivery automatically from PO you need not to enter it again.
Plz check else post screen shot of PO history and QA32.
Regards,
Priti.

Error message while creating an inbound delivery to generate an idoc

hi,
i am getting the following error message while creating an inbound delivery(vl31n) where the message has to be sent ot decentralized warehouse mangament using idoc .
." No recipient could be determined for object BUS2015 method SAVEREPLICA"
Procedure for System Administration
The system attempts to determine a recipient for object BUS2015 method SAVEREPLICA using the filter object types WHSE_NO. The system cannot determine a recipient. Define a filter object type WHSE_NO with a valid filter value for recipient determination for object BUS2015 method SAVEREPLICA.
need help
regards
leo

Inbound delivery is not part of Sales and Distribution. You might want to move your post to either the Logistics Materials Management (MM) forum or the Workflow forum.
Also sometimes search for OSS notes by the message class and number helps.

Creation of IDOC with message type INVOIC01

Hi All,
I am trying to create a new IDOC with message type INVOIC01.
When I see transaction WE81, I observe that the required message type INVOIC is available. Also in WE82 the basic types INVOIC01, INVOIC02 and INV_ID01 are attached to the message type INVOIC.
However, while trying to create an IDOC in WE19 using a message type, I get options to create against INVOIC02 or INV_ID01. The basic type INVOIC01 is not getting populated because of which all the IDOC that I create are of basic type INVOIC02.
The client wants me to create IDOCs with basic type INVOIC01.
Can anyone please help?
Thanks in advance.
regards
Nagarajan

Hi Nagaraj!
I've looked at the documentation and did not find information, which would help me. Should I use in my case z-segment to put extra lines or there is some qualifier in segment E1EDP02 (Document Item Reference Data), which triggers to another referencing (not PO or delivery note)?
Thank You,
Natalija

Error during Inbound Delivery

Dear Expert,
I have problem when we want to create Inbound Delivery/VL31N. Error message is "No deliveries created (check log)". The long text of log is :
Diagnosis
                                                                                There is no item category available in item category
    determination in the delivery (table T184L) for the following
    entries: EL LEIS V
                                                                                System Response
                                                                                The system does not allow further processing of this item.
                                                                                Procedure
                                                                                Specify the appropriate item category for the above mentioned
    entries or inform your system administrator.
I confuse with this message, because i don't know the relation of table T184L with my case. the another Inbound delivery is working fine, only 1 inbound delivery that getting this error. Any solution and advice. Thx a lot
BR,
Affan

hi
go to t code 0184 and here against the entry EL LEIS V maintain item cat as norm and same manintain in ur material master
regards
kunal
award if helpful

Posting Data Issue with IDOC Type : COND_A03

Friends,
I'm posting the data from Middleware(Message Broker) to SAP using the IDOC Type : COND_A03 with Message Type : COND_A.
For this IDOC,I'm populating the below Segment's data.
Segement :E1KOMG:
Fields:
KVEWE,KOTABNR,KAPPL ,KSCHL,VAKEY ,KONDA,MATNR .
Segement :E1KONH:
Fields:
KNUMH,DATAB,DATBI
Segement :E1KONP:
Fields:
KSCHL,STFKZ,KSTBM,KSTBW,KRECH ,KBETR,KONWA,KPEIN,KUMZA,KUMNE,MXWRT,GKWRT,ZAEHK_IND ,KBRUE,VALTG,
VALDT,ANZAUF,MIKBAS,MXKBAS,KOMXWRT,KLF_STG,KLF_KAL
Problem: In SAP, IDOC's are processing successfully with status 53 and updating the tables : KONH,KONP successfully.
But Table A957 which is passing against KOTABNR field is not pupulating with the Materials passing.
Can anyone please guide me why the Materials are not populating in the table : A957.
Regards,
Sreeram

Hi,
I guess there might be some issue with VAKEY population.
All the key fields in A957 should be concated properly while populating VAKEY. (Leading zeros must be prefixed to the material)
Regards,
Ganga

Error : No authorization to send IDocs with message type MATMAS

Hi All,
My scenario is FILE-XI-IDOC.
I am getting chequered flag in SXMB_MONI,but in that under outbound status I am getting red flag.
When I check in SM58 I am getting message as "No authorization to send IDocs with message type MATMAS".
Do I need to give any authorizations on XI side or on R/3 side?
If so, what is the authorization required?
I could not find the note :837595.

<i>You use the IDoc Adapter in the Exchange Infrastructure and you try to use the IDocs to receive or send data. For these IDocs, an attempt is made to load the IDoc metadata from an R/3 reference system with an SAP NetWeaver Release lower than 6.20.
This occurs either at runtime, whereby the relevant messages run into 'System error' status, or when you use transaction IDX2 during manual loading of the metadata. In this case, the reference ystem is called by RFC and the logon user of the RFC destination does not have the necessary authorizations for determining the metadata.
Solution
In transaction PFCG, extend the role of the logon user by adding the following authorizations:
Authorization object S_RFC
      Field name RFC_TYPE value FUGR
      Field name RFC_NAME value EDIMEXT, SDTX
      Field name ACTVT    value 16
Authorization object S_IDOCDEFT
      Field name ACTVT value 03
      Field name EDI_CIM value ' '
      Field name EDI_DOC value TXTRAW01
      Field name EDI_TCD value WE30
Authorization object S_CTS_ADMI
      Field name CTS_ADMFCT value TABL
Authorization object S_TABU_DIS
      Field name ACTVT      value 03
      Field name DICBERCLS value</i>
from the note mentioned above.
Regards
Bhavesh

Issue with Message Type Triggering during Inbound Delivery Creation

Similar Messages

Maybe you are looking for