Creation of a purchase order triggers the event ReleaseStepCreated twice

Hello,
I tried to use the standard workflow for the approval of a purchase order and noticed that i am receiving twice the same mail.
As you know, the workflow is triggered by the event ReleaseStepCreated. After I created a purchase order, i saw that the event is triggered twice, so that is why i am receiving two emails.
I believe this is wrong, Has anyone noticed this problem?
Thanks,
Efren

Hello,
The event linkage contains only one record, which is the one that connects my workflow to the event. This is not the cause.
What do you mean by delegations? Are you talking about delegated objects? If yes, i do not have any.
I looked in transaction SWEC(events for changed documents), and i guess i found the cause. There is a record with change doc. object EINKBELEG with the event ReleaseStepCreated of the object BUS2012. It has the trigger event "On Create", and in the Function Module, in Event Container it has function FRE_ORD_EVENT_PO_DB.
I removed this record and now the event RELEASESTEPCREATED is triggered only once, so i think it is ok.
I guess this record existed before there. Do you have that record with the function module FRE_ORD_EVENT_PO_DB?Or do you know what is the use of this function?

Similar Messages

IDOC creation after the creation of a purchase order

Hi everybody,
            I want some configuration details regardign IDOC creation. The requirement is, once i create a purchase order in one system, the details should automatciaclly transfer to other system through IDOC. could any one suggest any document or detailed procedure to accomplish the task. Thanks in advance,
         Santosh.

hi santosh kumar,
Creating an IDoc Segment WE31:
The segment defines the structure of the records in an IDoc. They are defined with transaction WE31.
We will define a structure to send a text from the text database.
Transaction WE31 calls the IDoc segment editor. The editor defines the fields of a
single segment structure. The thus defined IDoc segment is then created as a data
dictionary structure. You can view the created structure with SE11 and use it in an
ABAP as any TABLES declaration.
To demonstrate the use of the IDoc segment editor we will set up an example, which
allows you to send a single text from the text pool (tables STXH and STXL) as an
IDoc. These are the texts that you can see with SO10 or edit from within many
applications.
We will show the steps to define an IDoc segment YAXX_THEAD with the DDic
structure of THEAD.
To facilitate our work, we will use the "copy-from-template-tool", which reads the
definition of a DDIC structure and inserts the field and the matching definitions as
rows in the IDoc editor. You could, of course, define the structure completely
manually, but using the template makes it easier.
The tool in release 4.0b lets you use both DDIC structures or another IDoc segment
definition as a template.
The thus created structure can be edited any time. When saving, it will create a data
dictionary structure based on the definition in WE31. The DDIC structure will retain
the same name. You can view the structure as a table definition with SE11 and use it
in an ABAP the same way.
Defining the Message Type (EDMSG)
The message type defines the context under which an IDoc is transferred to its destination. It allows for using the same IDoc file format for several different applications.
Imagine the situation of sending a purchase order to a supplier. When the IDoc with
the purchase order reaches the supplier, it will be interpreted as a sales order
received from a customer, namely you.
Simultaneously you want to send the IDoc data to the supplier's warehouse to inform
it that a purchase order has been issued and is on the way.
Both IDoc receivers will receive the same IDoc format; however, the IDoc will be
tagged with a different message type. While the IDoc to the supplier will be flagged
as a purchase order (in SAP R/3 standard: message type = ORDERS), the same IDoc
sent to the warehouse should be flagged differently, so that the warehouse can
recognize the order as a mere informational copy and process it differently than a
true purchase order.
The message type together with the IDoc type determine the processing function.
The message types are stored in table EDMSG.
Defining the message type can be done from the transaction WEDI
EDMSG: Defining the message type (1)
The entry is only a base entry which tells the system that the message type is
allowed. Other transactions will use that table as a check table to validate the entry.
IT is as shown .
EDMSG: Defining the message type (1):
The entry is only a base entry which tells the system that the message type is
allowed. Other transactions will use that table as a check table to validate the entry.
Sales Orders are being created through inbound IDocs using FM 'EDI_DATA_INCOMING'. Now a Report is required to check the status of these Inbound IDocs along with Sales Orders generated against customer Purchase Orders.
Requirement:
Sales Orders are being created through inbound IDocs using FM 'EDI_DATA_INCOMING'. Now a Report is required to check the status of these Inbound IDocs along with Sales Orders generated against customer Purchase Orders.
Processing:
The report selects, 'ORDERS' IDoc numbers & status, generated between given time range, from table EDIDC. Further, it calls Function Module 'IDOC_READ_COMPLETELY' to get the IDoc details. Then required information is extracted by reading relevant field data of IDoc segments.
sampl code:
REPORT Z_EDI_FILE_LOAD_STATUS_REPORT           .
Staus Report for Inbound IDOCs ( Sales Orders )
Program        : Z_EDI_FILE_LOAD_STATUS_REPORT
Presented By   : www.rmtiwari.com
TABLES : EDIDC.
ALV stuff
TYPE-POOLS: SLIS.
DATA: GT_FIELDCAT TYPE SLIS_T_FIELDCAT_ALV,
      GS_LAYOUT   TYPE SLIS_LAYOUT_ALV,
      GT_SORT     TYPE SLIS_T_SORTINFO_ALV,
      GT_LIST_TOP_OF_PAGE TYPE SLIS_T_LISTHEADER.
DATA : BEGIN OF T_REPORT OCCURS 0,
         IDOC_NO       TYPE EDI_DOCNUM,
         IDOC_DATE     TYPE SY-DATUM,
         IDOC_TIME     TYPE SY-UZEIT,
         SORDER_NO     TYPE VBELN,
         STP_NO        TYPE KNA1-KUNNR,
         STP_NAME(35) TYPE C,
         STP_PHONE(12) TYPE C,
         PO_NO(15)     TYPE C,
         STATUS        TYPE C,
         S_TEXT(70)    TYPE C,
         ERROR(70)     TYPE C,
       END OF T_REPORT.
--PARAMETER--
selection-screen begin of block date with frame title TEXT-S01.
select-options: UDATE for EDIDC-UPDDAT
                      default SY-datum obligatory,    "Changed On
                UTIME for EDIDC-UPDTIM .             "Changed Time
selection-screen end   of block date.
INITIALIZATION.
START-OF-SELECTION.
PERFORM SHOW_STATUS_REPORT.
*&      Form alv_grid
      text
-->   p1        text
< -- p2        text
FORM ALV_GRID.
IF GT_FIELDCAT[] IS INITIAL.
    PERFORM FIELDCAT_INIT.
    PERFORM LAYOUT_INIT.
    PERFORM SORT_INIT.
ENDIF.
PERFORM GRID_DISPLAY.
ENDFORM.                    "alv_grid
*&      Form layout_init
FORM LAYOUT_INIT.
GS_LAYOUT-ZEBRA             = 'X'.
GS_LAYOUT-CELL_MERGE        = 'X'.
GS_LAYOUT-COLWIDTH_OPTIMIZE = 'X'.
GS_LAYOUT-NO_VLINE          = ' '.
GS_LAYOUT-TOTALS_BEFORE_ITEMS = ' '.
ENDFORM.                    " layout_init
*&      Form fieldcat_init
FORM FIELDCAT_INIT.
DATA: LS_FIELDCAT TYPE SLIS_FIELDCAT_ALV.
   CLEAR LS_FIELDCAT.
LS_FIELDCAT-FIELDNAME    = 'IDOC_NO'.
LS_FIELDCAT-KEY          = 'X'.
LS_FIELDCAT-REPTEXT_DDIC = 'IDOC'.
LS_FIELDCAT-OUTPUTLEN    = 10.
Fix for ALV print bug, which puts 'N/A' over last digit
Set inttype to 'N' to stop corruption of printed ALV cell.
LS_FIELDCAT-INTTYPE = 'N'.
APPEND LS_FIELDCAT TO GT_FIELDCAT.
CLEAR LS_FIELDCAT.
LS_FIELDCAT-FIELDNAME    = 'IDOC_DATE'.
LS_FIELDCAT-REPTEXT_DDIC = 'Creation Date'.
LS_FIELDCAT-OUTPUTLEN    = 10.
APPEND LS_FIELDCAT TO GT_FIELDCAT.
CLEAR LS_FIELDCAT.
LS_FIELDCAT-FIELDNAME    = 'IDOC_TIME'.
LS_FIELDCAT-REPTEXT_DDIC = 'Creation Time'.
LS_FIELDCAT-OUTPUTLEN    = 8.
APPEND LS_FIELDCAT TO GT_FIELDCAT.
CLEAR LS_FIELDCAT.
LS_FIELDCAT-FIELDNAME    = 'STATUS'.
LS_FIELDCAT-REPTEXT_DDIC = 'St'.
LS_FIELDCAT-OUTPUTLEN    = 2.
APPEND LS_FIELDCAT TO GT_FIELDCAT.
CLEAR LS_FIELDCAT.
LS_FIELDCAT-FIELDNAME    = 'ERROR'.
LS_FIELDCAT-REPTEXT_DDIC = 'Message'.
LS_FIELDCAT-OUTPUTLEN    = 70.
APPEND LS_FIELDCAT TO GT_FIELDCAT.
CLEAR LS_FIELDCAT.
LS_FIELDCAT-FIELDNAME    = 'STP_NO'.
LS_FIELDCAT-REPTEXT_DDIC = 'S.T.Party No'.
LS_FIELDCAT-OUTPUTLEN    = 10.
APPEND LS_FIELDCAT TO GT_FIELDCAT.
CLEAR LS_FIELDCAT.
LS_FIELDCAT-FIELDNAME    = 'STP_NAME'.
LS_FIELDCAT-REPTEXT_DDIC = 'Sold to Party Name'.
LS_FIELDCAT-OUTPUTLEN    = 35.
APPEND LS_FIELDCAT TO GT_FIELDCAT.
CLEAR LS_FIELDCAT.
LS_FIELDCAT-FIELDNAME    = 'PO_NO'.
LS_FIELDCAT-REPTEXT_DDIC = 'Purch Order'.
LS_FIELDCAT-OUTPUTLEN    = 15.
APPEND LS_FIELDCAT TO GT_FIELDCAT.
CLEAR LS_FIELDCAT.
LS_FIELDCAT-FIELDNAME    = 'STP_PHONE'.
LS_FIELDCAT-REPTEXT_DDIC = 'S.T.Party Phone'.
LS_FIELDCAT-OUTPUTLEN    = 15.
APPEND LS_FIELDCAT TO GT_FIELDCAT.
ENDFORM.                    "fieldcat_init
*&      Form sort_init
FORM SORT_INIT.
DATA: LS_SORT TYPE SLIS_SORTINFO_ALV.
CLEAR LS_SORT.
LS_SORT-FIELDNAME = 'IDOC_DATE'.
LS_SORT-SPOS      = 1.
LS_SORT-UP        = 'X'.
APPEND LS_SORT TO GT_SORT.
CLEAR LS_SORT.
LS_SORT-FIELDNAME = 'IDOC_TIME'.
LS_SORT-SPOS      = 2.
LS_SORT-UP        = 'X'.
APPEND LS_SORT TO GT_SORT.
CLEAR LS_SORT.
LS_SORT-FIELDNAME = 'STATUS'.
LS_SORT-SPOS      = 3.
LS_SORT-UP        = 'X'.
APPEND LS_SORT TO GT_SORT.
CLEAR LS_SORT.
LS_SORT-FIELDNAME = 'IDOC_NO'.
LS_SORT-SPOS      = 4.
LS_SORT-UP        = 'X'.
APPEND LS_SORT TO GT_SORT.
ENDFORM.                    "sort_init
*&      Form grid_display
FORM GRID_DISPLAY.
CALL FUNCTION 'REUSE_ALV_GRID_DISPLAY'
    EXPORTING
      IS_LAYOUT     = GS_LAYOUT
      IT_FIELDCAT   = GT_FIELDCAT
      IT_SORT       = GT_SORT
      i_callback_program      = SY-REPID
      I_CALLBACK_TOP_OF_PAGE = 'TOP_OF_PAGE'
      I_DEFAULT     = ' '
      I_SAVE        = 'X'
    TABLES
      T_OUTTAB      = T_REPORT
    EXCEPTIONS
      PROGRAM_ERROR = 1
      OTHERS        = 2.
ENDFORM.                    "grid_display
*&      Form COMMENT_BUILD
      Processing of listheader
FORM COMMENT_BUILD USING P_FK_LIST_TOP_OF_PAGE TYPE SLIS_T_LISTHEADER.
DATA: LS_LINE TYPE SLIS_LISTHEADER.
REFRESH P_FK_LIST_TOP_OF_PAGE.
List Heading : Typ H
CLEAR LS_LINE.
LS_LINE-TYP = 'H'.
LS_LINE-INFO = 'Sales Order Interface: Z_EDI_FILE_LOAD'.
APPEND LS_LINE TO P_FK_LIST_TOP_OF_PAGE.
List : Typ S
clear LS_LINE.
LS_LINE-typ = 'S'.
LS_LINE-key = 'Date Range:'.
LS_LINE-info = UDATE-low.
if not UDATE-high is initial.
    write ' To ' to LS_LINE-info+30.
    LS_LINE-info+36 = UDATE-high.
endif.
APPEND LS_LINE TO P_FK_LIST_TOP_OF_PAGE.
ENDFORM.                               " COMMENT_BUILD
      FORM TOP_OF_PAGE                                              *
      Ereigniss TOP_OF_PAGE                                       *
      event     TOP_OF_PAGE
FORM TOP_OF_PAGE.
PERFORM COMMENT_BUILD USING gt_LIST_TOP_OF_PAGE[].
CALL FUNCTION 'REUSE_ALV_COMMENTARY_WRITE'
    EXPORTING
      IT_LIST_COMMENTARY = GT_LIST_TOP_OF_PAGE.
ENDFORM.                    "TOP_OF_PAGE
*&      Form show_status_report
FORM SHOW_STATUS_REPORT .
Report to show status.
DATA: BEGIN OF T_TEDS2 OCCURS 0.
          INCLUDE STRUCTURE TEDS2.
DATA: END OF T_TEDS2.
DATA: BEGIN OF T_IDOC_CONTROL_TMP OCCURS 0.
          INCLUDE STRUCTURE EDIDC.
DATA: END OF T_IDOC_CONTROL_TMP.
CONSTANTS: C_STATUS_IN_IDOC_POSTED       LIKE EDIDC-STATUS VALUE '53'.
DATA : T_EDIDS TYPE STANDARD TABLE OF EDIDS WITH HEADER LINE.
DATA : T_EDIDD TYPE STANDARD TABLE OF EDIDD WITH HEADER LINE.
DATA : GV_PARTNER_SEG TYPE E1EDKA1,
         GV_PO_REF_SEG TYPE E2EDK02.
Get text for status values
SELECT * FROM TEDS2 INTO TABLE T_TEDS2 WHERE LANGUA = SY-LANGU.
Read the IDoc's status after processing
SELECT * FROM EDIDC
    INTO TABLE T_IDOC_CONTROL_TMP
   WHERE UPDDAT IN UDATE
     AND UPDTIM IN UTIME
     AND MESTYP = 'ORDERS'.
LOOP AT T_IDOC_CONTROL_TMP.
IDoc has been processed, since control record changed.
    READ TABLE T_TEDS2 WITH KEY STATUS = T_IDOC_CONTROL_TMP-STATUS.
    T_REPORT-IDOC_NO = T_IDOC_CONTROL_TMP-DOCNUM.
    T_REPORT-IDOC_DATE = T_IDOC_CONTROL_TMP-CREDAT.
    T_REPORT-IDOC_TIME = T_IDOC_CONTROL_TMP-CRETIM.
    T_REPORT-S_TEXT = T_TEDS2-DESCRP.
    IF T_IDOC_CONTROL_TMP-STATUS = C_STATUS_IN_IDOC_POSTED.
    ok status
      T_REPORT-STATUS = 'S'.
    ELSE.
    error status
      T_REPORT-STATUS = 'E'.
    ENDIF.
    Get IDoc details.
    CALL FUNCTION 'IDOC_READ_COMPLETELY'
      EXPORTING
        DOCUMENT_NUMBER         = T_REPORT-IDOC_NO
      TABLES
        INT_EDIDS               = T_EDIDS
        INT_EDIDD               = T_EDIDD
      EXCEPTIONS
        DOCUMENT_NOT_EXIST      = 1
        DOCUMENT_NUMBER_INVALID = 2
        OTHERS                  = 3.
Get Error status
    READ TABLE T_EDIDS WITH KEY STATUS = T_IDOC_CONTROL_TMP-STATUS.
    IF SY-SUBRC EQ 0.
      REPLACE FIRST OCCURRENCE OF '&1' IN T_EDIDS-STATXT
                            WITH T_EDIDS-STAPA1.
      REPLACE FIRST OCCURRENCE OF '&2' IN T_EDIDS-STATXT
                            WITH T_EDIDS-STAPA2.
      REPLACE FIRST OCCURRENCE OF '&3' IN T_EDIDS-STATXT
                            WITH T_EDIDS-STAPA3.
      REPLACE FIRST OCCURRENCE OF '&4' IN T_EDIDS-STATXT
                            WITH T_EDIDS-STAPA4.
      REPLACE FIRST OCCURRENCE OF '&' IN T_EDIDS-STATXT
                            WITH T_EDIDS-STAPA1.
      REPLACE FIRST OCCURRENCE OF '&' IN T_EDIDS-STATXT
                            WITH T_EDIDS-STAPA2.
      REPLACE FIRST OCCURRENCE OF '&' IN T_EDIDS-STATXT
                            WITH T_EDIDS-STAPA3.
      REPLACE FIRST OCCURRENCE OF '&' IN T_EDIDS-STATXT
                            WITH T_EDIDS-STAPA4.
      T_REPORT-ERROR = T_EDIDS-STATXT.
    ENDIF.
    LOOP AT T_EDIDD.
      CASE T_EDIDD-SEGNAM.
        WHEN 'E1EDKA1'.
          GV_PARTNER_SEG = T_EDIDD-SDATA.
          CLEAR : T_REPORT-STP_NAME.
          CALL FUNCTION 'CONVERSION_EXIT_ALPHA_INPUT'
            EXPORTING
              INPUT = GV_PARTNER_SEG-PARTN
            IMPORTING
              OUTPUT = T_REPORT-STP_NO.
          SELECT SINGLE NAME1 TELF1
            INTO (T_REPORT-STP_NAME,T_REPORT-STP_PHONE)
            FROM KNA1
           WHERE KUNNR = T_REPORT-STP_NO.
        WHEN 'E1EDK02'.
          GV_PO_REF_SEG = T_EDIDD-SDATA.
          T_REPORT-PO_NO = GV_PO_REF_SEG-BELNR.
      ENDCASE.
    ENDLOOP.
    APPEND T_REPORT.
ENDLOOP .
SORT T_REPORT BY STATUS IDOC_NO.
Show Report
PERFORM ALV_GRID.
ENDFORM.                    " show_status_report
thanks
karthik
reward me points if usefull.

Standalone Scenario - Error during Creation of Local Purchase Order

Hi All,
I am trying to setup Standalone Scenario, i have created all the master data locally, i am able to Order SC, but after workflow approval SC goes into error 'Error during creation of local purchase order from shopping cart XXXXXXXXX'
I have created following configuration setting for local PO number
1) In SPRO -> Cross-Application Basic Settings -> Number Ranges -> Define Number rang. for Schopping Carts and Follow-on Doc. --- i have number ranges for PO follow-on doc. i.e.
inrerval No = PO, from number = 0004000000, to number = 0004999999, ext. = unchecked
2) In SPRO -> Cross-Application Basic Settings -> Number Ranges -> Define Ranges per backend system for follow-on documents PO, PR etc
3) In sourcing (SPRO -> Cross-Application Basic Settings -> Sourcing -> Define Interactive Sourcing for product categories) --- sourcing is never carried out.
Can anybody help?
Regards,
SAP Guy.
Edited by: SAP Guy on Apr 23, 2008 2:32 AM

Hi SAP Guy,
Following steps are must for Local number range
1) Create number range for local PO
2) Maintain your logical system in 'Define number range per backend system for follow on document'
3) Define Transaction Type for BUS2201, define document type (e.g. EC1)
4) Assign Document type (EC1) in Org attribute BSA.
Hope this helps.
Regards,
Manish.

Purchase Order triggering Sales Order using Inbound Idocs

Hi All,
Can any one explain the flow of Purchase Order triggering Sales Order using Inbound Idocs..??
Thanks & Regards
Anoop

Use search tool to find sample like Integrating MM & SD Modules in Same Client to Create Sales order in Supplying Company Code Using PO raised in Receiving Company Code By I-Doc Message Type ORDERS Part1, Part 2 and Part 3.
Regards,
Raymond

Changed Purchase order triggering Email and Fax to vendor

Hello,
Ecc6.0 srm3.0.
a changed purchase order triggering email to vendor, although in the table BBPD_PO_METAOUT all the fields are unchecked and we donu2019t have customization in the table BBPD_COMP_FIELDS,
Please suggest, we donu2019t want email of fax to be triggered when we amend the purchase order,
Thanks for reply.
jairaj

When we change vendor text, It is SAP std that mail will triger to vendor

Email of the Purchase Order to the User

Hi,
Currently, I am able to send the email of the purchase order to the vendor mail address, which is mentioned on general data tab of the vendor master.
In addition, the requirement is that the purchase order also to be emailed to the User, who has created it.
I have added the VU in NACE settings for application EF, output type NEU. The payment medium I have used is 5 (external send).
However, when I try to add the VU and the user name to the vendor master partner details tab, the system is not taking in.
Please let me know how can I email the purchase order to user.
Thanks in advance for your time.
Thanks,
Ravi

Hi,
1) Add the user email address also in the vendor master.
2) Verify all settings in condition records.
3) Check tcode sost for any waiting send requests.
Regards,
BK

Create a Purchase order using the BAPI using the data in the XML file.

Hello Gurus,
here is the scenario can anyone help me how to proceed explaining the procedure?
Create a Purchase order using the BAPI using the data in the XML file.
comprehensive explanations are appreciated.
thanks in advance.

hi,
first use fm "bapi_po_create".
then use fm "BAPI_ACC_GL_POSTING_POST"
The demo environment was made with real business scenario in mind, but following subjects need to be addressed in a live implementation:
     No exceptions and error handling is implemented, except the order rejection (e.g. partly delivery);
     In Navision both XML Ports and the XML DOM has been used to integrate with SAP XI, because XML ports has some drawbacks regarding to Namespaces in XML Documents (mandatory in SAP XI);
     A minimum of SAP and Navision customization is required to implement this solution. (e.g. user exit in SAP, Navision XML DOM).

Creating a Purchase Order for the Asset

Hi,
Please see the following steps:
1.Create a purchase order for the asset.
2. Post a goods receipt from this PO.
3. Quantity of asset will be transfered from goods receipt.
But I find quantity of asset(AS02) was not be transfered and still was equal to 0.
Could you help me?
Thanks and Regards,
Colin.

see the field status varient for the gl account see the qty field is optional field or not
and check in the asset group also qty field is the optional field
Assign point if useful
Regards
A.k

Creation of a refurbishment order from the notification is not supported

Hello All,
I would like to know whether we can create Refurbishment Order directly from Refurbish. Request Notification.
Currently when trying to do that I'm getting error message saying that 'Creation of a refurbishment order from the notification is not supported'.
SAP doesn't support that kind of scenario or I'm missing some configuration?
Thanks in advance
G.

Hello again,
Thanks for your answer but I would like to get some more clarification.
What I would like to do is create Refurbishment Order from the notification directly by clicking create button which seats just next to order field or from the menu Notification -> Create -> Direct.
I'm getting pop up window where Order Type is filled in automatically because of the config I made. Then I just fill in Main Work Center field and hit continue. Afterwards message 'Creation of a refurbishment order from the notification is not supported' appears.
Can you confirm that above described scenario is not supported by SAP.
Thanks in advance.
G.

How to create multiple Purchase Order using the same document number?

HI Friends,
I m in a product which extracts data from SAP and stored in Access database.
For that,while i extracting Purchase Order from the Demo Database (SBODemo_US)for OEC Computers,the same DocNum is used for several Purchase Order using Index Line numbers.
eg:
DocNum for Purchase Order1 -->3000   0 (Index)
DocNum for Purchase Order2 -->3000   1 (Index)
    But i can't create multiple Purchase Order using same DocNum manually in SAP B1,Could anybody please help me <b>to create a Purchase Order using same DocumentNumber?</b>
Thanks in Advance
SooriyaKala.P

Hi,
The problem statement is not quite clear to me.
As far as I understand your statement, I think you want to club multiple orders into one purchase order using the index incrementally.
For this I think once you have created the first purchase order, open the purchase order in edit mode the second time and append the new line items.
If I am getting you wrong please explain the problem statement in more detail.
Regards,
Rara.

Purchase order for the new license

We sent the purchase order for the new license to Oracle on last Friday
yet to receive the new CSI for the new server .
can we still move forward with deployment activity and later specify the CSI
or would that stop us suring the install process if we don't have yet the CSI ?
Kindly help me .
If you have any idea any metaline node pls let me know ..
Thanks an addvance..
j2vinod

user11197404 wrote:
We sent the purchase order for the new license to Oracle on last Friday
yet to receive the new CSI for the new server .
can we still move forward with deployment activity and later specify the CSI
or would that stop us suring the install process if we don't have yet the CSI ?
Are you asking from a technical or legal standpoint?
If technical, do you see anything in the installation instructions that mention entering license information? What happens if you try to go ahead and install? What could be the worst that could happen?
>
Kindly help me .
If you have any idea any metaline node pls let me know ..
Thanks an addvance..
j2vinod

Uploading Purchase Order Against the Sales Order through DTW

Hi Experts,
I searched the forum but could not see anything regarding this.
Can I upload Purchase Orders against the Sales Orders using DTW upload facility? Manually we do it through the Logistics Tab in Sales Order.
Thank you in advance.
Kind Regards,
IC

Hi,
You can use the BaseType, BaseEntry and BaseLine columns for this in the row level template (DLN1):
BaseType: it's the Object Type of base document (ORDR.ObjType) which is '17' in case of Sales Order
BaseEntry: it's the Document Entry of the base document (ORDR.DocEntry)
BaseLine: it's the row number of the line in the base document (RDR1.LineNum)
If you import your Delivery Notes with this info, the link to the Sales Order will be updated just as if you used Copy To in SAP.
Regards,
Nat

Printing Terms and Conditions for each Purchase order in the RDF output

Hi All,
Present i have an RDF report with the registered concurrent program. when i run this concurrent program i am getting the terms and conditions at the end of the purchase orders only once(for example 10 purchase orders). Now the requirement is to get this terms and conditions printed for each purchase order. The output is in PDF format. It's an 11i RDF report. Can any one suggest me the methods how to do this? Please give me reply as soon as possible.
Thankyou in advance
Regards,
Polimera

Hi, Polimera
Welcome to OTN
Present i have an RDF report with the registered concurrent program. when i run this concurrent program i am getting the terms and conditions at the end of the purchase orders only once(for example 10 purchase orders). Now the requirement is to get this terms and conditions printed for each purchase order. The output is in PDF format. It's an 11i RDF report. Can any one suggest me the methods how to do this? Please give me reply as soon as possible.
Take a fixed frame inside the purchase order master repeating frame and place your terms and condition inside the fixed frame.
Hope this helps
If someone response is helpful or correct, please mark is accordingly

Delivery date in Purchase Order in the item overview

Hi all,
In which table is Delivery date in Purchase Order in the item overview stored.
the screen field name is eeind.
Thanks

In table EKET in field EINDT the delivery date is stored, based on the Schedule lines in the PO Item

Blanket Purchase Order and the Framework Order

hi Gurus,
I wanted to know the following.
What is the difference between Blanket Purchase Order and the Framework Order.
Thanks.

Hi,
Framework order is also known as Blanket PO.....which we use for the procurement of Low value Material with Long term planning....It is used as Mini Contract....
Blanket Order:
Used for long validity period and with the provided value limit. By its name u201Cblanketu201D which covers to required long time? We use doc type FO(for long period) and item cat. B(for value limit).Goods receipts or the entry and acceptance of services performed are not necessary in the case of a blanket PO and limit items. The invoices are posted directly with reference to the purchase order, provided that the specified value limit is not exceeded. But manual entry of invoiced amount and invoiced quantity is required during LIV process.
Example: Procurement of stationary items.
Frame work order:
Framework order (FO) is a document type which is provided by the standerd SAP.
It can be used for the consumable material ( Which is having low value & where making GR is not of worth like C category item.) & called as blanket PO. Here we need to mntion the validity period & target value or quantity as a restriction as well as need to mention item category as a "b".
Also it can be used for the procurement of extarnal services (Item category "D" ). Here we need to do the entry of services which have been performed & need to accept the same whereas in blanket PO, GR is not required.
At the end i would tel u that Framework order is the document type which can be used as blanket Po & procurement of services.
Regards
KK

Creation of a purchase order triggers the event ReleaseStepCreated twice

Similar Messages

Maybe you are looking for