Partner in inbound delivery

Hi,
I'm creating an inbound delivery with trx VL31N, I clicked on header button, then I clicked the Partner tab
and if I click on Propose alternatives button the system prompts *There are no alternatives available for Vendor
X*.
I want the system proposes automatically the partner number when I click on Propose alternatives button
Regards

Have you maintained these settings?
SPROLOGISTICS EXECUTIONSHIPPINGBASIC SHIPPING FUNCTIONSPARTNERS--SET UP PARTNER DETERMINATION FOR DELIVERIES
Here, select the procedure for inbound deliveries, and add your partner.
Then maintain the partner number in vendor master data.i.e. this partner needs to be added as a partner function in vendor master also.

Similar Messages

User exit to change partner for inbound delivery creation

Hello,
I have a requirement to change the partner number for
the inbound delivery creation.
I only see the USEREXIT_MOVE_FIELD_TO_LIKP but I am not sure if this is
the right user exit for this requirement.
Is there the user exit for modifying partner in the inbound delivery?
Thanks in advance,

HI
There is a program with which you can find the available exits as per your requirement. You have to execute the same and give your transaction code. Hope this helps...
*& Report ZFINDUSEREXIT
report zfinduserexit.
tables : tstc, tadir, modsapt, modact, trdir, tfdir, enlfdir.
tables : tstct.
data : jtab like tadir occurs 0 with header line.
data : field1(30).
data : v_devclass like tadir-devclass.
parameters : p_tcode like tstc-tcode obligatory.
select single * from tstc where tcode eq p_tcode.
if sy-subrc eq 0.
select single * from tadir where pgmid = 'R3TR'
and object = 'PROG'
and obj_name = tstc-pgmna.
move : tadir-devclass to v_devclass.
if sy-subrc ne 0.
select single * from trdir where name = tstc-pgmna.
if trdir-subc eq 'F'.
select single * from tfdir where pname = tstc-pgmna.
select single * from enlfdir where funcname =
tfdir-funcname.
select single * from tadir where pgmid = 'R3TR'
and object = 'FUGR'
and obj_name eq enlfdir-area.
move : tadir-devclass to v_devclass.
endif.
endif.
select * from tadir into table jtab
where pgmid = 'R3TR'
and object = 'SMOD'
and devclass = v_devclass.
select single * from tstct where sprsl eq sy-langu and
tcode eq p_tcode.
format color col_positive intensified off.
write:/(19) 'Transaction Code - ',
20(20) p_tcode,
45(50) tstct-ttext.
skip.
if not jtab[] is initial.
write:/(95) sy-uline.
format color col_heading intensified on.
write:/1 sy-vline,
2 'Exit Name',
21 sy-vline ,
22 'Description',
95 sy-vline.
write:/(95) sy-uline.
loop at jtab.
select single * from modsapt
where sprsl = sy-langu and
name = jtab-obj_name.
format color col_normal intensified off.
write:/1 sy-vline,
2 jtab-obj_name hotspot on,
21 sy-vline ,
22 modsapt-modtext,
95 sy-vline.
endloop.
write:/(95) sy-uline.
describe table jtab.
skip.
format color col_total intensified on.
write:/ 'No of Exits:' , sy-tfill.
else.
format color col_negative intensified on.
write:/(95) 'No User Exit exists'.
endif.
else.
format color col_negative intensified on.
write:/(95) 'Transaction Code Does Not Exist'.
endif.
at line-selection.
get cursor field field1.
check field1(4) eq 'JTAB'.
set parameter id 'MON' field sy-lisel+1(10).
Do reward if useful...
Regards
Dinesh

Inbound delivery partner profile question

Hello,
Based on the help documentation, i have setup a distribution model between ECC and EWM system.
After executing this transaction /n/SPE/OL19, my distribution model is properly generated and I am able to send Idoc from ECC system. However on on EWM system, I am getting an error related to message type DELINF is not found in inbound partner profile.
I searched in WE80 and I do not see this message type in SCM system, can someone kindly suggest if the below mentioned message types used in ECC are right and on the SCM side I have only one message type which is SYNCH.
Following message type in ECC
DELINF
DELORD
/SPE/LIKP.DELIVERYCHANGE
/SPE/LIKP.REQUESTCHANGES
/SPE/LIKP.SAVEREPLICA
BUS2015.DELIVERYCHANGE
BUS2015.SAVEREPLICA
BUS6050.EXECUTE
Following message type in SCM
SYNCH.
Am i missing some setting which is preventing from idoc to be posted in EWM to generate inbound delivery request.
If someone could suggest what are the message types should exist for inbound in EWM side or DELINF needs to be added in EWM system.
Appreciate your suggestions/comments.
Thanks
Bhaskar

No..you can not know it.There is no log.

Partner not copied from Purchase order to inbound delivery

Hello,
When I create an inbound delivery (VL31N) from a purchase order (ME23N), the partner FM is not copied (whereas partner FO is copied).
Does someone know how to solve this issue? (customizing or user exit..).
thanks

Hi,
Is there any specific Copy Control Routine or User Exit that copy Partners from a Purchase Order Header to Delivery Header?
Please provide me the Routine Name/Number or User Exit Name.
Thanks,
RV

Partner Function for STO and relevant inbound delivery

Dear Expert,
i did the partner configuration for Vendor and STO with partner VN-vendor DP-delivery plant.
When i create the STO vendor UP07, both of VN and DP are UP07, but when i create the STO for UP07, no partner data come out for the PO, the partner data didn't copy out from vendor master.For standard PO not STO, the partner data are copied from vendor master automatically. Any advice any further more setting need to do?
I manually input the partner data for the STO, then i try to create inbound delivery, following incompleteness came out"Vendor : Account Number of Vendor or Creditor Missing",user need to manually input the partner number for LF-vendor.But when i check the partner setting for inbound delivery, LF is copied out from VN.Any more setting need to do to make sure the partner number of LF is auto copied from PO data.
Look forward to your reply,
Thank you and regards

Hello,
PLease check the vendor data created as a plant. Go to Vendor master and in purchasing view select extras -> additional Purchasing data-> in the plant assignment enter the Plant number. This will pull in the vendor details into the inbound delivery.
Thanks!!

Copy partner from PO to inbound delivery

Hi! I have create new partner function called FA and am able to maintain with other partner functions such as CR for the vendor master. When I create the PO, these partners are copied to the PO. However, when I create an inbound delivery for the PO, only CR is copied over but not FA. I have checked the configuration but couldn't find anything wrong with the set up. Does anyone know whether standard SAP can be configured to copy all the partners over? Have I missed out a config?
Thanks
Dilip

I'm also having the same problem but after looking into the source code it is not possible to copy another partner different than LF (Vendor) to the inbound delivery with customization. A user exit or a BADI will be necessary.
I have an explanation if you're interested in technical details:
When an inbound delivery is created, the partners are determined in
FM SHP_COPY_PARTNER_FROM_PREC_DOC
FORM FILL_VBPA_SINGLE.
There you'll see that the code only handles the following partners WE(SH)Ship to party, AG(SP) Sold to party, LF(VN) Vendor and SP(CR) forwarding agent.
Previous to this, program RM06EANL (called by txn VL34), field LIFNR is the only field filled in structure XKOMDLGN. Field SPDNR is not filled at all, in this way, there is no chance that even forwarding agent gets copied in the function described in the previous paragraph.
pd: The system gives all parameters for creating an inbound delivery into structure XKOMDLGN and executing FM RV_DELIVERY_CREATE.
Regards.
[ivo]

New partner function in the inbound delivery

Hi
I want to have the partner fuction: CR (forwarding agent) in the inbound delvery. It has to be copied from the purchase order.
I added the partner type to the partner determination procedure for the vendor, the purchasing document and the in the inbound the delivery.
Then I added a forwarding agent to the master data of the vendor. When I created a purchase order the forwarding agent was nicely copied to the purchase order. But when I created the inbound delivery from the purchase order it was not copied over.
By the way I checked also the partner procedure which is linked to the sales order which is used as the source for the copy control of the inbound delivery. This has the forwarding agent in it as well.
Anybody an idea how to proceed?
Thanks,
Rudy

There might be an entry of Partner function missed in SPRO.
SPRO>Logistics Execution>Shipping>Partners>Master Data-->Set Up Partner Determination for Deliveries.
If forwarding agent entry missed ,maintain the entry.Then partner entry will automatically copy to delivery .

Inbound Idoc with T-code: BORGR ( Inbound delivery create) EDI cannection

Dear all,
Kindly help me to create inbound delivery with BORGR transaction.
Here the we have to create the inbound delivery in the system with the help of vendor number and material without using Scheduling agreement number in BORGR
Please suggest the processing code and the function module required for the BORGR document posting.
I have done the following steps u2026but not able to post the dummy idoc through WE19 .
1. Use standard message Type DESADV (T code: WE81).
2. Use standard IDOC type DELVRY05 (T code: WE30).
3. Assign message type to IDOC Type ( Tcode: WE82).Message Type:-DESADV, Basic Type:-DELVRY05,Release 700
4. Use standard assignment of process code DELS with the message type DESADV ( Tcode: WE42)
5. Inbound Function Module : IDOC_INPUT_DESADV1 ( T code : WE57)
6. Define Port type File (Tcode: WE21) Port u2013 EDI_ASN Inbound Delivery.
7. Define Partner Profile (Tcode: WE20) Inbound Parameters.
8. Enhancement can be done in inbound IDOC as per the business requirement. Business has confirmed Field name wise Inbound IDOC data which will be received from vendor and all fields are available in the standard IDOC type DELVRY05.
Please help if anything more required for posting dummy idoc .
Thanks and regards,
koshti

Hi Dick,
just one additional hint as we had recently such problems :
It my happen that DESADV creates an inb.del w/o packing the HUs (idoc status is 'yellow' instead of 'red'). To avoid this OSS #912470 is the solution.
Kind Regards
Kay

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

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

Inbound Delivery (DESADV): How to transmit SLED/BBD and Manufacture Date?

Hello
We have another challenging task to solve. Here is the scenario (SAP Release ERP 6.0):
One Lindt company (supplier) sends an outbound DESADV IDoc to another Lindt company (Purchaser). Here the inbound DESADV should create an inbound delivery. Finally, the inbound delivery is replicated to the external WHS partner who does the Goods Receipt against this inbound delivery.
The outbound DESADV contains all logistical data including SSCC. In particular, the batches have a manufacture date (LIPS-HSDAT) and a SLED/BBD (LIPS-VFDAT).
SLED = Shelf Life Expiration Date
BBD = Best-Before Date
In the outbound DESADV the SLED/BBD is mapped by default into segment E1EDL24/VFDAT. For the manufacture date we implemented an user-exit.
How does the inbound delivery look like? The batch number appears as "Vendor batch". The SLED/BBD does NOT show up even though the inbound DESADV contains the date in E1EDL24/VFDAT. This inbound DESADV did NOT contain any controlling segment E1EDL19. Adding this segment (QUALF = 'VDT' = Shelf Life Expiration or Best-Before Date) had no effect.
Here is my assumption why the SLED/BBD does not show up in the inbound delivery created by the inbound DESADV:
Because we do not yet have the "real" batch (just the "Vendor batch") the system ignores any SLED/BBD. As soon as the external WHS partner sends the GoodsReceipt message (as inbound WHSCON ) the inbound delivery is updated with the "real" batch as well as the SLED/BBD.
QUESTIONS:
(1) Why does the SLED/BBD not show up in the inbound delivery created by an inbound DESADV?
(2) Do we need another user-exit to map the manufacture date into the inbound delivery?
Once again thank you for sharing your time and expertise with us.
Regards
   Uwe

Apply SAP Note
Note 1576788 - Transfer of exp. date
(IDOC_INPUT_DESADV1) to inb. delivery
Here are the correction instructions for your reference:
=========================================
FORM DESADV_IDOC_PARSE
Delta001Context Block
        IF NOT t_dlgn-vbelv IS INITIAL.
          t_dlgn-posnv = s_dl24-posex.
        ENDIF.
Delete Block
        mv s_dl24-brgew t_dlgn-brgew.
Insert Block
        mv s_dl24-vfdat t_dlgn-vfdat.                         "n_1576788
        mv s_dl24-brgew t_dlgn-brgew.
Have fun!
- Joemil

Idoc WHSORD for inbound delivery

Hello,
We want to send inbound deliveries to an external WMS (not SAP WM) by using an output in the inbound delivery.
I tried to use idoc WHSORD (basic type DELVRY01) as for Outbound delivery.
I obtained an error message when processing the output : "The message record of the message control contains a partner role with a partner type LS that cannot be used here. Only the 'KU' and 'LI' partner types are allowed."
Configuration done (same as outbound delivery) :
Output : Medium "6 EDI" / Partner type LS
Partner profile (WE20) : Partner type LS / Partner role LS /Message control : Application E1 / process code DELV.
Finally, I've been able to generate one idoc from the inbound delivery by using medium "A ALE" and partner type LI "vendor". But I need to do it for a LS partner as we do want to maintain partner profile for each vendor.
Is this due to some missing configuration linked to application E1 (i.e allow partner type LS ?) ?
How can we solve this ?
Thanks a lot for your help

Hi zhiqiang,
In order to test inbound idocs, you can use transaction WE19 to create manually idocs.
As pre-requisite, you have to maintain ALE configuration : port and partner profiles.
Then in WE19, you can create an idoc from message type : fill all the fields you need to and delete unuse segments. Then click on "Standard inbound" and your idoc will be received in your SAP system.
Check the status in transaction BD87.
To fill correctlly your idoc :
1. You can find documentation on message type in transaction WE60 (when you go in this transaction, check the documention is "active" => Goto => user settings => "Documentation output" and "field value output" must be ticked)
2. In WE19, for some fields, if you press F4, you will get list of possible values.
Good luck,
JP

Inbound IDOC to post goods receipt with inbound delivery as reference

Kindly let me know the message and IDOC type for
Inbound IDOC to POST GOODS RECEIPT with inbound delivery as reference
I tried using WMMBXY but it didn;t work.
Pls let me know asap.Your help is appreciated.
Thanks and Regards
Priti
Edited by: Priti Adukia on Feb 11, 2008 4:48 AM

Hi Nicole,
What I've to do is quite the same as the case. Outbound and Inbound are in the same SAP system. If I've good understanding, I must set partner profile as follows :
INBOUND - Parter LI with
                        Message DESADV
                        Operation code DELS
OUTBOUND - Partner KU
                        Message DESADV
                        Operation code ???
Please advise
Suchart

Inbound Delivery via Idoc with more than 1 line fails

Hi @ all,
i try to replicate inbound deliveries from an external system to SAP EWM using Idocs (SHP_IBDLV_SAVE_REPLICA02 with MessageType SHP_IBDLV_SAVE_REPLICA).
If there's only one position in inbound delivery it works, but if i try with two or more lines processing ends up with idoc-status 51 (WE02) and message 'Error inserting partner and location data at item level' (SLG1).
Any ideas to solve this problem?
kind regards

Hello Markus,
"i try to replicate inbound deliveries from an external system to SAP EWM using Idocs".
you are trying to send the information from non sap system?. Can you elaborate the scenario.
Is the case you are sending ASN information directly to eWM system.
Seems the process is more interesting. Can you please share details.
regards
Sastry

Automatic creation of TO's for Handling Unit Inbound Delivery -del type HID

Hi Guru's,
I would like to create the putaway TO's for a Handling Unit inbound delivery automatically (delivery type HID). This means at the moment of the creation of the Inbound Delivery. The packing is also automatically done by the customizing of the delivery type. Did somebody faced this requirement before?
Thx,
Carl

I found the solution:
Choose Customizing activity Define Output Types for Inbound Delivery, and define output type WMTA. Enter the following values in the detail view of output type WMTA under General Data:
Enter an existing Access sequence. Access sequence 0001 is predefined in the standard system.
Set the indicator Access to conditions.
Set the indicator Partner-indep. output.
Save your entries.
In the menu tree, choose the entry Processing Routines in the Customizing activity Define Output Types, and enter the following values:
Choose entry 8 (special function) for the indicator Transmission Medium.
Enter RLAUTA20 in the field Program.
Enter ENTRY in the field Form Routine.
Save your entries.
Choose the Customizing activity Maintain Output Determination Procedure.
Define a procedure and enter the output type WMTA in the control view of the procedure. The procedure E10001 is predefined in the standard system.
To define a suitable condition record for inbound deliveries,
choose Logistics -> Materials Management -> Purchasing -> Master Data ->
Messages -> Inbound Delivery -> Create from the SAP menu.
Enter the output type WMTA.
Enter output medium 8 (special function) for delivery type Inbound Delivery.
Select the desired Date/Time.
Select the desired Language.
Cheers,
Carl

Partner in inbound delivery

Similar Messages

Maybe you are looking for