Restriction on sending planned orders to SAP R/3

Dear all,
can anybody explain me the details as how can i control the transfer of transcation data to SAP R/3 either by timeline, or by PPDS production or SNP production horizon.
Scenario: We are planning cycle for 1 year where in we use 6 months consensus plan and 6 months annual business plan. now from management for business procurement is allowed only for 3 months, and want to control of transfer of transcation data to SAP R/3.
As my requirement is i need to send only the transcation data of 3 months only for execution. i.e. Transcation data with startdate comes within 3 months should only be transfered to SAP R/3.So that only purchase requisitions with in 3 months will be utilised and not of all year.
In short need a control on use of Pur. Req. being utilised.
Early reply will much more helpful.
Amol Chavan
I dont know it will clear my problem, suggestions on this greatly appericiated.

In transaction /SAPAPO/RRP7 you have fields Offset for Opening Period and Start Date (Instead of Opening Period).
The Opening Period is a field in the Location-Product Master (PPDS tab) which can be set based on the Products PP or SNP Horizon values.
As a result when you carry out conversion based on a certain Offset for Opening Period - for different products different horizon gets considered for selecting order for conversion.
F1 help for Offset for Opening Period mentions:
Number of calendar days by which the opening period for conversion should be increased.
The system uses the opening period to calculate the scheduled opening date for a planned order or for a purchase requisition. Using the conversion report, you can only transfer or convert a planned order or a purchase requisition if the opening date is on the current date, or if the opening date has passed (that is, is in the past).
On the other hand Start Date (Instead of Opening Period) disregards the Opening Period set in Product Master and considers the horizon as mentioned in Start Date range.
Hope this clarifies.
Somnath

Similar Messages

How can I send purchase order through SAP mail ?

How can I send purchase order through SAP mail ? Can any one explain whts the NACE settings?

just do it as <b>Anji reddy</b> said to you   ...or else ... in the purchase order trascation ...print it ... so that it will generate the spool request for that purchase order ....
so the   the belwo program is for sending <b>the Spool   Request data   as Email to any Email id ...</b>
The code below demonstrates how to retrieve a spool request and email it as a PDF document. Please note for the below program to process a spool request the program must be executed in background otherwise no spool request will be created. Once you have had a look at this there is an modified version of the program which works in both background and foreground. Also see transaction SCOT for SAPConnect administration.
*& Report ZSPOOLTOPDF                                                 *
*& Converts spool request into PDF document and emails it to           *
*& recipicant.                                                         *
*& Execution                                                           *
*& This program must be run as a background job in-order for the write *
*& commands to create a Spool request rather than be displayed on      *
*& screen                                                              *
REPORT zspooltopdf.
PARAMETER: p_email1 LIKE somlreci1-receiver
                                    DEFAULT '[email protected]',
           p_sender LIKE somlreci1-receiver
                                    DEFAULT '[email protected]',
           p_delspl AS CHECKBOX.
*DATA DECLARATION
DATA: gd_recsize TYPE i.
* Spool IDs
TYPES: BEGIN OF t_tbtcp.
        INCLUDE STRUCTURE tbtcp.
TYPES: END OF t_tbtcp.
DATA: it_tbtcp TYPE STANDARD TABLE OF t_tbtcp INITIAL SIZE 0,
      wa_tbtcp TYPE t_tbtcp.
* Job Runtime Parameters
DATA: gd_eventid LIKE tbtcm-eventid,
      gd_eventparm LIKE tbtcm-eventparm,
      gd_external_program_active LIKE tbtcm-xpgactive,
      gd_jobcount LIKE tbtcm-jobcount,
      gd_jobname LIKE tbtcm-jobname,
      gd_stepcount LIKE tbtcm-stepcount,
      gd_error    TYPE sy-subrc,
      gd_reciever TYPE sy-subrc.
DATA: w_recsize TYPE i.
DATA: gd_subject   LIKE sodocchgi1-obj_descr,
      it_mess_bod LIKE solisti1 OCCURS 0 WITH HEADER LINE,
      it_mess_att LIKE solisti1 OCCURS 0 WITH HEADER LINE,
      gd_sender_type     LIKE soextreci1-adr_typ,
      gd_attachment_desc TYPE so_obj_nam,
      gd_attachment_name TYPE so_obj_des.
* Spool to PDF conversions
DATA: gd_spool_nr LIKE tsp01-rqident,
      gd_destination LIKE rlgrap-filename,
      gd_bytecount LIKE tst01-dsize,
      gd_buffer TYPE string.
* Binary store for PDF
DATA: BEGIN OF it_pdf_output OCCURS 0.
        INCLUDE STRUCTURE tline.
DATA: END OF it_pdf_output.
CONSTANTS: c_dev LIKE sy-sysid VALUE 'DEV',
           c_no(1)     TYPE c   VALUE ' ',
           c_device(4) TYPE c   VALUE 'LOCL'.
*START-OF-SELECTION.
START-OF-SELECTION.
* Write statement to represent report output. Spool request is created
* if write statement is executed in background. This could also be an
* ALV grid which would be converted to PDF without any extra effort
WRITE 'Hello World'.
new-page.
commit work.
new-page print off.
IF sy-batch EQ 'X'.
    PERFORM get_job_details.
    PERFORM obtain_spool_id.
*** Alternative way could be to submit another program and store spool
*** id into memory, will be stored in sy-spono.
*submit ZSPOOLTOPDF2
*        to sap-spool
*        spool parameters   %_print
*        archive parameters %_print
*        without spool dynpro
*        and return.
* Get spool id from program called above
* IMPORT w_spool_nr FROM MEMORY ID 'SPOOLTOPDF'.
    PERFORM convert_spool_to_pdf.
    PERFORM process_email.
    if p_delspl EQ 'X'.
      PERFORM delete_spool.
    endif.
    IF sy-sysid = c_dev.
      wait up to 5 seconds.
      SUBMIT rsconn01 WITH mode   = 'INT'
                      WITH output = 'X'
                      AND RETURN.
    ENDIF.
ELSE.
    SKIP.
    WRITE:/ 'Program must be executed in background in-order for spool',
            'request to be created.'.
ENDIF.
*       FORM obtain_spool_id                                          *
FORM obtain_spool_id.
CHECK NOT ( gd_jobname IS INITIAL ).
CHECK NOT ( gd_jobcount IS INITIAL ).
SELECT * FROM tbtcp
                 INTO TABLE it_tbtcp
                 WHERE      jobname     = gd_jobname
                 AND        jobcount    = gd_jobcount
                 AND        stepcount   = gd_stepcount
                 AND        listident   <> '0000000000'
                 ORDER BY   jobname
                            jobcount
                            stepcount.
READ TABLE it_tbtcp INTO wa_tbtcp INDEX 1.
IF sy-subrc = 0.
    message s004(zdd) with gd_spool_nr.
    gd_spool_nr = wa_tbtcp-listident.
    MESSAGE s004(zdd) WITH gd_spool_nr.
ELSE.
    MESSAGE s005(zdd).
ENDIF.
ENDFORM.
*       FORM get_job_details                                          *
FORM get_job_details.
* Get current job details
CALL FUNCTION 'GET_JOB_RUNTIME_INFO'
       IMPORTING
            eventid                 = gd_eventid
            eventparm               = gd_eventparm
            external_program_active = gd_external_program_active
            jobcount                = gd_jobcount
            jobname                 = gd_jobname
            stepcount               = gd_stepcount
       EXCEPTIONS
            no_runtime_info         = 1
            OTHERS                  = 2.
ENDFORM.
*       FORM convert_spool_to_pdf                                     *
FORM convert_spool_to_pdf.
CALL FUNCTION 'CONVERT_ABAPSPOOLJOB_2_PDF'
       EXPORTING
            src_spoolid              = gd_spool_nr
            no_dialog                = c_no
            dst_device               = c_device
       IMPORTING
            pdf_bytecount            = gd_bytecount
       TABLES
            pdf                      = it_pdf_output
       EXCEPTIONS
            err_no_abap_spooljob     = 1
            err_no_spooljob          = 2
            err_no_permission        = 3
            err_conv_not_possible    = 4
            err_bad_destdevice       = 5
            user_cancelled           = 6
            err_spoolerror           = 7
            err_temseerror           = 8
            err_btcjob_open_failed   = 9
            err_btcjob_submit_failed = 10
            err_btcjob_close_failed = 11
            OTHERS                   = 12.
CHECK sy-subrc = 0.
* Transfer the 132-long strings to 255-long strings
LOOP AT it_pdf_output.
    TRANSLATE it_pdf_output USING ' ~'.
    CONCATENATE gd_buffer it_pdf_output INTO gd_buffer.
ENDLOOP.
TRANSLATE gd_buffer USING '~ '.
DO.
    it_mess_att = gd_buffer.
    APPEND it_mess_att.
    SHIFT gd_buffer LEFT BY 255 PLACES.
    IF gd_buffer IS INITIAL.
      EXIT.
    ENDIF.
ENDDO.
ENDFORM.
*       FORM process_email                                            *
FORM process_email.
DESCRIBE TABLE it_mess_att LINES gd_recsize.
CHECK gd_recsize > 0.
PERFORM send_email USING p_email1.
* perform send_email using p_email2.
ENDFORM.
*       FORM send_email                                               *
* --> p_email                                                       *
FORM send_email USING p_email.
CHECK NOT ( p_email IS INITIAL ).
REFRESH it_mess_bod.
* Default subject matter
gd_subject         = 'Subject'.
gd_attachment_desc = 'Attachname'.
* CONCATENATE 'attach_name' ' ' INTO gd_attachment_name.
it_mess_bod        = 'Message Body text, line 1'.
APPEND it_mess_bod.
it_mess_bod        = 'Message Body text, line 2...'.
APPEND it_mess_bod.
* If no sender specified - default blank
IF p_sender EQ space.
    gd_sender_type = space.
ELSE.
    gd_sender_type = 'INT'.
ENDIF.
* Send file by email as .xls speadsheet
PERFORM send_file_as_email_attachment
                               tables it_mess_bod
                                      it_mess_att
                                using p_email
                                      'Example .xls documnet attachment'
                                      'PDF'
                                      gd_attachment_name
                                      gd_attachment_desc
                                      p_sender
                                      gd_sender_type
                             changing gd_error
                                      gd_reciever.
ENDFORM.
*       FORM delete_spool                                             *
FORM delete_spool.
DATA: ld_spool_nr TYPE tsp01_sp0r-rqid_char.
ld_spool_nr = gd_spool_nr.
CHECK p_delspl <> c_no.
CALL FUNCTION 'RSPO_R_RDELETE_SPOOLREQ'
       EXPORTING
            spoolid = ld_spool_nr.
ENDFORM.
*&      Form SEND_FILE_AS_EMAIL_ATTACHMENT
*       Send email
FORM send_file_as_email_attachment tables it_message
                                          it_attach
                                    using p_email
                                          p_mtitle
                                          p_format
                                          p_filename
                                          p_attdescription
                                          p_sender_address
                                          p_sender_addres_type
                                 changing p_error
                                          p_reciever.
DATA: ld_error    TYPE sy-subrc,
        ld_reciever TYPE sy-subrc,
        ld_mtitle LIKE sodocchgi1-obj_descr,
        ld_email LIKE somlreci1-receiver,
        ld_format TYPE so_obj_tp ,
        ld_attdescription TYPE so_obj_nam ,
        ld_attfilename TYPE so_obj_des ,
        ld_sender_address LIKE soextreci1-receiver,
        ld_sender_address_type LIKE soextreci1-adr_typ,
        ld_receiver LIKE sy-subrc.
data:   t_packing_list like sopcklsti1 occurs 0 with header line,
        t_contents like solisti1 occurs 0 with header line,
        t_receivers like somlreci1 occurs 0 with header line,
        t_attachment like solisti1 occurs 0 with header line,
        t_object_header like solisti1 occurs 0 with header line,
        w_cnt type i,
        w_sent_all(1) type c,
        w_doc_data like sodocchgi1.
ld_email   = p_email.
ld_mtitle = p_mtitle.
ld_format              = p_format.
ld_attdescription      = p_attdescription.
ld_attfilename         = p_filename.
ld_sender_address      = p_sender_address.
ld_sender_address_type = p_sender_addres_type.
* Fill the document data.
w_doc_data-doc_size = 1.
* Populate the subject/generic message attributes
w_doc_data-obj_langu = sy-langu.
w_doc_data-obj_name = 'SAPRPT'.
w_doc_data-obj_descr = ld_mtitle .
w_doc_data-sensitivty = 'F'.
* Fill the document data and get size of attachment
CLEAR w_doc_data.
READ TABLE it_attach INDEX w_cnt.
w_doc_data-doc_size =
     ( w_cnt - 1 ) * 255 + STRLEN( it_attach ).
w_doc_data-obj_langu = sy-langu.
w_doc_data-obj_name   = 'SAPRPT'.
w_doc_data-obj_descr = ld_mtitle.
w_doc_data-sensitivty = 'F'.
CLEAR t_attachment.
REFRESH t_attachment.
t_attachment[] = it_attach[].
* Describe the body of the message
CLEAR t_packing_list.
REFRESH t_packing_list.
t_packing_list-transf_bin = space.
t_packing_list-head_start = 1.
t_packing_list-head_num = 0.
t_packing_list-body_start = 1.
DESCRIBE TABLE it_message LINES t_packing_list-body_num.
t_packing_list-doc_type = 'RAW'.
APPEND t_packing_list.
* Create attachment notification
t_packing_list-transf_bin = 'X'.
t_packing_list-head_start = 1.
t_packing_list-head_num   = 1.
t_packing_list-body_start = 1.
DESCRIBE TABLE t_attachment LINES t_packing_list-body_num.
t_packing_list-doc_type   = ld_format.
t_packing_list-obj_descr = ld_attdescription.
t_packing_list-obj_name   = ld_attfilename.
t_packing_list-doc_size   = t_packing_list-body_num * 255.
APPEND t_packing_list.
* Add the recipients email address
CLEAR t_receivers.
REFRESH t_receivers.
t_receivers-receiver = ld_email.
t_receivers-rec_type = 'U'.
t_receivers-com_type = 'INT'.
t_receivers-notif_del = 'X'.
t_receivers-notif_ndel = 'X'.
APPEND t_receivers.
CALL FUNCTION 'SO_DOCUMENT_SEND_API1'
       EXPORTING
            document_data              = w_doc_data
            put_in_outbox              = 'X'
            sender_address             = ld_sender_address
            sender_address_type        = ld_sender_address_type
            commit_work                = 'X'
       IMPORTING
            sent_to_all                = w_sent_all
       TABLES
            packing_list               = t_packing_list
            contents_bin               = t_attachment
            contents_txt               = it_message
            receivers                  = t_receivers
       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.
* Populate zerror return code
ld_error = sy-subrc.
* Populate zreceiver return code
LOOP AT t_receivers.
    ld_receiver = t_receivers-retrn_code.
ENDLOOP.
ENDFORM.
Girish

Constraining Planned Orders in SAP-PP

Hi,
Can someone indicate me how I can get my planned orders constrained into SAP-PP?
I have an external Requirement Planning tool that generate an unconstrined requirement plan. The external tool is then interfaced into SAP to send in the planned orders.
I will then like to know the steps I need to use to setup a constraining process to optimize the allocation of plans to my capacities.
Thanks,
Paulin

Paulin,
You could configure capacity management, then run capacity leveling. Strictly speaking, this will provide a plan in which each work center's load is constrained to work center capacity. However, the overall plan will not be optimized, nor will it necessarily be feasible. For this functionality, you need APO.
ERP Capacity leveling overview
http://help.sap.com/saphelp_erp60_sp/helpdata/en/8a/a58a794adc11d189740000e8322d00/frameset.htm
Best Regards,
DB49

Error while creating Planned order in SAP PP

Hi ,
I am creating planned order for finished material and system has given below error - Please specify the order deadlines in ascending order.
SAP Message Error- Message no. 61009 Please specify the order deadlines in ascending order
Very first planned order get saved and we declare the production and business completed
Now creating second planned order , while saving system giving above error.
I am Taking Planned Order Profile LA -Stock order
Any solution ...?
Thanks in advance !!!
Deepak.

Hello Deepak,
Please adjust the order dates in the scheduling of the planned order. In normal production scenario operation completed end of the night shift and order finish date is possibly moved one day in the future for this reason we need to set the operation timing in 24:00:00 format
In your issue change date like this
End date : 30.06.2014
Start : 31.05.2014
Opening date : 31.05.2104
Check with this date, it’s work for you
Regards
Umesh Mali

Restrict release of planned orders

Hi,
I am working in ASCP - and my user would like the ability to restrict the release of planned orders by either planner code or user ID. Is there a way I can do this via profile option, or form personalization, or anything else?
Please provide insight on other ways to achieve this!
Thanks
Valeria

Hi,
Yes but in that case the responsibility being used to release the planned orders should not have access on any OU.
Below is the other thread where i gave the solution for requisitions.
Release from Planner's workbench auto-triggers WIP Mass Load, how do we restrict
Please let me know if you are interested and we can do it at user levels also if can't implemented at resp level..
Thanks,
Abhishek Sharma
Please mark the post correct or helpful, if answered

Automatic changing of activity start date and time of planned orders in SAP

Hello experts,
I have a requirement that in the transaction /SAPAPO/SEQ1 for the list of planned orders what ever we get in the sap we have to swap the activity start date and time for two planned orders which we select automatically. For this I have found the BADI "/SAPAPO/SEQ_VISUAL01".
Now i am able to identify the two selected planned orders inside the BADI method SEQGRID_TOOLBAR_OKCODE_HANDLE.
Now my requirement is i have to swap the start date and time for these two planned orders automatically i.e. through BAPI or any FM.
Any idea of any BAPI or FM to change the details of the planned order.
Thanks,
Sanath.

Hi Sanath,
Please check this BAPI BAPI_MOSRVAPS_SAVEMULTI3. This Bapi has the provision of chaning Planned Order & Production Order Data. Also, you can explore more info on available bapis in the T-code 'BAPI'.
Thank you,
Santosh KB.

Restriction of conversion planned order

Hi SAP Gurus,
I have question. Exists any way, how to set up, that planned order could be converted to productin order only 14 days before planned start?
Thaks
Lukas

Hi Lukas,
You can mantain schedule margin key for the plant in customizing and mantain the opening period as 14 days. You need to mantain the material master with schedule margin key.
With the opening period mentioned, when planned order is created it would subtract 14 days from order start date.
Do let me know if it suits your requirement.
BR
Rahul

EDI IDOC OUTBOUND send Purchase Orders from sap to vendors

Hi Experts,
I am new to EDI IDOCS, but i got object on this. So my requirement is purchase orders are send to vendors from sap (OUTBOUND) through EDI-850 format. and also i have to add some more fields to standard idoc type ORDERS05, one more condition is if vendor type is not EDI, then the POs should send through fax, email, how can we solve this condition.
So plaese send some sample code on this object.
Thanks in advance,
S Reddy

Hi ,
You can send the purchase order to the vendors using different outytpes configurations in NACE transaction .
If you define a particular output type where you need to give medium 6 and define partner functions within this you can also set condition which partner needs to recieve EDI output and which one FAX or email all this will be done by Functional expert.
For adding extra segments to your basic type ORDERS05 you need to extend the idoc you can do it via WE30 and WE31 .Link you message type to basic type and extension . Please follow below tcodes for further help . Create all the requested steps in the tcodes mentioned below.
we20:patner profile
we21:port
we30:idoc creation
we30:segment creation
we81:message type
we82:link message with idoc type.
we02:to status of idocs.
Now you need to write code for filling those extra segments you have added to you extension type. For that you need to check where your new segment is placed in Idoc structure . There will be a exit avaliable to attach your code to fill those segments .
Please go through previous SDN links to see more info.
One the settings are done in the NACE , issue output from PO transction and once your output is processed check your Idoc in WE02 to see if the segments are coming with the desired data.
Regards
Vikas

Migration of Planned Orders from one SAP system to another one

Hi,
A quick help needed.
We are migrating SAP data from one SAP system to other due to business split. Regarding PP data, can Planned orders be migrated as it is from one SAP System to another? What is the impact if we do so?
Appreciate your response.
Kind Regards,
tanuji

hi ,
As suggested , you can propose to migrate only Firmed Planned orders from SAP to SAP system .
How to acheive it ?
You can use below BAPI to extract details of planned order from Table PLAF and upload in TARGET SYSTEM
BAPI_PLANNEDORDER_CREATE
Please note newly created Planned order in Target system would not have BOM EXPLOSION and Scheduling .
If need , Make a BDC recording as a add on step to explode Bom and Schedule by clicking those icons in Planned order .
Technical Team can do this .

Core Interface: Planned Order Integration

Hi
We are planning a product in both systems (ECC & APO). We want to restrict the Planned Order Integration b/w ECC & APO which are generating in ECC. At a same time we want a Planned order integration which are generating in APO.
Is there any standard BADI, USER Exit ?
Kindly give your valuable inputs for my mentioned query.

Hi Gurvarender,
Find this Customer exist for planned order
In SAP APO
Customer Exits For Planned Orders
●      APOCF004 u2013Inbound processing of planned orders
●      APOCF020 u2013 User-specific fields in the order interface
●      APOCFPIP u2013 Publication of in-house production orders (planned orders)
In SAP R/3
Customer Exits For Planned Orders
●      CIFORD01 u2013 Enhancement for order inbound interface .
●      CIFORD02 u2013 Enhancement for the transfer of customer-specific order fields )
●      CIFORD03 u2013 Enhancement for inbound customer-specific fields in the in-house production order
Regards,
MJ

Option to convert Planned orders to Process order C

Kindly suggest, which is the best option to convert Planned order to Process order C from below mentioned options
1) Convert Planned orders to Process order C & send it to R/3. or
2) Send Planned orders to R/3 & convert it into Process order C in R/3
Regards,
Chetan

Depends on the process and how stable your planning is. If there is a lot more decisions to be made in the R3 side you let the planned orders be converted in R3 else
you normally would use the conversion indicator and send the planned order to R3 and it gets converted to Process Order there

Delete Planned Orders

Experts,
is there a way to delete (Mass Delete) planned orders in SAP. Beside using MRP-Run ?
Thanks in advance
Jörg

HI
Check this program RMPLAF00
also check this thread
How to mass delete unfirmed planned orders?
Regards
Anupam Sharma

SAP PP-delete Production orders, planned orders, purchase requitions & othe

How to delete Production orders, planned orders, purchase requitions & other orders .
Pls send me the T-codes or Paths.
Any comments welcome & Thanks in advance.

Dear,
1) Delete Production Order,
Please refer this link,
[DeleteProduction Orders |http://www.sap-img.com/production/how-to-delete-old-production-orders.htm]
2) Delete Planned Order,
MD16 is the only option to delete planned orders in mass.
During MRP run if you choose - Delete and recreate plan order mode. Automatically the unwanted plan orders
2) Delete Purchase Requisation,
Execute MD04, in that it will display the created PR's
Check in tcode MD62 whether you have any demand for that material which you are getting PRs first delete requirement here/
Then run MRP by tcode MD03 or MD02 giving input of material and plant. In the initial screen of MD03 / MD02, make field planning mode - Delete and recreate planning data
Is that Old PR Firmed.
If yes remove the Firm indicator and Re run the MRP with planning Mode 3.
It removes the PR from EBAN.
Now check in MD04
OR,
Use Mass change transaction code MEMASSRQ or use BAPI (BAPI_REQUISITION_DELETE) to do the same.
Or
Use ME57 with layout ALV, in this also u can delete PR
If you want delete PR manually then
goto ME52N --> enter PR number --> select line item --> click delete button
or
goto ME52N --> enter PR number --> Item --> Tab Quanties/Dates --> set tick mark for closed check box
Please check this thread,
Deletion of SubReq
Hope it will help you.
Regards,
R.Brahmankar

Planned Order to Purchase Order report in SAP

Dear All
The Business process is Planned Order - Converted to Purchase Requsition - Converted to purchase order .
Is there any report in SAP , which shhows the direct link between Planned order to Purchase Order ?
Regards
Shyam

I have never seen a standard report, build a query based on tables PLAF, EBAN and EKET should be involved

How to restrict planned order by production order type

we develop one Z-report which include planned order as well as production .on restriting the output by order type given on selection screen of report, production order can be restricted but it show all the planned order which is to be converted to selected order type production order or not.
is there any suggesion to display that planned order only to the output of report which will convert to the production order of the type given on selection screen of report.
i know that we define prod scehu profile in work sched view of material and in production schedu. profile we define the order type picked while conversion of planned order to production order.but i am not able to connect them by using table...please guide

Hi,
Could you explain your problem correctly.
regards
mkrk

Restriction on sending planned orders to SAP R/3

Similar Messages

Maybe you are looking for