Issue in CIF of delivery from R/3 to APO

Hi Experts,
I am facing an issue while transferring sales order from R/3 to APO.
When any sales order is created in ECC, it is transferred to APO.
My requirement is to restricted specific sales order type and respective deliveries from going to APO.
I have written my logic in exit CIFSLS03 in FM EXIT_SAPLCSLS_002.
But this code is working fine for sales order but not for respective deliveries.
Here is screen shot of my logic.
Please look into this and help me to overcome this situation.

Let me know if I am missing any configuration settings.

Similar Messages

CIF Transportation Lanes from R/3 to APO

Currently, we are creating transportation lanes in APO via BAPI calls from R/3.     We have been lead to believe that transportation lanes can be CIF'ed over to APO.
We are only executing GATP in APO.    We currently do not use DP, SNP, PP/DS, TP/VS, etc.
I have seen several OSS notes that allows additional fields to be added to the CIF screen (tx = CFM1) but these fields would be more for filtering data.
We just upgraded our APO system from 3.1 to 5.0.    The CFM1 screen stayed the same in SCM 5.0.     Could it be possible that we don't have an updated CFM1 screen with the option of CIF'ing transportaion lanes??
Any information on this would be appreciated.
Thank you.

Hi,
As you in your requirement only describe gATP, I am a bit unsure why you need the transportation lanes? There are some different ways to handle the scheduling part in gATP and you should look into this before making any decisions regarding this. Normally you can ake use of transportation zones in APO to give a goiod level of detail vs maintenance for transportation lead time scheduling. gATP also allows for usage of condition technique and, as of 5.0, a new general procudure process scheduling from which I have no experience. I can see benefitds with transportation zones and scheduling, and in this scenario it would be possoble to make use of some data (customers) that can be CIFed and grouped. But as said there are several options, please specify your requirments to see if I can support further.
Fredrik

Not able to cif transiton data from APO to R/3 and from R/3 to APO

Hi:
I have made all relevant setting as per required for configuration of cif architecture in R/3 and in APO.I am able to cif master data from R/3 to APO but when I am transferring Planned Order from APO to R/3 or Sales Order from R/3 to APO I am not able to tranfer it .Even I am not getting any blocked q.
Even I am able to access remote login to both system by RFC Connection.
Please let me know how to debug it and solve it.
With Regards
Ashish Gupta

Hi Ashish,
Please try ciffing only one transactional data and then check on the application logs using t-code CFM1 or SLG1 in R/3 and /n/sapapo/c3 & slg1 in APO. This will give you idea where is going on wrong.
Kindly confirm
Regards
R. Senthil Mareeswaran.

Goods Issue in SD delivery (from vendor consignment stock)

Hi, all.
I'm trying to make a goods issue in SD delivery from a vendor consignment stock (movement 601K), but the system gives me an error message M7071 - I have to enter a vendor at item level, but where? And if I have a stock determination strategie, why the system needs the vendor, if I have stock K available for a vendor?
Please advise.
Thanks,
HA

Hi Helena Maria,
I think you have made some mistake in the movement types in the consignment processes..
just go through this and its easy to remember...
<b>Please reward if this is useful for you..</b>
1. Consignment fill up:
Sales document type is KB
Item category KBN
schedule line category 1
In this step, you are not invoicing the customer. document flow is sales order -
delivery item category. It will not be relevant for billing and pricing because you are not charging money for these goods in this step.
In schedule line category, you will set movement type 631 & set for availability check and TOR.
2. Consignment Issue.
Once the customer informed you that he used all the goods or partial goods then you will create consignment issue for used goods.
Sales document: KE
Item category: KEN
schedule line category: C0 or C1
Here you are invoicing the customer(because he used the goods). you are assigning the delivery document and billing document to the sales document.
In item category, you are setting relevant for billing, pricing, special stock.
In schedule line category, your setting is 633 movement type, relevant for availability check & TOR.
3. Consignment Return:
Customer found that some goods are damaged or he not able to sold the goods he want to send it back. that you are creating this document.
Sales document type: KR
Item category: KRN
You will assign delivery document and billing to sales document. you will create return order, return delivery, return billing.
Your setting item category relevant for billing, returns, pricing, special stock.
Your setting schedule line item category: 634 movement type, NO availability NO TOR.
4. Consignment Pick up:
Even if you create the consignment return the goods are not come to direct to your plant. For that you need to create consignment pick up. here the owner ship is not changing so you do not need to create billing.
Assign return delivery to sales document type.
Sales document: KA
Item category: KAN

Issue Updating Base Sales Order From A Delivery

As a Delivery doc is added that was created from a Sales Order, I would like to be able to update certain unclosed information in the base Sales Order document. Two of the fields are user fields, which don't present an issue. I can make the updates accordingly through the SDK. The issue I'm having presents itself when I attempt to update the TransportationCode (ORDR.TranspCode) field in the base sales order, which is a field on the logistics tab. I can make the update through the SBO interface version 2005 fine, but when I make the update through the SDK version 2005 use VB.NET 1.1 I get the following error:
[ORDR.DocRate] , 'Field cannot be updated (ODBC -1029)'.
It's strange because I'm not making any updates to the DocRate field. This issue arose after an upgrade from 6.5 to 2005. Worked fine in 6.5. The DocRate (exchange rate) field is not used in documents entered in local currency as far as I know.
Any ideas?
Private Sub UpdateOrderFromDelivery(ByVal DS As DataSet)
        Dim oORDR As SAPbobsCOM.Documents
        Dim oDEL As SAPbobsCOM.Documents
        Dim RetVal As Long
        Dim DT As New DataTable
        Dim DR As DataRow
        Dim OrdrTrackNum As String
        Dim AL As New ArrayList
        DT = DS.Tables(0)
        oORDR = oCompany.GetBusinessObject(SAPbobsCOM.BoObjectTypes.oOrders)
        oDEL = oCompany.GetBusinessObject(SAPbobsCOM.BoObjectTypes.oDeliveryNotes)
        Dim i As Integer
        For i = 0 To (DT.Rows.Count - 1)
            DR = DT.Rows.Item(i)
            Dim CurBaseDocEntry As String = DR.Item(0)
            'Check to see if the Sales Order update has already been processed
            If AL.Contains(CurBaseDocEntry) Then
                GoTo SkipLoop
            End If
            If oORDR.GetByKey(CurBaseDocEntry) = False Then
                Throw New Exception("Could not find Sales Order Key " & DR.ItemArray(0) & ".")
            End If
            If oDEL.GetByKey(DocEntry) = False Then
                Throw New Exception("Could not find Delivery Key " & DocEntry & ".")
            End If
            Dim DelTrackNum As String = oDEL.UserFields.Fields.Item("U_TrackNum").Value
            oORDR.UserFields.Fields.Item("U_TrackNum").Value = DelTrackNum
            Dim DelShipCost As Double = oDEL.UserFields.Fields.Item("U_ShipCost").Value
            oORDR.UserFields.Fields.Item("U_ShipCost").Value = DelShipCost
            <b>Dim DelTransCode As String = oDEL.TransportationCode
            oORDR.TransportationCode = DelTransCode</b>
            RetVal = oORDR.Update
            If RetVal <> 0 Then
                Dim Err As String, Msg As String
                oCompany.GetLastError(Err, Msg)
                Throw New Exception("Unable to update ORDR from ODLN. " & Err & " - " & Msg)
            Else
                AL.Add(CurBaseDocEntry)
            End If
SkipLoop:
        Next
    End Sub

Hi,
i think any of the fields in the base sales order get updated when u set the delivery 's(target's) base entry no
oDel.BaseEntry = docnum of Order
Hope this helps

Posting multiple goods issues against the same delivery

Hello gurus,
We are a fashion apparel company using ECC 6.0 and would like to know if it is possible to post mutliple goods issues against the same delivery?
I will explain the business requirement.
- We create a stock transport order to deliver 400 units of merchandise to on or our retail stores (STO is created and processed to a delivery).
- This information is passed down to our warehouse management system (which is not SAP)
- Our warehouse management system has the ability to split a delivery into multiple shipment when needed. For example, our warehouse may only be able to complete 250 units for our morning shipment and will therefore pick, pack and post this. This will feed back into SAP and process a 641 movement so that the units now show as "in transit". This is needed so that our stores can process the ASN and move the units into their inventory when they receive the merchandise later that day.
- During the afternoon, our warehouse will process the remaining 150 units and will ship this to our store later in the evening or next day.
Currently, we are not able to process another goods issue against a delivery as we close out the delivery during the first goods issue. We would prefer not to have to generate a new delivery for our DC and let them continue to process against the same delivery, but we are unsure how to configure this.
Any help or guideance would be extremely appreciated
Thanks in advance

Hi RJ,
First of all sorry to write such a lengthy reply,In one line if i want to summerize then it is not possible with standard SAP however we can achieve this by writing some piece of code in both the system
AS - IS
               Business process
          From business process point of view you are right that once the pick & pack is in process it is not advisable to create a new delivery document for balance quantity and share the same with WMS as then they have to create a new document in WMS and start picking based on that rather then the old delivery document number. if i am in your position then i can give a thought like this
e.g.
Delivery                                                  - 100 Unit
Shipment confirmation from WMS            -   60 Unit
Change in delievry quanity / Pick qty        -   60 Unit
Invoice from SAP                                    -   60 Unit
Second confirmation from WMS                          -   40 Unit
Change in the existing delivery quantity                -   Now here we have two option either
1) Change the delivery quantity / Pick qty to (60+40) =100 or
2) Remove the 60 and update 40 as delivery and pick quantity
Pros & Cons
if you will select option 1 then furhter invoice will happen for 100 unit which is incorrect as physically you are shipping only 40 unit
if you are selecting option 2 then the document flow is incorrect as you don't have history(in SAP) for the 60 unit which was shipped earlier
Solution ::
so in my opinion the best option is to create a seperate delivery document (store the old delviery number in one of the field of the new delivery and pass the same to custom segment of the IDoc) transmit the IDoc to WMS write the validation logic in WMS
Find the record with old deliver number in the WMS system, check the status whether it is active or inactive
if it is acitive Validate the Material + qty with the WMS record(Material + balance quantity) if both are same then pass the new deliery number to custom field of the WMS table
At the time of confirming back to the SAP, Write a piece of code in SAP that if the incoming idoc custom field(new delivery number) field is populated then ignore the orignal document number and post the document using the new delivery document number
Hope this help

Creation of outbound delivery from ASN

We have an issue while developing EDI interface with our subcontractor. The requirement is to create an outbound delivery in R/3 system based on the Advanced Shipping Notification (ASN) received from the subcontractor. In this business scenario subcontractor tells us how much quantity of component is required by them and when (based on their capacity). So we need to create outbound delivery from the ASN to dispatch the components. Kindly suggest how this can be done ?

Hi,
Please check the below links
http://help.sap.com/bp_bblibrary/500/html/W41_EN_DE.htm
http://help.sap.com/bp_cpwsd604/BBLibrary/HTML/298_EN_CO.htm
Kuber

Issue in CIF data between ECC to APO

Hi Experts,
We have ECC and APO system in our landscape. we have configured CIF and transferred data between ECC and APO however after ECC system refresh CIF configuration is not working. we verified and reconfigured the CIF configuration but still no luck.
strange thing is, while sending the data for e.g vendor from ECC to APO, there is no error reported. It displays successful in both qRFC trace files but the transferred data is nt reflecting in APO system.
There is no system run time error, no errors in system log (SM21), no logs in SLG1 application log, no erros in qRFC trace files.
we have enabled RFC user trace but can't conclude the issue. could you please anyone let me know where we can check the error log or how to resolve this?
Outbund Queue logs from ECC:
QTYPE :OUTBOUND/S
DATE       TIME     CLIENT     USER            QDATE      QTIME    BJOB       QEVENT
        TID                              ORGTID                        QSTATE
    DEST                                    ERRMESS
20.03.2015 17:44:56 300             20.03.2015 17:44:56 N          N
        0A1A01720F70550C0F4019E7                                       SENDING
    <SID>CLNT300
LUWCNT   QNAME                    FNAM
00000001 CFLDSHQCLNT300_0014      /SAPAPO/CIF_LOC_INBOUND
+++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
                                      QTYPE :OUTBOUND/S
DATE       TIME     EXETIME CLIENT USER            QDATE      QTIME    BJOB    QEVENT
        TID                              ORGTID                        QSTATE
    DEST                                    ERRMESS
20.03.2015 17:44:57 00:00:01 300          20.03.2015 17:44:56 N       N
        0A1A01720F70550C0F4019E7                                       CONFIRMD
    <SID>CLNT300
LUWCNT   QNAME                    FNAM
00000001 CFLDSHQCLNT300_0014      /SAPAPO/CIF_LOC_INBOUND
+++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
                                      QTYPE :OUTBOUND/S
DATE       TIME     CLIENT     USER            QDATE      QTIME    BJOB       QEVENT
        TID                              ORGTID                        QSTATE
    DEST                                    ERRMESS
20.03.2015 17:44:57 300             20.03.2015 17:44:56 N          N
        0A1A01720F70550C0F4019E8                                       SENDING
    <SID>CLNT300
LUWCNT   QNAME                    FNAM
00000001 CFLDSHQCLNT300_0014      /SAPAPO/CIF_GEN_EVENT
+++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
                                      QTYPE :OUTBOUND/S
DATE       TIME     EXETIME CLIENT USER            QDATE      QTIME    BJOB    QEVENT
        TID                              ORGTID                        QSTATE
    DEST                                    ERRMESS
20.03.2015 17:44:57 00:00:00 300          20.03.2015 17:44:56 N       N
        0A1A01720F70550C0F4019E8                                       CONFIRMD
    <SID>CLNT300
LUWCNT   QNAME                    FNAM
00000001 CFLDSHQCLNT300_0014      /SAPAPO/CIF_GEN_EVENT
+++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
Inbound Queue trace log from APO:
QTYPE :INBOUND
DATE       TIME     CLIENT     USER            QDATE      QTIME    BJOB       QEVENT
        TID                              ORGTID                        QSTATE
    DEST                                    ERRMESS
20.03.2015 17:39:48 300                20.03.2015 17:44:56 N          N
        0A1A01720F70550C0F4019E7                                       SENDED
    <SID>CLNT300
LUWCNT   QNAME                    FNAM
00000001 CFLDSHQCLNT300_0014      /SAPAPO/CIF_LOC_INBOUND
+++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
                                       QTYPE :INBOUND
DATE       TIME     EXETIME CLIENT USER            QDATE      QTIME    BJOB    QEVENT
        TID                              ORGTID                        QSTATE
    DEST                                    ERRMESS
20.03.2015 17:39:48 17:39:48 300             20.03.2015 17:44:56 N       N
        0A1A01720F70550C0F4019E7                                       FINISH
    <SID>CLNT300
LUWCNT   QNAME                    FNAM
00000001 CFLDSHQCLNT300_0014      /SAPAPO/CIF_LOC_INBOUND
+++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
                                       QTYPE :INBOUND
DATE       TIME     CLIENT     USER            QDATE      QTIME    BJOB       QEVENT
        TID                              ORGTID                        QSTATE
    DEST                                    ERRMESS
20.03.2015 17:39:48 300                20.03.2015 17:44:56 N          N
        0A1A01720F70550C0F4019E8                                       SENDED
    <SID>CLNT300
LUWCNT   QNAME                    FNAM
00000001 CFLDSHQCLNT300_0014      /SAPAPO/CIF_GEN_EVENT
                                       QTYPE :INBOUND
DATE       TIME     EXETIME CLIENT USER            QDATE      QTIME    BJOB    QEVENT
        TID                              ORGTID                        QSTATE
    DEST                                    ERRMESS
20.03.2015 17:39:48 17:39:48 300             20.03.2015 17:44:56 N       N
        0A1A01720F70550C0F4019E8                                       FINISH
    <SID>CLNT300
LUWCNT   QNAME                    FNAM
00000001 CFLDSHQCLNT300_0014      /SAPAPO/CIF_GEN_EVENT
                                       QTYPE :INBOUND
DATE       TIME     EXETIME CLIENT USER            QDATE      QTIME    BJOB    QEVENT
        TID                              ORGTID                        QSTATE
    DEST                                    ERRMESS
20.03.2015 17:39:48 00:00:00 300             20.03.2015 17:44:56 N       N
        0A1A019D23F8550C0E0C2559         0A1A01720F70550C0F4019E7      RUNNING
    <SID>CLNT300
LUWCNT   QNAME                    FNAM
00000001 CFLDSHQCLNT300_0014      /SAPAPO/CIF_LOC_INBOUND
                                       QTYPE :INBOUND
DATE       TIME     EXETIME CLIENT USER            QDATE      QTIME    BJOB    QEVENT
        TID                              ORGTID                        QSTATE
    DEST                                    ERRMESS
20.03.2015 17:39:48 00:00:00 300             20.03.2015 17:44:56 N       N
        0A1A019D23F8550C0E0C2559         0A1A01720F70550C0F4019E7      FINISH
    <SID>CLNT300
LUWCNT   QNAME                    FNAM
00000001 CFLDSHQCLNT300_0014      /SAPAPO/CIF_LOC_INBOUND
                                       QTYPE :INBOUND
DATE       TIME     EXETIME CLIENT USER            QDATE      QTIME    BJOB    QEVENT
        TID                              ORGTID                        QSTATE
    DEST                                    ERRMESS
20.03.2015 17:39:48 00:00:00 300             20.03.2015 17:44:56 N       N
        0A1A019D23F8550C0E0C2559         0A1A01720F70550C0F4019E7      CONFIRMD
    <SID>CLNT300
LUWCNT   QNAME                    FNAM
00000001 CFLDSHQCLNT300_0014      /SAPAPO/CIF_LOC_INBOUND
                                       QTYPE :INBOUND
DATE       TIME     EXETIME CLIENT USER            QDATE      QTIME    BJOB    QEVENT
        TID                              ORGTID                        QSTATE
    DEST                                    ERRMESS
20.03.2015 17:39:48 00:00:00 300             20.03.2015 17:44:56 N       N
        0A1A019D23F8550C0E0C255A         0A1A01720F70550C0F4019E8      RUNNING
    <SID>CLNT300
LUWCNT   QNAME                    FNAM
00000001 CFLDSHQCLNT300_0014      /SAPAPO/CIF_GEN_EVENT
                                       QTYPE :INBOUND
DATE       TIME     EXETIME CLIENT USER            QDATE      QTIME    BJOB    QEVENT
        TID                              ORGTID                        QSTATE
    DEST                                    ERRMESS
20.03.2015 17:39:48 00:00:00 300             20.03.2015 17:44:56 N       N
        0A1A019D23F8550C0E0C255A         0A1A01720F70550C0F4019E8      FINISH
    <SID>CLNT300
LUWCNT   QNAME                    FNAM
00000001 CFLDSHQCLNT300_0014      /SAPAPO/CIF_GEN_EVENT
                                       QTYPE :INBOUND
DATE       TIME     EXETIME CLIENT USER            QDATE      QTIME    BJOB    QEVENT
        TID                              ORGTID                        QSTATE
    DEST                                    ERRMESS
20.03.2015 17:39:48 00:00:00 300             20.03.2015 17:44:56 N       N
        0A1A019D23F8550C0E0C255A         0A1A01720F70550C0F4019E8      CONFIRMD
    <SID>CLNT300
LUWCNT   QNAME                    FNAM
00000001 CFLDSHQCLNT300_0014      /SAPAPO/CIF_GEN_EVENT
Thanks and regards,
Pradeep

Hello Pardeep,
Please check the setting of SMQS and SMQR for CF and client registration
these entries, the field 'TYPE' is set to 'R'.
QIN scheduler may be available for every client if you are working in this client with registered inbound queues.
Choose Edit->Activate scheduler from the menu (available in both SMQR and SMQS)
During processing in dialog work processes, the system uses a parallel RFC to restart the registered inbound queues. For this, you can use transaction RZ12 to specify a group of application servers and dialog work processes that are allowed to use a QIN scheduler. You must use transaction SMQR to assign the group name to the relevant QIN scheduler.
Different parameters in SMQR are explained in note 1579728. The explanation for SMQS is similar
Also try the report RSQIWKEX
Best Regards,
R.Brahmankar

Creating Delivery from Sales Document

Hi,
When I try to create a automatic delivery from the sales document I am getting an error as :
Delivery duplication only possible for one ship-to party.
I am trying to create Sales order through IDOC, still I find the same issue.
The message raised is VLBAPI - 001.
Is there any thing to do with partner profiles or the distribution model.
Thanks.

Hi,
You can find the duplicate entry in TBD06. Searching by FOBJVALUE for example may show where you have a duplicate RCVSYSTEM.
Regards,

Create outbound delivery from IDOC

i want to create outboud delivery from incomming idoc..is DELVRY02 idoc type and shpcom message type will do this ..after crating the delivery i aslo need to do PGI..
please tell me this idopc type and message type will do this or not?
Thanks,

Hi,
I also have the same issue - I would like to be able to create an outbound delivery via IDOC/BAPI although cannot find the means to accomplish this. Is there a standard process available to generate an outbound delivery without reference (VL01NO)? I would like to avoid writing custom code if possible.
Thanks!

Inbound Delivery from PGI

Hi SAP Gurus,
We are using two step STO process. I want to make Inbound delivery at the recieving plant from the Outbound delivery at the Issuing plant after PGI is done. What I understand is that we need to have ASN implemented to do so. Is there any other way available in standard SAP to do so?
Please tell.
Thanks
Manav

ASN implemented means you need to have Order Acknowledgment from the Vendor which we are not using in our system. This is IS Retail system and we are using STO between DC and Stores. The problem we are facing is when DC issues less material than what is in STO, Inbound delivery does not get updated for the same qty at Store. So the person who is recieving material expects qty mentioned in Inbound delivery but physically recieves less. So that creates problem as he tries to do GR of more material but systme does not let him do because of less qty in PGI. So now I want that system should create Inbound delivery from PGI/Outbound delivery instead of creating from STO. In this case it will be able to pull the exact qty of the material expected for GR in store.
So I want to know how to do this.

Account Determination Error when doing GI for Delivery from Projects

Hi,
When we try and Goods Issue a delivery from Projects, we get the following error:
Account determination for entry 0 GBB 0001 ___ 7900 not possible
We are not sure why the Account grouping code comes through with no value. Please could someone assist with this issue.
Regards,
De Wet

Hi,
Check in T code OBYC,whether the account determination is maintained against the valuation class for BPX.
Regards

Delivery from one plant taking order of another plant

Hi,
Please share your view that how it is possible to delivery from one plant taking the order from another plant where production is made in later plant and material is moved by STo to the first plant for despatch.
     So stock is ready in first plant but since the order is of second plant , if we bypass the first phase check in shipping point while create delivery by VLO1N , inside the document the second plant is determined. is there any way around?
Please explore.
Regards
Indranil Saha

Dear Lakhsmipathi,
Thnaks for your reply . I will Definitely close the open issues later.
   There is no problem about STO. Problem is that we have to issue the sale order in manufacturing plant and with respect to the same order we have to make the delivery by VL01N from another plant. So MRP will run in manufacturinf plant. Stock will built up in manufacturing plant, then it will be transferred to another plant and from there the same material is to be despatched where the delivering plant in sale order is the manufacturing plant.
    SAP does not allow to do it as the delivering plnat specified in the order is different from thye plant from where it is to be despatched.
   We have thought also to create customized routine for it where we may bypass the check of shipping point in copy control as well as the population of the plant which is to be filled up manually by user in delivery document.
   Is there any other alternative . please explore.
Regards
Indranil

Delivery from projects Assembly

Hello All,
When i am trying to do delivery from CNS0,for a project and WBS the system is not showing DeliveryQty,Open Qty is 0.
The system shows error.
Acitivty is confirmed,Delivery info isassinged to WBS
Ramanan

Hi Ramanan,
Please check whether material is getting issued to the network (281 movement) when you confirm the activity. In that case stock would be zero. Obviously, then you cannot make the delivery. Use MMBE and check the stock position, most likely yhis is the case.
Get the material into project stock and check out. It should work.
Muraleedharan.R

Create delivery from Purchase order

Hi all,
I want to know the TCode to create a delivery from a Purchase Order
Harini

HI HARINI KESANI,
IN ORDER TO CREATE DELIVERY FROM PO CAN DO THRU THE T.CODE
VL10B( BATCHES). ENTER THE PURCHASE DOCUMENT IN THE PURCHASE ORDERS TAB PAGE, CLICK ON EXECUTE
YOU WILL ENTER INTO ANOTHER SCREEN , SELECT THE LINE ITEM AND CLICK ON EXECUTE BACKGROUND.
YOU WILL GET THE DELIVERY NO., GO TO VL02N AND DO THE POST GOODS ISSUE.
YOUR CAN ALSO CHECK THE DELIVERY NO. IN THE P.O , PURCHASSE ORDER HISTORY TAB PAGE, THERE U CAN SEE THE STATUS OF THE GOODS ALSO , WHETHER MATERIAL DELIVERED ,ISSUED AND GR.
REGARDS,
RAM

Issue in CIF of delivery from R/3 to APO

Similar Messages

Maybe you are looking for