Creation of order

Dear Cons
I want to create a P.O by giving acct. assignment F ( order). For this order no. is necessary. pl. tell me the menu path or T-code for creation of order.
nrk

Thanks DB for your reply !!
   But My requirement is a bit different from your imagination.
   Once the order is delivered in R/3 system. The intransits will be created in SCM. we can see the In transits in RRP3 TCode. once the shipment is done I will get a file from the Customer and I need to delete the Intransits according to the data in the file.
    Once I got he file from the customer its will pass though XI (Exchange Infrastructure). later XI will call a BAPI of SCM system to delete Intransits in SCM,
    This is the process we are following as of now. Now we need to change this interface depending on SHIP to Data.
    If we got the file from the customer whose ship to is from VMI ship to then Instead of deleting intransits we need to create an order under the category "XX" created especially for this "Receipt " category type ("1" is of type Receipt). using the same order data which we are getting in the file.
     I went through the function module Using to change INtransits. But there is no field in the BAPI structure which can carry ATPCategory. So I am thinking to make use of different BAPI to Create orders under this new Category .
     Hope you understand my problem. Please help me....
Thanks & Regards,
Ramana

Similar Messages

Auto Creation of Order from Notification

Hi all,
As all of us are aware we can create notification automatically on creation of order, through Order/Notification integration setting in SPRO.
Is it possible to create Order automatically on creation of Notification in standard SAP ?? Pls confirm.
Thanks in advance,
Talanki

Hi
Option given in ECC6.0 cration of order from notificaton automatically by direct and background
With this option you can create the order from notification provided you need to update all the data in notificatin like funcitnal location/equipment/workcentre( so that it will fetch all the data from this master data while creating)
then if you select the PM notification>function>order >create direct or create backgroup option then order will be created but it will throw in pop up saying details of order type and planning plant.. if you say ok...then order will be created in foreground. if you select backgroud also it will throw popup if you say ok it will create the order in back ground.
For this you need to do the customization setting assigining the order type to notifiction so that it will automatically fetch the order type aganit the notification while creating the order.
regards
Krishna

Creation of order information profile for COID Transaction

Hi PP Friends,
Could anybody tell me the procedure to creation a Order iformation profile to use in COID tranaction, I need to create a profile for the object Material.
I have created but not showing in drop dowin of COID transaction. It look I missed some where.
Pl give me the solution for my issue of any body knows.
regards,
Purna

You can use transaction COISN
(Following taken from IDES help )
Define Profile for Order Information System
     In this step you can define overall profiles for the order information
     system.
     The overall profile controls
     o   what information is displayed in the order information system
     o   the layout of the information.
     An overall profile contains a number of individual profiles. Each
     individual profile contains parameters for the object overview list and
     the object detail list.
     In the overall profile you define the following:
     o   which objects are to be read from the database
     o   which objects are to be displayed in the list
     o   up to which object the objects are to be expanded in the overview.
     Activities
     Define which objects you want to display in the object overview.
Using Production Order Information System Profiles
The objects selected and the layout of the screen can be determined by an overall profile defined in the initial screen of the production order information system. The overall profile embodies various subordinated single profiles.
An overall profile can be assigned the following specifications:
u2022 A variant which can be used to suppress selection criteria
u2022 Which objects to read from the database
u2022 Which of these objects are to be displayed in the list
u2022 The object up to which objects are to be expanded on the object overview
u2022 Single profiles for all objects
A single profile is made up of sets of parameters. The first set of parameters applies to both the object overview and the object detail list. The other sets of parameters are subprofiles that apply only to the object detail lists. A profile controls the following aspects of the information system display:
u2022 Fields displayed in both object overview and object detail list
u2022 Subprofile defining the fields to be displayed in the object detail list
u2022 Specifications on how the list is formatted with respect to column width, field grouping,
   format of the values displayed
u2022 Sort criteria
u2022 Subprofile sort specification for the object detail list
u2022 Grouping criteria
u2022 Subprofile field grouping for the object detail list
u2022 User filters
u2022 Filter criteria to be used for selecting objectsu2014defined as a report variant for each set
of criteria
u2022 Status filtersu2014objects that are status controlled can be filtered according to a selection
profile

Setting default values to CUSTOMERH field during creation of ORDER?

Hi guys,
Does anyone know of any BAdI that is called once during the ORDER creation?
I have a CUSTOMERH field that needs to be set to 'X' during creation, and the user can de-select them anything. Anyone know how this can be achieved??
Many thanks in advance, points to be awarded for any helpful ideas.

Hi Joshua,
have a look to the interface IF_EX_ORDER_SAVE.
this give you the Methods CHANGE_BEFORE_UPDATE and PREPARE.
I hope you can use this.
kind regards an happy x-mas
Torsten

Problem in creation of order relevant - intercompany invoice

Dear all ,
I am facing problem in creation of intercompany invoice which is sales order relevant . Please tell which settings is required to resolve this as all the settings has been made.
Send ur email id so that the problem can be described if required....
Thanks .........

Hi,
while creating inter company sales order give the delivering plant in the overview screen. so that enables the system and tells that that is inter company sales order . u can verify whether the system takes which sales order whether it is standard order or inter company? by going to the conditions in the item overview in that u can find the "pi01" or "pi02" and select the delivery details there u can find the delivering plant which is supplying plant and the shipping point of the supplying plant..
in case of doubt u can mail me at [email protected]
Reward if Helpful..
Regards,
Praveen Kumar.D

Automatic form generation on creation transfer order for delivery note?

Hi,
I have to create a form that should automatically be generated on the creation of a transfer order for delivery note. How do I trigger this automatic creation of the form? And how can the transfer order number be passed to my print program?
Thx!

hi christophe,
To issue the delivery output, go to transaction VL02N.
Then go to EXTRAS-> OUTPUT->HEADER->EDIT
In the Message output screen enter the relevant output type created for the delivery.
Choose the relevant medium of output.
Choose Simple Mail, in this case the field NAST-NACHA will be having a value of 7.
Specify the Partner Function; in this case it is MA -> Mail partner address
Select the Communication Method for the output type maintained.
This will take you to the SAPOFFICE screen.
Enter there the E-Mail Address to which you want to send the delivery document as PDF.
A mail will be sent to the e-mail address of the E-Mail Address specified, with the delivery output form as a PDF attachment.
hope it will help u ..
*& Report ZZ_TEST                                                     *
REPORT zz_test                                 .
INCLUDE zz_test_top.
INCLUDE zz_test01.
      FORM entry                                                    *
--> RETURN_CODE                                                   *
--> US_SCREEN                                                     *
FORM entry USING return_code us_screen.
CLEAR retcode.
xscreen = us_screen.
PERFORM processing USING us_screen.
CASE retcode.
    WHEN 0.
      return_code = 0.
    WHEN 3.
      return_code = 3.
    WHEN OTHERS.
      return_code = 1.
ENDCASE.
ENDFORM.                    "entry
*& Include           ZZ_TEST_TOP                                      *
TABLES : nast,
           tnapr.
TYPES : BEGIN OF t_SOUDNAMEI1.
        INCLUDE STRUCTURE SOUDNAMEI1.
TYPES : END OF t_SOUDNAMEI1.
Internal Table declarations
DATA: i_otf TYPE itcoo OCCURS 0 WITH HEADER LINE,
i_tline TYPE TABLE OF tline WITH HEADER LINE,
i_receivers TYPE TABLE OF somlreci1 WITH HEADER LINE,
i_record LIKE solisti1 OCCURS 0 WITH HEADER LINE,
*Objects to send mail.
i_objpack LIKE sopcklsti1 OCCURS 0 WITH HEADER LINE,
i_objtxt LIKE solisti1 OCCURS 0 WITH HEADER LINE,
i_objbin LIKE solisti1 OCCURS 0 WITH HEADER LINE,
i_reclist LIKE somlreci1 OCCURS 0 WITH HEADER LINE,
i_lips LIKE lips OCCURS 0 WITH HEADER LINE,
i_SOUDNAMEI1 TYPE STANDARD TABLE OF t_SOUDNAMEI1.
Work Area declarations
DATA:w_objhead TYPE soli_tab,
wa_control_parameters TYPE ssfctrlop,
wa_output_options TYPE ssfcompop,
w_return TYPE ssfcrescl,
w_doc_chng TYPE sodocchgi1,
w_data TYPE sodocchgi1,
w_buffer TYPE string,"To convert from 132 to 255
wa_SOUDNAMEI1 TYPE t_SOUDNAMEI1,
Variables declarations
w_form_name TYPE rs38l_fnam,
w_len_in LIKE sood-objlen,
w_len_out LIKE sood-objlen,
w_len_outn TYPE i,
w_lines_txt TYPE i,
w_lines_bin TYPE i,
retcode      TYPE sy-subrc,
xscreen      TYPE c,
w_spld TYPE usr01-spld,
w_receiver TYPE SOXNA-FULLNAME,
w_OBJ_RECORD TYPE OBJ_RECORD,
w_user type sy-uname,
w_email TYPE ad_smtpadr.
Constants Declaration
CONSTANTS : c_x TYPE c VALUE 'X',
              c_atrate(1) TYPE c VALUE '@'.
*& Include           ZZ_TEST01                                        *
      FORM PROCESSING                                               *
FORM processing USING proc_screen.
SELECT * FROM lips
    INTO TABLE i_lips
    WHERE vbeln = nast-objky.
Call Function module to Getfunction Module name Generated by Smartform
CALL FUNCTION 'SSF_FUNCTION_MODULE_NAME'
    EXPORTING
      formname           = tnapr-sform
    IMPORTING
      fm_name            = w_form_name
    EXCEPTIONS
      no_form            = 1
      no_function_module = 2
      OTHERS             = 3.
IF sy-subrc <> 0.
    retcode = sy-subrc.
ENDIF.
CLEAR : wa_control_parameters,
          wa_output_options.
CASE nast-nacha.
    WHEN '1'.
      wa_control_parameters-device    = 'PRINTER'.
    WHEN '7'.
      DATA: l_email TYPE ad_smtpadr.
      wa_output_options-tdnoprev = c_x.
      wa_control_parameters-getotf = c_x.
To get the default output device maintained in the
User profile
     SELECT SINGLE spld FROM usr01
      INTO w_spld
      WHERE bname EQ nast-usnam.
      IF sy-subrc EQ 0.
        MOVE w_spld TO wa_output_options-tddest   .
      ENDIF.
      wa_output_options-tdnoprev = c_x.
      wa_control_parameters-getotf = c_x.
To get the email address maintained for the particular output
      CALL FUNCTION 'NAST_GET_MESSAGE_OBJECT_RECV'
        EXPORTING
          pi_objkey             = nast-tdname
        IMPORTING
          pe_addr               = w_receiver
        CHANGING
          pc_objhandle          = w_obj_record
        EXCEPTIONS
          maildata_not_readable = 1
          OTHERS                = 2.
      IF sy-subrc <> 0.
        MESSAGE ID sy-msgid TYPE sy-msgty NUMBER sy-msgno
       WITH sy-msgv1 sy-msgv2 sy-msgv3 sy-msgv4.
      ENDIF.
      IF w_receiver NA c_atrate.
To retrieve the E-Mail Id in case we get the User name from NAST
        CLEAR wa_soudnamei1.
        REFRESH i_soudnamei1.
        MOVE w_receiver TO wa_soudnamei1-fullname.
To get the user name
        CALL FUNCTION 'SO_NAME_CONVERT_API1'
          EXPORTING
            name            = wa_soudnamei1
          TABLES
            names           = i_soudnamei1
          EXCEPTIONS
            user_not_exist = 1
            parameter_error = 2
            x_error         = 3
            OTHERS          = 4.
        IF sy-subrc <> 0.
          MESSAGE ID sy-msgid TYPE sy-msgty NUMBER sy-msgno
           WITH sy-msgv1 sy-msgv2 sy-msgv3 sy-msgv4.
        ENDIF.
        CLEAR wa_soudnamei1.
        READ TABLE i_soudnamei1 INTO wa_soudnamei1 INDEX 1.
        MOVE wa_soudnamei1-sapname TO w_user.
To get the e-mail Id maintained in the user profile
        CALL FUNCTION 'FTR_CORR_CHECK_EMAIL_SAP_USER'
          EXPORTING
            i_user              = w_user
          IMPORTING
            e_email_address     = l_email
          EXCEPTIONS
            mail_address        = 1
            determination_error = 2
            OTHERS              = 3.
        IF sy-subrc <> 0.
          MESSAGE ID sy-msgid TYPE sy-msgty NUMBER sy-msgno
           WITH sy-msgv1 sy-msgv2 sy-msgv3 sy-msgv4.
        ENDIF.
        MOVE l_email TO w_receiver.
      ENDIF.
      MOVE w_receiver TO w_email.
ENDCASE.
wa_control_parameters-no_dialog = c_x.
wa_control_parameters-langu     = nast-spras .
wa_output_options-tdteleland    = nast-tland.
wa_output_options-tdtelenum     = nast-telfx .
wa_output_options-tdsenddate    = nast-erdat .
wa_output_options-tdsendtime    = nast-eruhr .
wa_output_options-tddataset     = nast-dsnam .
wa_output_options-tdsuffix1     = nast-dsuf1 .
wa_output_options-tdsuffix2     = nast-dsuf2 .
wa_output_options-tdimmed       = nast-dimme .
wa_output_options-tddelete      = nast-delet .
wa_output_options-tdautority    = nast-tdautority.
wa_output_options-tdcovtitle    = nast-tdcovtitle .
wa_output_options-tdcover       = nast-tdocover .
wa_output_options-tdreceiver    = nast-tdreceiver.
wa_output_options-tddivision    = nast-tddivision.
wa_output_options-tdcopies      = nast-anzal .
wa_output_options-tdnewid       = c_x.
wa_output_options-tdarmod       = nast-tdarmod.
wa_output_options-tdnoarmch     = c_x.
CALL FUNCTION w_form_name
    EXPORTING
     archive_index      = toa_dara
     archive_parameters = arc_params
      control_parameters = wa_control_parameters
      output_options     = wa_output_options
      user_settings      = ' '
    IMPORTING
      job_output_info    = w_return
    TABLES
      it_lips            = i_lips
    EXCEPTIONS
      formatting_error   = 1
      internal_error     = 2
      send_error         = 3
      user_canceled      = 4
      OTHERS             = 5.
IF nast-nacha EQ 7 AND sy-subrc EQ 0.
    i_otf[] = w_return-otfdata[].
    CALL FUNCTION 'CONVERT_OTF'
      EXPORTING
        format                = 'PDF'
        max_linewidth         = 132
      IMPORTING
        bin_filesize          = w_len_in
      TABLES
        otf                   = i_otf
        lines                 = i_tline
      EXCEPTIONS
        err_max_linewidth     = 1
        err_format            = 2
        err_conv_not_possible = 3
        OTHERS                = 4.
    IF sy-subrc <> 0.
      MESSAGE ID sy-msgid TYPE sy-msgty NUMBER sy-msgno
      WITH sy-msgv1 sy-msgv2 sy-msgv3 sy-msgv4.
    ENDIF.
Convert PDF from 132 to 255.
    LOOP AT i_tline.
Replacing space by ~
      TRANSLATE i_tline USING ' ~'.
      CONCATENATE w_buffer i_tline INTO w_buffer.
    ENDLOOP.
Replacing ~ by space
    TRANSLATE w_buffer USING '~ '.
    DO.
      i_record = w_buffer.
Appending 255 characters as a record
      APPEND i_record.
      SHIFT w_buffer LEFT BY 255 PLACES.
      IF w_buffer IS INITIAL.
        EXIT.
      ENDIF.
    ENDDO.
    REFRESH: i_reclist,
    i_objtxt,
    i_objbin,
    i_objpack.
    CLEAR w_objhead.
Object with PDF.
    i_objbin[] = i_record[].
    DESCRIBE TABLE i_objbin LINES w_lines_bin.
Document information.
    w_doc_chng-obj_name = 'Smartform'.
    w_doc_chng-expiry_dat = sy-datum + 10.
    CONCATENATE 'Delivery' 'Note'
    INTO w_doc_chng-obj_descr.
*w_doc_chng-obj_descr = 'Smart form output'.
    w_doc_chng-sensitivty = 'F'. "Functional object
    w_doc_chng-doc_size = w_lines_txt * 255.
Pack to main body as RAW.
Obj. to be transported not in binary form
    CLEAR i_objpack-transf_bin.
Start line of object header in transport packet
    i_objpack-head_start = 1.
Number of lines of an object header in object packet
    i_objpack-head_num = 0.
Start line of object contents in an object packet
    i_objpack-body_start = 1.
Number of lines of the object contents in an object packet
    i_objpack-body_num = w_lines_txt.
Code for document class
    i_objpack-doc_type = 'RAW'.
    APPEND i_objpack.
Packing as PDF.
    i_objpack-transf_bin = 'X'.
    i_objpack-head_start = 1.
    i_objpack-head_num = 1.
    i_objpack-body_start = 1.
    i_objpack-body_num = w_lines_bin.
    i_objpack-doc_type = 'PDF'.
    i_objpack-obj_name = 'Smartform'.
    CONCATENATE 'Delivery' 'Note' '.pdf'
    INTO i_objpack-obj_descr.
    i_objpack-doc_size = w_lines_bin * 255.
    APPEND i_objpack.
Document information.
    CLEAR i_reclist.
e-mail receivers.
    i_reclist-receiver = w_email.
    i_reclist-express = 'X'.
    i_reclist-rec_type = 'U'. "Internet address
    APPEND i_reclist.
sending mail.
    CALL FUNCTION 'SO_NEW_DOCUMENT_ATT_SEND_API1'
      EXPORTING
        document_data              = w_doc_chng
        put_in_outbox              = 'X'
      TABLES
        packing_list               = i_objpack
        object_header              = w_objhead
        contents_bin               = i_objbin
   contents_txt               = i_objtxt
        receivers                  = i_reclist
      EXCEPTIONS
        too_many_receivers         = 1
        document_not_sent          = 2
        document_type_not_exist    = 3
        operation_no_authorization = 4
        parameter_error            = 5
        x_error                    = 6
        enqueue_error              = 7
        OTHERS                     = 8.
    IF sy-subrc <> 0.
      MESSAGE ID sy-msgid TYPE sy-msgty NUMBER sy-msgno
      WITH sy-msgv1 sy-msgv2 sy-msgv3 sy-msgv4.
    ENDIF.
ENDIF.
ENDFORM.                    "processing

Duplicate material entry at the time of PO creation based order type

How Restrict duplicate material entry at the time of PO creation based on define order type.
Moderator message: please do some research before asking.
Edited by: Thomas Zloch on Mar 11, 2011 1:45 PM

Hi Rahul,
try with This Badi ME_PROCESS_PO , Method Open or Process item,
Implemente it and use a break-point to test it i.e it is triggred or nt , before processing it.
Regards,
Abhisek

Problem with creation of Order template

Hi Experts,
We are facing an issue with ISA 4.0. B2B application.
The extension data is not getting updated in CRM 4.0 while creating Order template.
The same extension data is getting updated for Order template change process.
Also same extension data is getting updated for CRM order creation.
Can any one put some lights on this issue ?
for both order and order template creation the below statement is used for holding the document.
SalesDocument preOrderSalesDocument = bom.getBasket();
Thnx.
Regards,
Murugan Arumugam.

Hi Experts,
We are facing an issue with ISA 4.0. B2B application.
The extension data is not getting updated in CRM 4.0 while creating Order template.
The same extension data is getting updated for Order template change process.
Also same extension data is getting updated for CRM order creation.
Can any one put some lights on this issue ?
for both order and order template creation the below statement is used for holding the document.
SalesDocument preOrderSalesDocument = bom.getBasket();
Thnx.
Regards,
Murugan Arumugam.

ATD Check Issue in creation TLB Order Manually in Planning Book.

Hi ,
I am facing issue in ATD Check in TLB Interactive Planning while creating TLB Order Manually.
Here goes scenario.
I am creating TLB Order Manually in TLB Planning Book with below Information.
Demand Date u2013 02.01.2012 ( Todayu2019s date ) & Qty u2013 20
Considering Lead Time of 10 Days to supply from Plant to Depot, Delivery Date in Purchase Order is calculated as 12.01.2012
Now I do outbound delivery for this PO in ECC. As client is not using Routes Transit Times functionalities, Planned Goods Issue Date for Outbound Delivery in ECC is calculated as Delivery Date from PO which is 12.01.2012 minus Transit Time in Route which is maintained as 0. Hence Planned Goods Issue Date in ECC is 12.01.2012.
This is same as Requirement Date for Outbound Delivery. PGI for this delivery is yet to happen. When PGI is done then issue is resolved.
When this Delivery goes in APO, it has requirement date as 12.01.2012 and now when I create TLB Order in Interactive Planning Book manually it allows me to create TLB Order of 20 qty extra before populating below message
u201CThere is only an ATD quantity of XXX available for product GHECP02u201D
In short it allows me to create 20 extra PO as Outbound Delivery is shifted to future bucketu2019s and hence is not counted in ATD Issues.
I am using Daily Bucket Profile in TLB Planning Book.
If I use Monthly Bucket Profile my issue is solved but again when client is creating TLB Order , by default system picks first date of bucket which client does not want.
Is there any way where in I can avoid this excess PO Creation. When it checks ATD Availability it should consider these outbound deliveries which are of future dates.
Regards,
Sameer

Hi Sameer,
Such kind of issues would come when master data/transaction data in APO and R/3 are not in sync.
You could go in for some custom development for TLB orders, but it's like opening a pandora's box as you are messing with teh standard working of system. It could create data inconsistencies between APO and R/3 and I would not really advise this. It's best to maintain all the relevant master data/transaction between APO and R/3 in sync.
Better ask your client to maintain the relevant routes as required. Otherwise they should create PO directly in R/3 as required.
Thanks - Pawan

Automatic Service Order creation and OBD line item creation - Repair Order

Hi ALL,
I tried to run the Repair process based on the help document of SAP:
Configs Followed:
1) In Material master MRP3 view, strategy group is assigned as 84 (service orders). By default this str.grp is linked with Requirement type SERA and Requirement class 203.
2 ) Requirement class is assigned with appropriate Service order type.
SPRO>Sales and Distribution>Basic Functions>Availability Check and Transfer of Requirements>Transfer of Requirements-->Define Requirements Classes (OVZG)
Actual Assignment:
Reqt. Class Service Order Type
039 SM01
203 SM01
3) Task list is assigned to your Service material - Service product - OISD
Actual Assignment:
Service Pdt Work Centre Plant B Area Gen TL Group Counter Task List Type
R-1001 PC-SERV 1200 8000 62 1 A
4) Check the Requirement class setting indicator for configuration (cnfg)
Actual Assignment:
= mandatory
5) SPRO>Sales and Distribution>Basic Functions>Availability Check and Transfer of Requirements>Transfer of Requirements-->Define Requirements Classes --> Determination Of Requirement Types Using Transaction
Actual Assignment:
Item Category Reqt class Reqt. Type
IRRS 039 SE
IRRE 203 SERP
IRRP 203 SERP
IRAL 040 KE
6) Sales and Distribution>Sales>Sales Document Item-->Assign Item Categories for determining the item category based on usage
Actual Assignment:
Sal. Doc. Type Item Cat. Group Item Usage H. L . Item Cat Item Category
RAS NORM IRRS
RAS NORM R101 IRRS IRRE
RAS NORM R102 IRRS IRRP
RAS NORM R103 IRRS IRAL
Errors Faced:
1. Service Order is not getting created automatically.
Error in SAP - IDES :"A service order has not been found for action 'Repairs'"
2. Also im not getting the automatic creation of the 4th line item(Item Category - IRAL) in the repair order, which in turn stops me from creating the Outbound delivery.
Please HELP !
Regards

Hi PeteA,
Sorry, here it is...
Let me explain the process that has been followed:
1) Initially to start with Service Notification was created with IW51 T-code.
    In that, Sold to party and material # were entered. Then from there directly i go for Create Repair Order from the Action Box.
    Order type for repair order - RAS, and when i save both Service Notification and the Repair gets saved.
    Now, in the repair order, two line items were getting created automatically and the requirement Types for those line items are:
    Line Item I : SE
    Line Item II: SERP
2) After that i take the material in with the help of t-code VRRE.
3) Then, i do the acceptance of the stock ( Technical Check) with t-code QA11.
    Once i do that, i get the Third line item in the Repair Order and the requirement Type for that line item is:
    Line Item III: SERP
Now my query is, Once i do the QA11 transaction i need to get a Service Order automatically but thats not happening.
Also if i create a Service Order manually, and do the repair and do the technically completion of the service order, then i need to get a third line item (IRAL) in the repair order automatically and thats also not happening.
Regards

Creation Purchase Orders in ECC (retraction) triggered from IP

Hi, my client (wholesaler) is implementing Integrated Planning for its Demand planning. Based on e.g.
- Sales History
- Product Information (e.g. products in stock and products on order)
it will determine the planned amount of materials that need to be purchased for a certain period. Once this is done, the user should be able to trigger (via a button on the IP screen) the creation of the relevant purchase orders in R/3 Materials Management. I came accross some examples of retraction of data from BPS/IP to R/3, mostly in the financial area.
Is it possible to do the above retraction? Has anyone encountered the same requirement i.e. automatic creation of (purchase) orders in R/3 triggered from IP or BPS for that matter? If so, how did you go about it? What was involved from a technical and functional point of view?
Thanks!
Pandaa

Hi.
There is no standard retraction to MM module (PO creation).
Very generally, you can write RFC function in ECC that uses BAPI to create PO, pass neded data from FOX to some function that will call RFC function and call the function within IP/WAD screen.
Regards.

Forbidden creation of order from notification

Hello Gurus,
I want to restrict the creation of maintenance order after 15 days of notification creation. Which user exit should I use?
I want to restrict the order creation at the time of creation not at the time of saving.
Regards,
VM

VM,
It can be done in user-exit IWOC0002 ("Check Status Change for Permission" for PM/CS) by setting the NO_STATUS_CHANGE flag
PeteA

Blocking creation of order/notificaiton against a equipment

Hi Friends ,
My requirement is to block order/notification creation against an equipment . I have tried creating a user status and activating radio button for "forbidden" against following transactions :
But its not working . Please help . Am I missing something ...

Here is User-exit way of achieving this. Once code is put in the respective user-exit it is hassle-free. Only thing is it prevents at the time of Save. Suppose the Equipment user status which should not allow user to create Notification or Order is 'DAMG' (say damaged),
Code for user-exit QQMA0014 to prevent notification creation
IF I_VIQMEL-EQUNR IS NOT INITIAL.
DATA: BEGIN OF I_USTAT OCCURS 10.
          INCLUDE STRUCTURE BAPI_ITOB_STATUS .
DATA:END OF I_USTAT.
DATA: BEGIN OF I_SSTAT OCCURS 10.
          INCLUDE STRUCTURE BAPI_ITOB_STATUS .
DATA:END OF I_SSTAT.
CALL FUNCTION 'BAPI_EQUI_GETSTATUS'
    EXPORTING
      EQUIPMENT     = I_VIQMEL-EQUNR
    TABLES
      USER_STATUS   = I_USTAT
      SYSTEM_STATUS = I_SSTAT.
LOOP AT I_USTAT.
    IF I_USTAT-TEXT = 'DAMG'.
      MESSAGE: 'The Status of equipment does not allow Notification Creation'
      TYPE 'E' DISPLAY LIKE 'I'.
    ENDIF.
ENDLOOP.
ENDIF.
This gives this error pop-up while saving, and the Notification is not created.
Similarly the code attached herewith, if used in user-exit IWO10009, would prevent Order creation giving rise to similar error pop-up. Hope this would be useful to you.
KJogeswaraRao

IDOCs creation - Transfer Orders(TOs) for Deliveries - Basic doubts, thanq

Hi Experts,
Am new to IDOCs. I hv a requirement, so, request u that, Can I get some Wht to do tips from u?
My doubts:
1- I hv been asked to create IDOC, Wht does it mean?
2 - How the created IDOC will be get posted?
My requirement is:
Original inbound idoc sent from Gentran will update the delivery with all serial numbers per material for all serialized product. The message code will be the indicator that a Transfer Order-TO, idoc must be created for TO confirmation.
I need to do===>   Should be executed only when the message code on the delivery idoc is u201CTOCu201D. Look up the warehouse code on the delivery header using the delivery nbr in the delivery idoc. Create a new TO confirm idoc per delivery idoc being processed. Create a line item on this idoc for every line on the delivery idoc. Each TO line includes the delivery number and delivery item number so the TO number and line number can be looked up in table LTAP by using the delivery number and line item number found on the delivery idoc. There will be at 2 transfer orders for each delivery item b/c of the 2 step pick process, so select the TO nbr that has 916 as the destination storage type (LTAP-NLTYP). There may be more than 1 pair of TOs per delivery item so this must be completed for each TO found relevant to each delivery item.
The inbound delvry03 idoc will update the delivery with the serial numbers as part of the standard functionality. Since the transfer order must also be confirmed with the quantities on the inbound idoc, an additional idoc must be created from within the delivery update process. The transfer order can be updated and confirmed using the standard idoc and function module which should be created and initiated from the delivery update function module customer exit.
Source = DELVRY03     Destination = WMTCID01
Record Name-Field Name-Record Name-Field Name-Description---Comments
E1EDL20     VBELN-E1LTCOH-LGNUM-Warehouse Number-Look w/ idoc delivery nbr
E1EDL20     VBELN-E1LTCOH-TANUM-Transfer Order Number- Look w/ idoc delivery nbr
E1EDL24     POSNR-E1LTCOI-TAPOS-Transfer Order Line Item- Look w/ idoc delivery line nbr
EVERY THING IS DATA TRIGGERED!!!
thanq
Edited by: Srinivas on Jun 27, 2008 4:41 PM

IDOC Programming
There are two processes in IDOC processing one is INBOUND PROCESS( IDOC coming to the system and its handling at various stages) and the other is OUTBOUND PROCESS( IDOC is send to other system . Separate ABAP programs are written for these 2 processes and different configuration settings are required for each one .Depending upon the trigeering mechanism different programming approaches are used.OUTBOUND PROGRAMS handle the IDOC creation and INBOUND PROGRAMS handle the inbound IDOC and the data trasfer from the IDOC to the database tables.
NEED FOR ABAP PROGRAMMING arises if
1)New IDOC was created
Depending upon the triggering mechanism i.e change pointer,message control
etc the programming technique changes and the type of process.
2)Existing IDOC was extended
User Exits are used to populate data in new segments added and to read them
back.
3)To enhance an exsiting process.
User Exits are used .
Basic structure of an OUTBOUND PROGRAM
The basic structure of all outbound programs is same. The CONTROL
record which is of TYPE EDIDC has to be filled. It contains important fields like
IDOCTP IDOC type
MESTYP Message Type
RCVPRN Recieving Partner (Destination)
RCVPRT Partner Type (it is LS i.e Logical System)
The DATA RECORD internal table which is of TYPE EDIDD has to be filled
in the same order as there are segments in the IDOC definition.
It has 2 important fields which are to be filled ,these are
SEGNAM Name of the segment
SEGDATA Data in the segment and can be upto 1000 bytes.This field
is corresponds to each data segment in the IDOC.
e.g.
DATA INT_EDIDD LIKE EDIDD OCCURS 0 WITH HEADER LINE.
DATA W_SEGDATA LIKE zsegment "custom segment zsegment
INT_EDIDD-SEGNAM = 'ZSEGMENT'
W_SEGDATA-field1 = value "taken from some table
W_SEGDATA-field2 = value "taken from some table
INT_EDIDD-SEGDATA = W_SEGDATA
APPEND INT_EDIDD
This will fill the data record corresponding to the segment ZSEGMENT . For all
segments the sam steps will be repeated until all the data corresponding to all the
segments in the idoc is filled in the internal table of type EDIDD.
There is only one control record and can be multile data records in the idoc
structure.
Which data is to be extracted from the tables to be filled in EDIDD type internal table is determined in standalone programs from the objects which are specified in the selection screen and from the object key passed to the function module in case of message control and is taken from BDCP table in case of change pointers using function modules "CHANGE_POINTERS_READ"
In case of stand alone programs and function modules based on change pointers method the function module "MASTER_IDOC_DISTRIBUTE" is used to send the IDOC to ALE layer for distribution ,in case of message control it is handled automatically by the RSNASTED program invoked by the message control.
OUTBOUND PROCESS AND OUTBOUND PROGRAM.
Outbound programs are used in outbound process to genearte IDOCs . There
purpose is to extract the data from the tables and to fill the IDOC data records
and the control record in the IDOC and pass ito the ALE layer for distribution to the recieving system .
Depending upon the triggering mechanism (how and when the outbound program will be started different techniques and interface is used for outbound program.
1)Message control
Application like PO(purchase order) creation use this technique , where the output type is linked to the application(Message control is a configurable cross application component which can be set in IMG .Such programs are created in the form of function modules and linked to the output type which is linked to the apllication.These have predefined interfaces.
In outbound programs(function module) that use message control the key of the
application document is passed to the function module whcig will read the data from the table depending upon the key passed(NAST structure) and fill the IDOC segemnts with the application data.The control record is also passed to the function module but is not fully filled, the rmaining fields are filled and the control is passed back to the calling program which is RSNASTED and is invoked by the
message control to process ALE and EDI output types and this program on recieving the IDOC data will create the physical IDOC in the system.
The parameteers passed to the function module are
IMPORTING PARAMETERS
OBJECT LIKE NAST
It contains documents key.
CONTROL_RECORD_IN LIKE EDIDC
It contains the partailly filled control record
EXPORETING PARAMETER
OBJECT_TYPE
CONTROL_RECORD_OUT LIKE EDIDC
TABLES
INT_EDID LIKE EDIDD
The internal table used to fill the data records in the same order as they exists in the IDOC.
The important parameters that should be filled in the custom function module are
CONTROL_RECORD_OUT and INT_EDIDD .The OBJK field of the structue NAST contains the key of the apllication document.
2)Stand alone programs
Generally used for Master Data transfer and as such depending upon the requirement can have different interfaces.The programs have a selection screen which has select options to select the objects, and parameters for specifying the recipient Logical System and the Message Type.
Data is selected based on the specified objects from the tables . and control record of type EDIDC is created and filled with important values like DIRECTION ,IDOCTP,RCVPRT,RCVPRN and MESTYP .
Data is filled in an internal table of TYPE EDIDD according to segment definitions
and in same order and the function module MASTER_IDOC_DISTRIBUTE is called passing the control record and the internal table containg IDOC data and importing an internal table consisting of control records for each communication IDOCS created.
3)Change pointer
Change Pointer table is read and checked if changes were made to important fields , if so the outbound program will be triggered automatically , these have predefined interfaces
ALE/IDOC Transaction
SALE Area Menu for ALE configurations.It includes transactions for
Logical System definition and linking it to a client, Transactions for
RFC Destination and Port Definition Etc.
SM59 RFC Destination
Here we specify the login settings for the destination including
the I.P address or Application Server name and the User name and
password.The information entered here is used to run Remote Function
Calls(RFC ) on the destination server .We can create number of types
of RFC Destinations but 3 types are important .
R/3 (R/3 to R/3), LS(logical system) and TCP/IP.
The name of the RFC destination should be same as that of Logical
System as it helps in creation of automatic partner profiles.
WE21 Port Definition.
There are 6 types of ports but only 2 types File and Transactional RFC
types of ports are important.
We have to specify the RFC Destination before a port can be created.
WE57 This is used to assign the Inbound function module to the Message Type
and to the IDOC Type.
WE42 This is used to define the process Code for Inbound Processing.
BD95 Define Filter object type .We can specify the field and the table it belongs
to as a filter object .
BD59 Assignment of Filter object type to the Message Type .Here we create the
link between Filter object and the segment and the message type and the
segment Field.
BD50 Set message Type to reducible.
BD65 Define Mandatory Fields.
BD64 Distribution Model . Also known as Customer Distribution Model Used to
define all the messages that will be exchanged between remote systems
and the name of thes logical systems. Any filters can also be specified.
The model once created has to be distributed on every system which will
be communicating ,It can be maintained on only One system.
BD21 Creating IDOcs from change pointers.
This can be used to create IDOCs from change pointers for a particular
message LIKE MATMAS.
BD22 This can be used to delete change pointers.
BD87 Status Monitor. Idocs can be selected base on number of criteria and there
processing status can be seen in detail.
BD10 Material Master Data Distribution .
Based on Message MATMAS.
BD12 Customer Master Data Distribution .
Based on Message CREMAS.
BD14 Vendor Master Data Distribution
Based on Message DEBMAS .
BDFG Generate ALE Interface for BAPI.
Here we specify the Business Object and the BAPI Function module for
which the interface has to be created.
WE31 Segment Editor.
This is used to create segments. We create the segment type and
segment definition is automatically created by editor e.g. Z1DUMMY is
segment type and Z2DUMMY is the segment definition .We specify the
fields and the data elements these cp\orresponds to create segments.
WE30 IDOC Editor
It is used to create a new IDOC Type or IDOC Extension .We specify the
segments that will be addd to the IDOC type.
WE02/05 IDOC List.
Various selct options and parameters are provided to select IDOCs
depending on the date, direction , mesage type etc.
WE20 Partner Profile
Here we create partner profile for each and every partner from / to which
the messages will be exchanged.There are 6 types of PF generally only
profiles of type LS(Logical System) ,KU(Customer) ,LI(Vendor) is used.
We specify the partner number and partner type and the agent and
the agent type responsible for handling of errors .
For every message send to the partner we have a outbound record and for
evry message coming from the partner we have the inbound record .
We specify the message in the otbound/inbound records ,double
clicking will take us to the detailed screen where the IDOC Type ,Port
and whether the IDCO will be immediatelt processed or collected are
mentioned.

Creation of Order from copying existing order in B2B

Hello Folks,
Do we need to do the copying control setting in SAP CRM GUI and also any specific setting in SHOP MANAGEMENT PROFILE for copying exiting transaction on B2B screen?
Regards

No need for any additional copy control. Or can I say, Copy Control configs have NO effect on web screens.
So, I am not sure how you would want to achieve "Copy" transaction in Web?
I can give you a hint. In the standard application (E-Commerce), there is an option to "Save as Template", where an order (basket / cart) can be saved as an Order Template. This uses "create from predecessor" classes in the Java layer and a similar function module in the backend (CRM) ABAP layer. With some enhacement effort, you can easily leverage these classes and function modules to implement your Copy feature.
Easwar Ram
http://www.parxlns.com

Creation of order

Similar Messages

Maybe you are looking for