View attached files for Sales Order in Approbation.

Hi,
I have attached a file in a Sales Order. My Sales Order then goes to approbation. Can my approbator open the attached file WITHOUT having to open the Sales Order.
Thank you !

Hi Thanh,
There is no such option to open the attached file without opening the sales order the approver has to open the order to check the attachment.
Regards,
Suresh

Similar Messages

Problem with attaching file to Sales Order

Hello,
In my company we have the possibility to attach files to sales orders, e.g. pdf files with the printing details.
These files are added by the GUI user, this works fine.
Now we have an extra order creation stream in which a pdf file has to be added to the SO without user interaction.
I found a helpful link ( /people/rammanohar.tiwari/blog/2005/10/10/generic-object-services-gos--in-background )
This program creates URL links with no problem, but the file generation is not implemented yet.
I tried to add the file functions to his sample report but still have one problem. The file is uploaded, but not reported as a PDF file in sap. If I select the created attachment SAP allows only the saving of the attachment. After saving the created file is a good PDF file, it opens with PDF-viewers.
Why does SAP not know this is a PDF file and report it as such (and open the pdf viewer when selected).
Thanks, Frank.
source-code:
REPORT zzfb_brc                                .
* Report Z_RMTIWARI_ATTACH_DOC_TO_BO
* Written By : Ram Manohar Tiwari
* Function   : We need to maintain links between Business Object and
*              the attachment.Attachment document is basiclally a
*              business object of type 'MESSAGE'.In order to maintain
*              links, first the attachment will be crated as Business
*              Object of type 'MESSAGE' using Message.Create method.
*              Need to check if we can also use FM
*              'SO_DOC_INSERT_WITH_ORIG_API1' or SO_OBJECT_INSERT rather
*              than using Message.Create method.
* I took this program and removed all the parts for adding URL's and
* notes.
* Include for BO macros
INCLUDE : <cntn01>.
* Load class.
CLASS cl_binary_relation DEFINITION LOAD.
CLASS cl_obl_object      DEFINITION LOAD.
PARAMETERS:
* Object_a
   p_botype LIKE obl_s_pbor-typeid DEFAULT 'BUS2032',    "SO
   p_bo_id LIKE obl_s_pbor-instid DEFAULT '0000757830', "example number
* Object_b
   p_docty LIKE obl_s_pbor-typeid DEFAULT 'MESSAGE' NO-DISPLAY,
   p_msgtyp LIKE sofm-doctp        DEFAULT 'EXT'     NO-DISPLAY,
* Relationship
   p_reltyp LIKE mdoblrel-reltype DEFAULT 'ATTA'.
TYPES: BEGIN OF ty_message_key,
        foltp     TYPE so_fol_tp,
        folyr     TYPE so_fol_yr,
        folno     TYPE so_fol_no,
        doctp     TYPE so_doc_tp,
        docyr     TYPE so_doc_yr,
        docno     TYPE so_doc_no,
        fortp     TYPE so_for_tp,
        foryr     TYPE so_for_yr,
        forno     TYPE so_for_no,
       END OF ty_message_key.
DATA : lv_message_key TYPE ty_message_key.
DATA : lo_message TYPE swc_object.
DATA : lt_doc_content TYPE STANDARD TABLE OF soli-line,
       ls_doc_content TYPE soli-line.
* Create an initial instance of BO 'MESSAGE' - to call the
* instance-independent method 'Create'.
swc_create_object lo_message 'MESSAGE' lv_message_key.
* Upload the pdf file, for now from the frontend, in the future from
* the server.
DATA:
* dsn(40) TYPE C VALUE '/usr/sap/trans/convert/1.pdf', "server location
l_lines TYPE i. "filelenght
CALL FUNCTION 'GUI_UPLOAD'
EXPORTING
    filename   = 'c:t1.pdf'
    filetype   = 'BIN'
IMPORTING
    filelength = l_lines
TABLES
    data_tab   = lt_doc_content.
* no exceptions, the file is there in this example
break brouwersf.
** the coding for the server input, for later
*OPEN DATASET dsn FOR INPUT IN BINARY MODE.
*IF sy-subrc <> 0.
* EXIT.
*ENDIF.
*READ DATASET dsn INTO ls_doc_content.
*WHILE sy-subrc EQ 0.
* APPEND ls_doc_content TO lt_doc_content.
* READ DATASET dsn INTO ls_doc_content.
*ENDWHILE.
*CLEAR ls_doc_content.
*CLOSE DATASET dsn.
* define container to pass the parameter values to the method call
* in next step.
swc_container lt_message_container.
* Populate container with parameters for method
swc_set_element lt_message_container 'DOCUMENTTITLE' 'Title'.
swc_set_element lt_message_container 'DOCUMENTLANGU' 'E'.
swc_set_element lt_message_container 'NO_DIALOG'     'X'.
swc_set_element lt_message_container 'DOCUMENTNAME' p_docty.
swc_set_element lt_message_container 'DOCUMENTTYPE' p_msgtyp.
swc_set_element lt_message_container 'DocumentSize'    l_lines.
swc_set_element lt_message_container 'DocumentContent' lt_doc_content.
swc_call_method lo_message 'CREATE' lt_message_container.
* Refresh to get the reference of create 'MESSAGE' object for attachment
swc_refresh_object lo_message.
* Get Key of new object
swc_get_object_key lo_message lv_message_key.
* Now we have attachment as a business object instance. We can now
* attach it to our main business object instance.
* Create main BO object_a
DATA: lo_is_object_a TYPE sibflporb.
lo_is_object_a-instid = p_bo_id.
lo_is_object_a-typeid = p_botype.
lo_is_object_a-catid = 'BO'.
* Create attachment BO object_b
DATA: lo_is_object_b TYPE sibflporb.
lo_is_object_b-instid = lv_message_key.
lo_is_object_b-typeid = p_docty.
lo_is_object_b-catid = 'BO'.
*TRY.
CALL METHOD cl_binary_relation=>create_link
EXPORTING
    is_object_a = lo_is_object_a
    is_object_b = lo_is_object_b
    ip_reltype = p_reltyp.
* Check if everything OK...who cares!!
COMMIT WORK.

Hi,
Welcome to the SDN Forums!!!
You need to supply the PC file extension in the container element 'DOCUMENTTYPE'.
swc_set_element lt_message_container 'DOCUMENTTYPE' p_msgtyp.
In your case change the above statement as below:
swc_set_element lt_message_container 'DOCUMENTTYPE' 'pdf'.
<b>OR</b> change the default value of p_msgtyp to 'PDF'.
Cheers,
Ramki Maley.
Please reward points if the answer is helpful.
For info on awarding points click on this link: https://www.sdn.sap.com/sdn/index.sdn?page=crp_help.htm
Message was edited by: Ramki Maley

How to prepare the Format of Flat file(Excel or Text file) for sales order

Hi All,
My requirement is to prepare the Flat File formats(Excel or Text file) for sales order Conversion using BAPI by COB.
Needed Sample Excel or Text flat file .
Thanks for all.
Regards,
Chowdary
Moderator message : Search for available information. Thread locked.
Your similiar question [Flat files formats|Flat files formats] has been already locked for similiar reason. Read forum rules before posting.
Edited by: Vinod Kumar on Jul 8, 2011 9:36 AM

Hi,
You can use something like this:
switch(cell.getCellType()) {
case Cell.CELL_TYPE_STRING:
    System.out.println(cell.getRichStringCellValue().getString());
    break;
case Cell.CELL_TYPE_NUMERIC:
    if(DateUtil.isCellDateFormatted(cell)) {
      System.out.println(cell.getDateCellValue());
    else {
      System.out.println(cell.getNumericCellValue());
    break;
    case Cell.CELL_TYPE_BOOLEAN:
      System.out.println(cell.getBooleanCellValue());
      break;
    case Cell.CELL_TYPE_FORMULA:
      System.out.println(cell.getCellFormula());
      break;
    default:
      System.out.println();
Hope it helps,
Daniel

Tab Separated file for Sales Order creation

Hi,
I am creating a Z Report which intern calls BAPI BAPI_SALESORDER_CREATEFROMDAT2 for creating Sales Orders.
Sales Order details I am giving through Tab Separated File which contains all details like
   1) Header Details
   2) Partner Details
   3) Item Details.
Can any one tell what is the process to convert this file to into Internal Table.....

This Example is only for three column. If there are more column you can check
"LOOP AT intern.
    IF intern-col = *. " * is coulmn number
CALL FUNCTION 'ALSM_EXCEL_TO_INTERNAL_TABLE'
       EXPORTING
            filename                = filename
            i_begin_col             = 1
            i_begin_row             = 1
            i_end_col               = 3
            i_end_row               = 65000
       TABLES
            intern                  = intern
       EXCEPTIONS
            inconsistent_parameters = 1
            upload_ole              = 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.
LOOP AT intern.
    IF intern-col = '1'.
      l_length = strlen( intern-value ).
      IF l_length > 10.
        l_flag = 'E'.
        wa_error-vbeln = intern-value.
        wa_error-message = 'Invalid Sales Order'.
        CONTINUE.
      ELSE.
        CALL FUNCTION 'CONVERSION_EXIT_ALPHA_INPUT'
             EXPORTING
                  input = intern-value
             IMPORTING
                  output = wa_vbeln-vbeln.
        CONTINUE.
      ENDIF.
    ELSEIF intern-col = '2'.
      IF l_flag = 'E'.
        wa_error-posnr = intern-value.
      ELSE.
        CLEAR : l_length.
        l_length = strlen( intern-value ).
        IF l_length > 6.
          wa_error-vbeln = wa_vbeln-vbeln.
          wa_error-posnr = intern-value.
          wa_error-message = 'Invalid item Number'.
          l_flag = 'E'.
        ELSE.
          wa_vbeln-posnr = intern-value.
          APPEND wa_vbeln TO i_vbeln.
          CLEAR : intern,wa_vbeln,l_flag,l_length.
        ENDIF.
      ENDIF.
    ELSEIF intern-col = '3'.
      CLEAR : wa_noti.
      wa_noti-aufnr = intern-value.
      APPEND wa_noti TO i_noti.
      CLEAR : wa_noti.
    ENDIF.
ENDLOOP.

How to configure rescheduling for sale order quantities

kindly explain how to configure rescheduling for sale order quantities that are created last month. kindly explain. i am in urgent.
regards,
g.v.shivakkumar

Hi,
Short text
Rescheduling sales and stock transfer documents: by material
Description
The 'Rescheduling' program (SDV03V02) processes sales document items that are contained in the item directory for the material. It takes into consideration open items and schedule lines from stock transfer items, stock transfer scheduling agreements and purchase order requests (items only), referred to hereafter as stock transfer documents, for the materials.
All sales documents for the material that are still open are selected. This means that the material index must be activated for at least all sales document types, whose items may have requirements. All stock transfer documents or items for the material that are still open are also selected. Open in this case means for example, that there is no deletion indicator, that the item from a stock transfer purchase order request cannot be labeled as completed or that the quantity delivered and posted to goods issue for the item in a stock transfer purchase order is the same as the amount ordered. An availability check can only be carried out if a checking rule is assigned to the document type - if this is not the case, the document or document item is not checked.
Checking rule 'A' is used as a basis for rescheduling sales orders (exceptions to this are rush orders they use checking rule B, and orders with individual customer stock; they use checking rule AE). Stock transfer documents use the checking rule that is assigned in Customizing for Purchasing. It is important that the scope of checks is consistent for both the stock transfer documents and the sales documents and that they do not exclude each other, as this can lead to incorrect test results. An example of an incorrect setting would be: The scope of check for checking rule 'A' checks delivery schedules for stock transfer purchase orders and stock transfer purchase requests, however the scope of check for the checking rule for the stock transport scheduling agreement does not.
The items and schedule lines found in the selection are sorted according to 'Priorities' - document category, delivery priority, creation date of the item or schedule line (for stock transfer purchase orders and delivery plans) entered on the selection screen or according to the schedule line date of the earliest schedule line with order quantity, document number and item number and then transferred to the availability check. Priority 1 is highest priority and priority 5 the lowest. Stock transfer purchase order requests are sorted after stock transfer purchase orders and scheduling agreements, as they are less binding. This means that when you have identical sort criteria such as delivery dates, the stock transfer purchase order item is checked first and then the item from the stock transfer purchase order request.
The preset option 'Unconfirmed documents required' only carries out rescheduling for materials for which there is at least one unconfirmed transaction.
You can use the parameters 'Sorting criteria delivery date' to define whether sorting is carried out with the order quantity after the creation date of the item or the delivery date of the earliest schedule line.
If you mark the 'Simulation' field, the checked documents are not saved. Instead a results list is generated and saved. However, the availability check for the corresponding documents continues as if saving has taken place already, that is, that the simulated list corresponds to the actual one.
Under 'Options' on the selection screen, specify whether sales documents and/or stock transfer documents should be processed. For stock transfer documents you can enter whether stock transfer purchase orders and scheduling agreements should be processed at item or schedule line level:
Processing at item level:
All open schedule lines for the item are read and collected, then transferred to the availability check. To sort and prioritize documents, you do not need each individual schedule line. It is sufficient to have the item or data from the first schedule line. All open schedule lines for the item are processed and checked.
Example of processing at item level:
Sorting: Date (Delivery date first schedule line) - Document number - Document item
Doc. cat. Doc. number Doc. item Doc. schedule line Delivery date PO        4500000012      10               0001              26.01. PO        4500000012      10               0002              26.02. PO        4500000025      20               0001              28.01. PO        4500000025      20               0002              02.02.
You can see that the second schedule line for document 4500000025/20 from 02.02 was processed after the second schedule line for document 4500000012/10 from 26.02. This is because all open schedule lines for an item are read and processed. The first schedule line from 4500000012/10 has the earliest delivery date, therefore it has priority.
Processing at schedule line level:
Each open schedule line for an item is entered in document sorting in accordance with the values entered under 'Priorities'. The availability check is carried out for each individual schedule line.
Example for processing at schedule line level:
Sorting: Date (delivery date first schedule line) - document number -document item
Doc. cat.    Doc. number Doc. item Doc. sched. line Del. date PO           4500000012    10             0001           26.01. PO           4500000025    20             0001           28.01. PO           4500000025    20             0002           02.02. PO           4500000012    10             0002           26.02.
Here you can see that each schedule line was sorted according to its delivery date. Note that this type of processing requires more runtime due to the individual checks and more frequent saving.
The results of rescheduling are saved, as long as the program was not started in simulation mode. When calling up from the 'Sales' area menu or when directly starting via the development environment, the iniator is informed via a dialog box that he has just started a process that changes data. He can then decide whether or not he wants to continue.
Checking procedure for stock transfer documents:
An availability check of stock transfer documents in rescheduling is carried out in accordance with the check carried out when manually creating a document. If, however, the required quantity for a schedule line is not available on a particular date and will not be ready until later, new schedule lines are created for the stock transfer purchase orders and scheduling agreements, containing the relevant data. New items are created in this case for stock transfer purchase order requirements. The total sum of schedule line quantities for a processed schedule line corresponds to the schedule line quantity of the original schedule line.
First example: Using a stock transfer purchase order item with a schedule line:
a) Status of item before rescheduling run:
Del. date PO quantity   Confirmed quant Confirmed del. date 23.07.      50 items       0 items              -
==> This now affects the stock/requirement situation:
    - Goods issue is posted for the material in the delivering plant on the 23.07.
    - A purchase order of 10 items was created for the material in the delivering plant. Delivery is expected on the 29.07.
b) Status of stock transfer purchase order item after rescheduling run:
Del. date PO quantity   Confirmed quant   Confirmed del. date 23.07.     40 items      40 items            23.07. 29.07.     10 items      10 items            29.07.
==> The first schedule line was changed in accordance with the results of the rescheduling availability check. Only 40 of the 50 original items could be delivered on the 23.07. Therefore, a new schedule line is created for the rest on the 29.07. for 10 confirmed items.
Second example: Same output situation as the above example.
==> There is now a change in the requirement/stock situation:
A purchase order for 10 items is created for the material in the delivering plant. Delivery is expected on the 29.07. A further purchase shows another 40 planned items on the 30.07.
   Status of stock transfer purchase order item after rescheduling run:
Del. date PO quantity Confirmed quant Confirmed del. date 29.07.     10 items       10 items          29.07. 30.07.     40 items       40 items          30.07.
==> The first schedule line was changed in accordance with the result of the availability check for rescheduling. The original delivery date is set to the date confirmed in the ATP check. A new schedule line is created for the remaining 40 items, that are available on the 30.07.
Note:
Any set fixed delivery date and quantity indicators and creation indicators for schedule lines or items are 'inherited' by newly created schedule lines. Assuming that the original schedule line was fixed in the above example (since it is created manually), this indicator is also set for the newly created schedule line.
If shipping scheduling is activated for a stock transfer document type, this is also implemented for newly created schedule lines, with the exception of route schedule determination. This means that in the current version of the program no route schedule has been determined for a schedule line containing a route schedule for which new schedule lines may need to be created.
The results of the run are issued in the form of a list, which is also saved, so that the results can be controlled at a later date. This is done using the function 'Evaluate rescheduling', but it is only a good idea to do this after the first rescheduling has taken place. You can restrict selection requirements but these can however affect the runtime. You can use this function to analyze the saved list until the next rescheduling run, which writes over the result. If you start rescheduling in the background, a spool file with the result list referred to will be created in the corresponding setting. You can see this in spool management.
Output
A list of changed documents, a list of documents in which an error occurred during processing and as a result were not changed, can be called up via the menu 'Edit - Error log'. If in a subsequent evaluation a restricted selection is carried out, a note appears at the end of the list to say that not all document items are displayed.
You can set the scope of the list under the menu option 'List' in the list display. You can view improvements, deteriorations and the whole list. Before the documents can be included in one or either of the restricted lists, the date or quantity has to have changed so that the item can be contained in both the list of improved or deteriorated documents.
You can use the interface for changing transactions and the order list to navigate. Use 'Back' to exit the list and 'New selection' to return to the selection screen.
Recommendation
You should only start this program occasionally and use very restricted selectin criteria during working hours as it requires enormous system resources.
Note
The columns for 'New date' and 'New confirmed qty' only contain entries if the dates or quantities have changed.
As the system only runs the change check (dates/quantities) per line in the original list, an item whose backlog has increased in the list of improvements. This occurs, for example, if the whole quantity can be delivered at once but at a later date. In this situation, the system determines an increase for the line when it compares quantities.
Regards,
Amrish Purohit

SAP Mobile Sales 2.0 delta load issue for Sales Orders

Hello,
we have used Mobile Sales 2.0 with a Windows app for a while now. Our current issue is that sales reps won't see any historical sales order data on their devices.
Background
Due customer requirements, we need to make small changes to customer master data attributes and reload all customers from ERP to CRM. Then we ran delta loads (MAS_PARTNER followed by all other objects) to DOE, in which virtually all 5000+ customer accounts were compared. The delta load ran for about 3 days (some performance bottleneck we haven't located yet).
During the delta load, data on devices was inconsistent. Accounts were missing and all transaction data disappeared. After the delta loads, all accounts and contacts are OK, save for a few. Data from activities (appointments, tasks) have reappeared, as they should. Only sales orders won't reappear. The sales orders exist in the backend and belong to active accounts and sales reps.
Settings and troubleshooting so far
We don't have any limitations for sales orders in CRM Sales Mobile configuration.
We've run delta loads for all objects in transaction SDOE_LOAD.
MAS_CUSTOMIZATION etc seem fine.
We've re-run initial load for sales orders from CRM.
In the test system, we've even reinitialized the whole CDS database on DOE and on the devices, then re-ran the loads.
Checked steps suggested in discussion
SAP CRM 2.0 initial load issue
Historical sales orders (those created before the master data reload) exist in the backend, but don't show up on the device.
If I change one of those historical sales orders in the backend, it gets sent to the device.
If I create a new sales order in the backend or on the device, it is saved and replicated just fine.
To sum it up, it seems DOE is unable to identify the sales orders relevant for replication.

First Doubt i got clarify by my self as we can go with Unwired Runtime option .
But i still have doubt in :
2. How can i Modifying the Main Menu for iOS.
i am able to customize the same for windows using files SybaseCRM.Configuration.xml file.
Same how can i do for iphone/ipad.

Inbound Files Create Sales Order With Reference To Quotation

Dear All,
I am working one Assignments For Sales Order Creation Through Inbound Files and Its working fine.
But I have one Issue during creation of Sales Order through inbound files ( Which Contains Quotation Number Which Already Exist in SAP ) and Quotation Number updated in PO Number (BSTKD) filed in Sales Order.
And My Problem is How we can update Quotation in Document Flow during creation of Sales Order through inbound files..
Any Help or Suggestion will very helpful for me.
Thanx in Advance.
Regards
Vijay Maurya

Dear All,
I am working one Assignments For Sales Order Creation Through Inbound Files and Its working fine.
But I have one Issue during creation of Sales Order through inbound files ( Which Contains Quotation Number Which Already Exist in SAP ) and Quotation Number updated in PO Number (BSTKD) filed in Sales Order.
And My Problem is How we can update Quotation in Document Flow during creation of Sales Order through inbound files..
Any Help or Suggestion will very helpful for me.
Thanx in Advance.
Regards
Vijay Maurya

Driver program for sales order in smartforms?

whatst he driver prog for sales order in smartforms?
how to attach my smart form to driver prog
thanks & regards
lakshmi

Hi,
Driver Program is the program which is used to link the form and the ABAP program.
U have to use the FM 'SSF_FUNCTION_MODULE_NAME' to give the form name.
Here 'Z_TRNG_SMART_MUL_PURCH_T012' is the form name.
sf_formname = 'Z_TRNG_SMART_MUL_PURCH_T012'.
CALL FUNCTION 'SSF_FUNCTION_MODULE_NAME'
    EXPORTING
      formname           = sf_formname
    IMPORTING
      fm_name            = sf_fm_name
    EXCEPTIONS
      no_form            = 1
      no_function_module = 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.
CALL FUNCTION sf_fm_name
    EXPORTING
ARCHIVE_INDEX              =
ARCHIVE_INDEX_TAB          =
ARCHIVE_PARAMETERS         =
CONTROL_PARAMETERS         =
MAIL_APPL_OBJ              =
MAIL_RECIPIENT             =
MAIL_SENDER                =
OUTPUT_OPTIONS             =
USER_SETTINGS              = 'X'
      v_ekpo                     = v_ekpo
     v_adrnr              = v_adrnr
IMPORTING
DOCUMENT_OUTPUT_INFO       =
JOB_OUTPUT_INFO            =
JOB_OUTPUT_OPTIONS         =
    TABLES
      it_ekko                    = it_ekko
      it_ekpo                    = it_ekpo
EXCEPTIONS
FORMATTING_ERROR           = 1
INTERNAL_ERROR             = 2
SEND_ERROR                 = 3
USER_CANCELED              = 4
OTHERS                     = 5
IF sy-subrc <> 0.
MESSAGE ID SY-MSGID TYPE SY-MSGTY NUMBER SY-MSGNO
        WITH SY-MSGV1 SY-MSGV2 SY-MSGV3 SY-MSGV4.
ENDIF.
Thanks & Regards,
Roja Velagapudi.

Attach document in sales order

HI
how to attach document in sales order

Dear SAP SD,
Please refer my Suggestion:
Re: Attaching a document
and
Re: Sending attatchment with PO
Best Regards,
Amit
Note: Also, try with:
VA02 --> Extras (menu-bar) --> Outout --> Header --> Edit
First maintain your Output Type (for sales Order) and then select the Output line and Click Tab: Communication method.
Now, Top left, you will see Icon: Attachment.
Click and Attach your document

Inbound Files Create Sales Order

Dear All,
I am working one Assignments For Sales Order Creation Through Inbound Files and Its working fine.
But I have one Issue during creation of Sales Order through inbound files ( Which Contains Quotation Number Which Already Exist in SAP ) and Quotation Number updated in PO Number (BSTKD) filed in Sales Order.
And My Problem is How we can update Quotation in Document Flow during creation of Sales Order through inbound files..
Any Help or Suggestion will very helpful for me.
Thanx in Advance.
Regards
Vijay Maurya

HI Vijay,
Could you please let me know, how are you processing the file to make sales order. In other words are you using BDC or something else for creating sales order.
If you are using a BDC to create sales order, you need to re-record it so that the sales order is created in reference to the quotation. In this way, the sales order will automatically get linked to sales order. And all the document flows will be updated, also the issues of pricing, delivery date will also be perfectly copied.
Also since the SAP will update the tables on its own, hence you will not need to direct update any table in SAP.
Hope this helps,
Abhishek
Edited by: Abhishek Purwar on Nov 20, 2008 9:11 PM

Adding a new search criteria in Web UI for Sales Order

Hi,
We have a requirement for Web UI as follows :
We want to add the ID number (identification number in BP ) as search criteria for Sales Order simialr to search criteria available in Accounts with ID number .
Can any one please give some inputs on this ?
Regards
Vinayak

Hi Vinayak,
I will try to give you some technical advise.
What you would need to do is:
In transaction SM30 open up view: CRMV_OBJ_BTIL
There is an entry for External Object Name "BTQAct"
The currently used DDIC structure is CRMST_QUERY_ACT_BTIL
You will need to adjust this structure to bring completely new parameters to the UI. This means put in your own.
As you can see in detail for this entry there are three fields with name "Structure" the last one is for the GenIL handler class. Currently it should be empty (there is some fancy SAP logic to determine it automatically). You can override it with your own handler class implementing the logic. As a hint: The implementation class currently used is: CL_CRM_QACT_RUN_BTIL
Anyhow most 1Order searches are handled by the class CL_CRM_Q1O_SEARCH perhaps you can use it as well. Additionally it would be a good idea to provide your users with a value help.
Oh and there is a customizing that lets you define which options (IS, BETWEEN, IS NOT, ...) should be available for the user. Please do not try to do this hardcoded
cheers Carsten

Quality inspection for the items issued for Sales order

Hi, How to map the qc for the items issued for sales order?

Dear Yadav,
-Activate insp type 10 in the Material Master-QM view insp setup (MM01)
-Create Inspection plan (QP01) with usage as Goods issue & assign Insp characteristics
-Create Sales order (VA01)
-Delivery against the Sales order (VL01N) or through sales order menu. Delivery Insp lot gets created after Delivery is made.
-Do results recording and take usage decision (QA32)
Note:
-This inspection is non stock relevant inspection. There will be no stock posting through Quality Management.
-Post Goods issue in the delivery can be made only after taking the usage decision.
Regards,
Keerthi.

Outbound message control for sales order SISCSO.

Hi...
I am trying to generate IDoc for Sales order using message control. The IDoc of type SISCSO is getting generated as per the requirement.
I want to calculate certain things before generating IDocs. I have done the following configurations:
1. A function module 'ZIDOC_OUTPUT_SALES_ORD' is created with interface same as 'IDOC_OUTPUT_ORDRSP'. (Where i am planning to write a code)
2. WE57 where Function module is assigned to SISCSO as outbound FM.
No BD51 is done as it is only for inbound process.
3. New process code ZSO is created through WE41, which is made message independent and FM created in step 1 is assigned to it.
4. In WE20 , this process code is attached to V1 type of application under message control.
Still, my FM is not getting called... I have checked it by applying Break point as well as raising exception in the FM. But still it's not working..
Where am i going wrong??
Can anybody suggest solution??
Thanks,
Audy.

Hi,
You need to use FM : MASTER_IDOC_DISTRIBUTE to create outbound idoc.fill the data in the tables EDIDC,EDIDD and generate the IDOC.
check this link:
Re: Master_IDoc_Distribute
and use transaction : WEDI for IDOC configurations.
here you will have all the transactions(step by step) to set the outbound IDOC configurations.
Regards
Appana

SP Need for sales order UDF

Hi all,
I am created UDF attachment link in Sale order once attachment done it will raise the A/R invoice template.
Option copy from sale order to AR invoice should be block in store procedure
" Without attachment A/R invoice should not raise"
How to write Store procedure transaction in SQL

Hi Ranjith,
try this one...
for Line UDF
IF (@object_type = '13') and (@transaction_type IN ('A', 'U'))
BEGIN
     IF EXISTS (SELECT T0.Docentry from OINV T0 Inner Join INV1 T1 ON T0.Docentry=T1.Docentry where
     T1.DocEntry = @list_of_cols_val_tab_del and (T1.[YOUR_UDF] is null or T1.[YOUR_UDF] ='' ))
     BEGIN
          Select @error = 10, @error_message = 'Sales Invoice cannot be raise W/O sales Order attachement'
     END
END
for Header UDF
IF (@object_type = '13') and (@transaction_type IN ('A', 'U'))
BEGIN
     IF EXISTS (SELECT T0.Docentry from OINV T0 where
     T0.DocEntry = @list_of_cols_val_tab_del and (T0.[YOUR_UDF] is null or T0.[YOUR_UDF] ='' ))
     BEGIN
          Select @error = 10, @error_message = 'Sales Invoice cannot be raise W/O sales Order attachement'
     END
END
regards,
Fidel

Outbound IDOC BW to R/3 for sales order information

Hello everybody,
is there someone, who has any experience with transferring data (sales order data) <b>from BW to R/3</b> via IDOC.
The customer has already implemented an EDI interface for R/3 via IDOC for generating sales orders. This IDOC interface should be used also for transferring BW data to R/3. So BAPI and flatfile interface BW-R/3 is not favored!
Is there any good documentation how to proceed which can be provided to me?
In particular i am interested how to create a function module to fill an IDOC structure from a standard data base table in BW (ODS table), how to create new message types etc.
Thanks in advance
Gunnar

Is it possible in general?
Yes, theoretically at least.
You do not have SAP standard IDOCs (ORDERS*) for Sales Orders, neither is the functions or message types etc available on BW system. This would mean you will have to create custom idocs/message-type/process-code and configuration setup. In addition, if you are going to read data from a cube (to create the orders), it is going to be a slow and painful work.
Another option, if you do have to create sales order IDOCs, would be to extract order data from BW to a , say Infospoke file, on BW. You can process this file in R/3 system to create/post a sales order idoc. This would help as the necessary components (eg sales order IDOC) are available there already. If you need help on that (creating sales order IDOC or BAPI posting, from a file), ABAP forum would be more helpful.

View attached files for Sales Order in Approbation.

Similar Messages

Maybe you are looking for