Hi Sanjeev : Validating PO during the creation of Sales Orders

Hi Sanjeev,
Thank you very much for helping me out in this problem.Still I haven't got the solution.
I tested the above mentioned configuration option by putting the Check Purchase Order Number field to 'A' in the transaction VOV8. But while creating sales orders, it is giving only information message. Is there any other way, to restrict the Duplicate PO value through configuration setup.
can you also explain how to use Enqueue and Dequeue FMs in the inbound posting function module.
Regards,
Madhusudan.

Hi
This is in customizing transaction SPRO -> SALES & DIST -> SALES -> SALES DOCUMENTS -> DEFINE VARIABLE MESSAGES.
I am pasting the help from customizing note
Define Variable Messages
Various checks are carried out during scheduling agreement processing with releases in the component supplier industry. Depending on the result of the check, the system can issue a warning or an error message. In this menu option, you can define which system response is to be linked to a particular message text.
Depending on the component supplier, you can specify whether certain system messages are to be sent as errors, as warning messages or not at all. By specifying a version, system responses can be specified by component supplier.
Example
When a forecast delivery schedule is created, the system compares the cumulative received quantities of the customer with the cumulative received quantities in the document flow at the time at which the delivery note was created. You can configure the system to issue an error message if these do not correspond.
Standard system
Two system responses can be configured in the standard system:
The message appears as a warning.
The message appears as an error.
In the standard system the messages are configured to appear as warnings.
Actions
1. Enter a message class and the message text and specify the system response.
2. If you want to use different versions for certain component suppliers, you copy a message and enter a version number together with the required system response.

Similar Messages

Need of User-Exit in the creation of Sales Order(VA01)

Hi,
In the creation of Sales Order, I need to Compare the Ordered Quantity and Confirmed Quantity. If the CQ is less than OQ I need to create one more line item with the same material for the rest of the quantity and send the request to Production order for the remaining quantity. For this I am unable to get the exact exit. Please help me in this regard ASAP.
Thank you.

the following program are the user exit for billing.
we often use RV60AFZC and RV60AFZZ.
RV60AFZA
RV60AFZB
RV60AFZC
RV60AFZD
RV60AFZZ
RV60BFZA
For Sales order
Pricing, item addtion deletion
MV45AFZZ
First, I did not find documentation for the BADI either. But at the first glance the process of implementing it looks quite straightforward. I assume you run R/3 Enterprise (4.7). So, you should implement BADI 'BADI_SD_SALES' - this must be done in transaction SE19. In particular for the purpose of adding some additional items into sales document I would implement method SAVE_DOCUMENT_PREPARE. This method has changing table parameter FXVBAP of type VA_VBAPVB_T - it holds all the sales document items. Just add items of yours to it. Certainly, you have to fill all the appropriate fields carefully.
Hope this helps somehow.
In that case you should use USEREXIT_DOCUMENT_SAVE_PREPARE subroutine (form). As far as I remember it has no parameters. To add items to the sales document you should modify internal table XVBAP.
regards
vinod

Problem regarding the creation of sales order using bapi.

Hai all,
I am creating sales order using bapi but i am, get following error messages :
TYPE ID NUMBER MESSAGE
E       VP   112       Please enter sold-to party or ship-to party
E       V4   219       Sales document was not changed
I have entered all the parameters.
my program is as follows :
*& Report ZSD_SALES_ORDER
REPORT ZSD_SALES_ORDER.
    Tables
*table definitions
TABLES:vbak,      "Sales Document: Header Data
        knvv,     "Customer Master Sales Data
        mara,     "General Material Data
        t001l,    "Plants/Branches
        mvke,     "Sales Data for Material
        vbap,     "Sales Document: Item Data
        konv.     "Conditions (Transaction Data)
    Types
*type for upload data
TYPES :BEGIN OF ty_upload,
       matnr(20) TYPE c,                  " Old material number
       quantity(20) TYPE c,               " Cumulative order quantity in sales units
VALUE TYPE       BAPIKWERT1,
      value(20) TYPE c,                  " Condition value
             value TYPE konv-kwert,                  " Condition value
END OF ty_upload.
*type for final output table
TYPES :BEGIN OF ty_main,
           bismt TYPE mara-bismt,    "Old material number
           matnr TYPE vbap-matnr,    "Material Number
           kunnr TYPE vbak-kunnr,    "customer number
           auart TYPE vbak-auart,    "Sales Document Type
           vkorg TYPE vbak-vkorg,    "Sales Organization
           vtweg TYPE vbak-vtweg,    "Distribution Channel
           spart TYPE vbak-spart,    "Division
           vbeln TYPE vbak-vbeln,    "Sales document
           werks TYPE marc-werks,    " Plant
           lgort TYPE mard-lgort,    "Storage Location
           posnr TYPE vbap-posnr,    "Sales Document Item
           parvw TYPE vbpa-parvw,    "Partner function
           kwmeng TYPE vbap-kwmeng,   "Cumulative order quantity in sales units
           kschl TYPE konv-kschl,    "Condition type
          kwert TYPE konv-kwert,    "Condition value
KWERT TYPE       BAPIKWERT1,
          kwert(20) TYPE c,    "Condition value
           waers TYPE konv-waers,    "Currency
     END OF ty_main.
*type for old material number
TYPES: BEGIN OF ty_matnr,
       matnr TYPE mara-matnr,
       bismt TYPE mara-bismt,
       END OF ty_matnr.
*type for order number
TYPES :BEGIN OF ty_output,
       vbeln TYPE vbak-vbeln,       "Sales Document
     END OF ty_output.
    Constants                Begin with C_                           *
CONSTANTS:
c_zpmu(4) TYPE c VALUE 'ZPMU',
c_zpmm(4) TYPE c VALUE 'ZPMM'.
DATA: c_ch(1) TYPE c VALUE 'X'.
    Data                     Begin with W_                           *
*global data for validations
DATA: w_count TYPE i,
      w_vkorg TYPE vbak-vkorg,
      w_vtweg TYPE vbak-vtweg,
      w_spart TYPE vbak-spart,
      w_werks TYPE t001l-werks,
      w_check TYPE c,
      w_itemno TYPE posnr_va,
     W_COND TYPE C.
      w_cond(3) TYPE c.
    Internal tables          Begin with IT_                          *
*internal table definitions
DATA : it_upload TYPE STANDARD TABLE OF ty_upload ,
       wa_upload TYPE ty_upload.
DATA : it_main TYPE STANDARD TABLE OF ty_main,
       wa_main TYPE ty_main.
DATA: it_matnr TYPE STANDARD TABLE OF ty_matnr,
      wa_matnr TYPE ty_matnr.
DATA : it_output TYPE STANDARD TABLE OF ty_output.
Internal table for BAPI.
DATA: it_bapisdhd1 TYPE STANDARD TABLE OF bapisdhd1,        "Sales and Distribution Document Header
      wa_bapisdhd1 TYPE bapisdhd1.
DATA: it_bapisditm TYPE STANDARD TABLE OF bapisditm ,       "Sales and Distribution Document Item
      wa_bapisditm TYPE bapisditm.
DATA: it_bapiparnr TYPE STANDARD TABLE OF bapiparnr,        "SD Document Partner: WWW
      wa_bapiparnr TYPE bapiparnr.
DATA: it_bapischdl TYPE STANDARD TABLE OF bapischdl,       "Schedule Lines
      wa_bapischdl TYPE bapischdl.
DATA: it_bapicond TYPE STANDARD TABLE OF bapicond,       "Communication Fields for Maintaining Conditions in the Order
      wa_bapicond TYPE bapicond.
DATA: it_bapiret2 TYPE STANDARD TABLE OF bapiret2,        "Return Parameter
      wa_bapiret2 TYPE bapiret2.
      Parameters              Begin with PR_                        *
*selection screen definition
SELECTION-SCREEN BEGIN OF BLOCK blk1 WITH FRAME .
PARAMETERS: pr_vkorg TYPE vbak-vkorg OBLIGATORY,
            pr_vtweg TYPE vbak-vtweg OBLIGATORY,
            pr_spart TYPE vbak-spart OBLIGATORY,
            pr_kunnr TYPE kna1-kunnr OBLIGATORY,
            pr_werks TYPE marc-werks OBLIGATORY,
            pr_lgort TYPE mard-lgort OBLIGATORY.
PARAMETERS: pr_auart TYPE vbak-auart OBLIGATORY,
           PR_AUGRU TYPE VBAK-AUGRU OBLIGATORY.
                        pr_augru TYPE vbak-augru.
SELECTION-SCREEN END OF BLOCK blk1.
SELECTION-SCREEN BEGIN OF BLOCK blk2 WITH FRAME.
PARAMETERS : pr_file TYPE ibipparms-path OBLIGATORY.
SELECTION-SCREEN END OF BLOCK blk2.
      At selection-screen                                           *
AT SELECTION-SCREEN.
PERFORM f006_validate_vkorg.
PERFORM f007_validate_vtweg.
PERFORM f008_validate_spart.
PERFORM f009_validate_kunnr.
PERFORM f010_validate_werks.
PERFORM f011_validate_lgort.
AT SELECTION-SCREEN ON VALUE-REQUEST FOR pr_file.
*for f4 help----
PERFORM f003_f4_help.
      S T A R T   O F   S E L E C T I O N                           *
START-OF-SELECTION.
*for material ,quantity and value upload
PERFORM f001_upload_file.
*get data
PERFORM f003_get_data.
*for check the data
PERFORM f002_check_data .
PERFORM f004_process.
*for posting
PERFORM f005_posting.
END-OF-SELECTION.
      E N D       O F   S E L E C T I O N                           *
*&      Form f001_upload_file
      upload file
FORM f001_upload_file .
DATA : lw_fname TYPE string.
CLEAR lw_fname.
lw_fname = pr_file.
REFRESH it_upload.
CALL FUNCTION 'GUI_UPLOAD'
    EXPORTING
      filename                = lw_fname
      filetype                = 'ASC'
      has_field_separator     = c_ch
    TABLES
      data_tab                = it_upload
    EXCEPTIONS
      file_open_error         = 1
      file_read_error         = 2
      no_batch                = 3
      gui_refuse_filetransfer = 4
      invalid_type            = 5
      no_authority            = 6
      unknown_error           = 7
      bad_data_format         = 8
      header_not_allowed      = 9
      separator_not_allowed   = 10
      header_too_long         = 11
      unknown_dp_error        = 12
      access_denied           = 13
      dp_out_of_memory        = 14
      disk_full               = 15
      dp_timeout              = 16
      OTHERS                  = 17.
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 it_upload INTO wa_upload.
   wa_upload-value = ( wa_upload-value ) / 10.
   MODIFY it_upload FROM wa_upload.
ENDLOOP.
ENDFORM.                    "F001_UPLOAD_FILE
*&      Form f003_f4_help
      f4 help
FORM f003_f4_help .
CALL FUNCTION 'F4_FILENAME'
    EXPORTING
      program_name = syst-cprog
      dynpro_number = syst-dynnr
      field_name    = ' '
    IMPORTING
      file_name     = pr_file.
ENDFORM.                    " f003_f4_help
*&      Form check_data
      text
FORM f002_check_data .
DATA: lw_lines TYPE i.
DESCRIBE TABLE it_main LINES lw_lines.
IF lw_lines LE 0.
    RETURN.
ENDIF.
SELECT a~matnr
         a~bismt FROM mara AS a INNER JOIN mvke AS b
               ON amatnr = bmatnr
               INTO CORRESPONDING FIELDS OF TABLE it_matnr
               FOR ALL ENTRIES IN it_main
               WHERE a~bismt = it_main-bismt.
IF sy-subrc = 0.
    LOOP AT it_main INTO wa_main.
      CLEAR : wa_matnr.
      READ TABLE it_matnr INTO wa_matnr WITH KEY bismt = wa_main-bismt.
      IF sy-subrc = 0.
        MOVE: wa_matnr-matnr TO wa_main-matnr.
      ENDIF.
      MODIFY it_main FROM wa_main TRANSPORTING matnr WHERE bismt = wa_main-bismt.
    ENDLOOP.
ELSE.
   MESSAGE e000(zmsd) WITH text-001.
ENDIF.
ENDFORM.                    "CHECK_DATA
*&      Form F009_validate_vkorg
      text
FORM f006_validate_vkorg .
CLEAR w_vkorg.
SELECT SINGLE vkorg
      INTO w_vkorg FROM tvko
      WHERE vkorg EQ pr_vkorg.
IF sy-subrc <> 0.
    MESSAGE e000(zmsd) WITH text-012 pr_vkorg.
ENDIF.
ENDFORM.                    " F009_validate_vkorg
*&      Form f007_validate_vtweg
      text
FORM f007_validate_vtweg .
CLEAR:w_vtweg.
SELECT SINGLE vtweg
       INTO w_vtweg FROM tvtw
       WHERE vtweg EQ pr_vtweg.
IF sy-subrc <> 0.
    MESSAGE e089(zmsd).
ENDIF.
ENDFORM.                    " f007_validate_vtweg
*&      Form f008_validate_spart
      text
FORM f008_validate_spart .
CLEAR:w_spart.
SELECT SINGLE spart
        INTO w_spart FROM tspa
        WHERE spart EQ pr_spart.
IF sy-subrc <> 0.
    MESSAGE e087(zmsd).
ENDIF.
ENDFORM.                    " f008_validate_spart
*&      Form F010_validate_kunnr
      text
FORM f009_validate_kunnr .
DATA: l_kunnr TYPE kunnr.
CLEAR: w_vkorg, w_vtweg,w_spart.
SELECT SINGLE kunnr FROM knvv
         INTO l_kunnr
         WHERE kunnr = pr_kunnr
         AND    vkorg = pr_vkorg
         AND    vtweg = pr_vtweg
         AND    spart = pr_spart.
IF sy-subrc <> 0.
   MESSAGE e000(zmsd) WITH text-010 pr_kunnr text-011 pr_vkorg .
ENDIF.
ENDFORM.                    " F010_validate_kunnr
*&      Form f010_validate_werks
      text
FORM f010_validate_werks .
CLEAR:w_werks.
SELECT SINGLE werks
        INTO w_werks FROM t001w
        WHERE werks EQ pr_werks.
IF sy-subrc <> 0.
    MESSAGE e088(zmsd).
ENDIF.
ENDFORM.                    " f010_validate_werks
*&      Form F011_validate_lgort
      text
FORM f011_validate_lgort .
CLEAR:w_werks .
SELECT   SINGLE werks FROM t001l
         INTO w_werks
         WHERE werks = pr_werks
         AND    lgort = pr_lgort.
IF sy-subrc <> 0.
    MESSAGE e000(zmsd) WITH text-007 pr_lgort text-008 pr_werks .
ENDIF.
ENDFORM.                    " F011_validate_lgort
*&      Form f003_get_data
      text
FORM f003_get_data .
CLEAR wa_main.
REFRESH it_main.
LOOP AT it_upload INTO wa_upload.
    CLEAR : wa_main.
    MOVE: wa_upload-matnr     TO wa_main-bismt,
          wa_upload-quantity TO wa_main-kwmeng,
          wa_upload-value     TO wa_main-kwert,
          pr_vkorg            TO wa_main-vkorg,
          pr_vtweg            TO wa_main-vtweg,
          pr_spart            TO wa_main-spart,
          pr_kunnr            TO wa_main-kunnr,
          pr_werks            TO wa_main-werks,
          pr_lgort            TO wa_main-lgort.
    APPEND wa_main TO it_main.
ENDLOOP.
ENDFORM.                    " f003_get_data
*&      Form f004_process
      text
FORM f004_process .
CLEAR w_check.
LOOP AT it_main INTO wa_main.
   IF wa_main-matnr = ''.
     WRITE:/ text-006,
                 wa_main-bismt.
     w_check = 1.
   ENDIF.
   IF wa_main-kwmeng = 0.
     WRITE:/ text-005,
             wa_main-bismt.
     w_check = 1.
   ENDIF.
   IF    pr_auart <> 'ZM01'.
     IF wa_main-kwert IS INITIAL.
       WRITE:/ text-004,
                wa_main-bismt.
       w_check = 1.
     ENDIF.
   ENDIF.
ENDLOOP.
ENDFORM.                    " f004_process
*&      Form f005_posting
      text
FORM f005_posting .
CLEAR: w_itemno,
         w_cond.
w_itemno = 10.
w_cond = 1.
IF w_check = '' OR w_check = 1.
wa_bapisdhd1-doc_type = pr_auart.
wa_bapisdhd1-ord_reason = pr_augru.
LOOP AT it_main INTO wa_main.
    IF w_cond = 1.
      CLEAR: it_bapiret2,
             it_bapisditm,
             it_bapiparnr,
             it_bapischdl,
             it_bapicond.
      REFRESH:it_bapiret2,
              it_bapisditm,
              it_bapiparnr,
              it_bapischdl,
              it_bapicond.
      MOVE: wa_main-vkorg TO wa_bapisdhd1-sales_org,
            wa_main-vtweg TO wa_bapisdhd1-distr_chan,
            wa_main-spart TO wa_bapisdhd1-division.
      wa_bapisdhd1-wbs_eleM = 'Y561.1'.
      CALL FUNCTION 'CONVERSION_EXIT_ALPHA_OUTPUT'
        EXPORTING
          INPUT         = pr_kunnr
       IMPORTING
         OUTPUT        = pr_kunnr.
      wa_bapisdhd1-PURCH_NO_S = pr_kunnr.
      wa_bapisdhd1-PURCH_NO_C = pr_kunnr.
    ENDIF.
    MOVE: w_itemno TO wa_bapisditm-itm_number,
           wa_main-matnr TO wa_bapisditm-material,
          wa_main-BISMT TO wa_bapisditm-material,
          wa_main-werks TO wa_bapisditm-plant,
          wa_main-lgort TO wa_bapisditm-store_loc.
                       wa_bapisditm-target_qty = '10'.
    wa_bapisditm-PURCH_NO_S = pr_kunnr.
    wa_bapisditm-PURCH_NO_C = pr_kunnr.
    APPEND wa_bapisditm TO it_bapisditm.
    IF w_cond = 1.
      wa_bapiparnr-partn_numb = pr_kunnr.
      wa_bapiparnr-itm_number = 10.
        wa_bapiparnr-partn_role = 'SP'.
      APPEND wa_bapiparnr TO it_bapiparnr.
      wa_bapiparnr-partn_role = 'AG'.
      APPEND wa_bapiparnr TO it_bapiparnr.
      CLEAR wa_bapiparnr-partn_role.
               wa_bapiparnr-partn_numb = pr_kunnr.
      wa_bapiparnr-partn_role = 'RE'.
      APPEND wa_bapiparnr TO it_bapiparnr.
      CLEAR wa_bapiparnr-partn_role.
               wa_bapiparnr-partn_numb = pr_kunnr.
      wa_bapiparnr-partn_role = 'RG'.
      APPEND wa_bapiparnr TO it_bapiparnr.
      CLEAR wa_bapiparnr-partn_role.
               wa_bapiparnr-partn_numb = pr_kunnr.
      wa_bapiparnr-partn_role = 'WE'.
      APPEND wa_bapiparnr TO it_bapiparnr.
    ENDIF.
    wa_bapischdl-itm_number = w_itemno.
    wa_bapischdl-req_qty    = wa_main-kwmeng.
     wa_bapischdl-PURCH_NO_S = pr_kunnr.
    APPEND wa_bapischdl TO it_bapischdl.
    wa_bapicond-itm_number = w_itemno.
    wa_bapicond-cond_type = 'ZECL'.
     IF    ( wa_bapisdhd1-doc_type = 'ZPMU' ) OR ( wa_bapisdhd1-doc_type = 'ZPMM' ).
       wa_bapicond-cond_type = 'ZVAL'.
     ELSE.
       wa_bapicond-cond_type = 'ZMRP'.       "+PK12122006
     ENDIF.
    wa_bapicond-cond_value = wa_main-kwert.
    APPEND wa_bapicond TO it_bapicond.
    w_itemno = w_itemno + 10.
    w_cond   = w_cond + 1.
ENDLOOP.
data : SALESDOCUMENTIN like BAPIVBELN-VBELN.
CALL FUNCTION 'BAPI_SALESORDER_CREATEFROMDAT2'
    EXPORTING
      order_header_in     = wa_bapisdhd1
    IMPORTING
      salesdocument       = SALESDOCUMENTIN
    TABLES
      return              = it_bapiret2
      order_items_in      = it_bapisditm
      order_partners      = it_bapiparnr
      order_schedules_in = it_bapischdl
      order_conditions_in = it_bapicond.
CALL FUNCTION 'BAPI_TRANSACTION_COMMIT'
    EXPORTING
      wait = c_ch.
ENDIF.
LOOP AT it_bapiret2 INTO wa_bapiret2.
    DATA : w_err(100) TYPE c,
    w_matnr TYPE matnr.
    IF wa_bapiret2-type = 'E' AND wa_bapiret2-id = 'V1' AND wa_bapiret2-number = 392.
      UNPACK wa_bapiret2-message_v1 TO w_matnr.
      READ TABLE it_matnr INTO wa_matnr WITH KEY matnr = w_matnr.
      IF sy-subrc EQ 0.
        CONCATENATE text-013 wa_matnr-bismt INTO w_err SEPARATED BY space.
        MESSAGE w_err TYPE 'S'.
      ENDIF.
    ENDIF.
    IF WA_BAPIRET2-TYPE = 'S'. " Comment
      WRITE: 40 TEXT-009, WA_BAPIRET2-MESSAGE_V2+0(10).
    ENDIF.
ENDLOOP.
ENDFORM.                    " f005_posting
I have given all the necessary parameters. it is telling that error is in parameter
sales_header_in.
I have checked it.
i have assigned purch_no_s and purch_no_c of the structure BAPISDHD1(ORDER_HEADER_IN)
in the bapi with customer number.
and also i have assigned the partnumber of the structure BAPIPARNR ORDER_PARTNERS
in the bapi with customer number.
but still , it is diplaying the error message, please enter the sold to or ship to party number.
how to resolve this error.
this is urgent requirement.
points will be awarded.
thanking u in advance,
a.srinivas.

Hi,
Did u have a look at the standard programs which make use of BAPI_SALESORDER_CREATEFROMDAT1
Heres a list...
LWSSOU08
MV45WF0S
MWWMJF21_BAPI_SALESORDER_CREAT
RBUS2032
Regards,
Tanveer.
<b>Please mark helpful answers</b>

Checks on vendors during the creation of PO with ME21N

Hi all,
i have this problem:
during the creation of a Purchase Order, for some types of them i have to bypass some checks that are made by standard on the Vendor.
Is it possibile to do? if it is, how can i do it?
Thanks
Lello

Hi
If they are standard controls, probably it'll mean to change the standard program: if your SAP release is ECC 6.00 u can try to use the Implicit Enhancement in order to change the standard else u need to register the standard to OSS in order to get the access key for modification.
Max

No Authorization to OLAP Cubes during the creation of universe connection

Hello friends we are not able to see the OLAP Cubes during the creation of universe connection using the Quality system and Application server "sapbmw01" client 100, system # 00. But we are able to set up the connection in our development system.
I will highly appreciate if you can let me know if we need some special role to access the OLAP Cubes during the creation of universe connection using the Q system.
Surprisingly we are using SAP_BW_ALL in Quality system still we are not able to access the infocubes. is there some thing missing in CMS IN BO to make that work.
Thanks
Soniya

Hi Jyothy,
Refer the below link on how to create universe on Analytic View/Calculation View using relation connection in IDT
http://www.sapanalyticsguru.com/index.php/sap-bobi/31-universe-creation-on-hana-view-using-information-design-tool

Analysis Services failing to Start . File system error: Error occurred during the creation of directory

Hello All,
Posting this problem here and hoping for a solution from the experts in this forum.
When i have restarted the Analysis Services , i see that it has been stopped but never started back. It fails with an error
"The SQL Server Analysis Services (MSSQLSERVER) service on Local Computer started and then stopped. Some services stop automatically if they are not in use by other services or programs."
When Checked the Event Viewer i see the following error -
The service cannot be started: The following system error occurred: The filename, directory name, or volume label syntax is incorrect. File system error: Error occurred during the creation of directory: '\\?\E:\OLAP\MSSOLAPFactory\OlapData;M:\Test
Backup'.
I remember changing the BackupDir value of Analysis Services few days back, and i think it could have impacted. Can you please help me how can i change back the BackupDir value and have the server back?
Let me know if you need any more details
SG

Is this still an issue? If so, I would find msmdsrv.ini and make sure you don't have two folders listed in the BackupDir (or DataDir or TempDir). You'll have to runas Administrator to edit the msmdsrv.ini file and save changes. Once you fix that, it should
succeed.
http://artisconsulting.com/Blogs/GregGalloway

Add new field during the creation of a dispute case from AR

Hi experts,
Can you help me out with the steps necessaries to create a new field and add it and completed during the creation of a dispute case from AR.
Many thanks.

Yes, BADI fdm_user_screen has to be used.
1 method GET_CREATE_SCREEN to define the screen with the new attribute/s
2 method CREATE_SCREEN_PBO to define the logic tht u want to get processed before the screen is up for display, (possibly pre-population of the attribute/s)
3 method CREATE_SCREEN_PAI for logic after the user has entered value in the attribute/s

Connection tab is inactive during the creation of system alias in portal

When we trying to implement the note 1249323, during the creation of
system alias in portal (Step B in SRM 7.0), the connection tab is
inactive to fill the information (EP-PCT-SRM).
Please can anybody give a solution to this problem so that we can finish our
implementation of the note.
Thanks and regards
Mahesh

If you are referring to the property "Collection" of the system object - I don't think you can edit it. It is not used at runtime by the applications/iviews.
That should have been a mistake in the SAP note and you can ignore that property and go ahead with creating your system.
Thanks,
Shanti

BBP_PO_SEND_XML - Not triggered during the creation of PO

Hi All,
We are using SRM 7.0, configuration for sending PO in the form of XML is done as suggested with the method BBP_PO_SEND_XML. The problem is, this BADI is not triggered when we save (even after order) the PO with XML option and the status is displayed as Incorrectly processed. But, when I select the Incorrectly processed output type and click on Repeat Output, the BADI is called and is processed succesfully.
Any reasons, why the BADI is not triggered during the creation or change of PO and is getting triggered only when we select the option Repeat Output? Please help me in correcting this issue.
Thanks,
Phani.

Logic inside META_PO_SEND was written in user name check. Whereas the method BBP_PO_SEND_XML is triggered with batch user. Due to this reason, custom logic is not triggered.

Regarding Performance concerns during the creation of Infocube

hai
im going to create the infocube on top of ODS.
Pls tell me some design tips for performance things during the creation of Infocube like partitioning , Indexes...
Basically im loading from Oracle Databasetables by using DB-COnnect .
pls tell me
i ll assing the points
bye
rizwan

hi Rizwan,
check these:
https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/1955ba90-0201-0010-d3aa-8b2a4ef6bbb2
https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/ce7fb368-0601-0010-64ba-fadc985a1f94
https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/4c0ab590-0201-0010-bd9a-8332d8b4f09c
https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/3a699d90-0201-0010-bc99-d5c0e3a2c87b
assign points if useful ***
Thanks,
Raj

ERROR ODI-40837: An error occurred during the creation of the schema

Hi I am trying to test an xml file server and keep getting the following error.
ERROR ODI-40837: An error occurred during the creation of the schema: ODI-40738: A SAXException was caught while reading the model saying: Expected 'DOCTYPE'.
JDBC URL jdbc:snps:xml?f=C:/Projects/prd.xml&ro=true&DOD=YES
anybody could help as i dont find any blog or documentation about this error?.
Thanks
Edited by: user626688 on May 31, 2013 1:26 PM

There seems to be some problem with your xml file. Please work with support channel to investigate this issue.
You can also check the xml driver parameters details at http://docs.oracle.com/cd/E28280_01/integrate.1111/e12644/appendix_xml_driver.htm#CHDECBHH

BAM Error - during the creation of BAM Activity and View in EXCEL

I'm getting an error "The Cube could not be created successfully. Please edit the view and validate the inputs" during the creation of BAM Activity and VIEW in MS Excel for BAM
Error Details:
Error Description:
The following system error occurred: Invalid class string .
Error Source:
Microsoft OLE DB Provider for Analysis Services 2008.
Please help me in resolving the issue. Thanks in Advance!!

Hi Ramesh,
Below link has the information related to all the prerequisites for using BAM Add-In for Excel.
Kindly ensure that you have all the files in place before creating BAM Activity and View.
http://msdn.microsoft.com/en-us/library/aa560476.aspx
Rachit
Please mark it as Answer if this answers your question

Different databse tables affected during the creation of a PR

Can someone please explain the different databse tables affected during the creation of a Purchase Requisition except EBAN?

Hi Ajit,
Thanks for the reply.
Kindly let me know how these tables will be affected when PR will be created(STXH,STXL)?
Thanks,
Lina

Concern during the creation of a menu contextual

Hello has all, I am a french developer using
Flex/ActionScript for the development of application to work.
I have a concern during the creation of a menu contextual.
I have could contater that a contextMenuItem with the value
“delete” is not posted in my menu contextual.
Sample :
var myContextMenu : ContextMenu() = new ContextMenu();
myContextMenu.hideBuiltInItems();
var customItemsArr : Array = new Array();
var item : ContextMenuItem = new
ContextMenuItem("supprimer");
item.addEventListener(ContextMenuEvent.MENU_ITEM_SELECT,
deleteHandler);
customItemsArr.push(item);
myContextMenu.customItems = customItemsArr;
on the other hand the same code with a different value that
to delete will be taken into account.
Is this an error of my share??
Does Y have you it of another words which are not to accept
in a menu contextual (nothing on this subject is specified in the
api one)??
thank you for your answer

Hi,
It is probably that the one or both of the following situations
apply:
1) please check the value for field BEXCLUDE in table GB01 for the
relevant field(s). If the field has the value X then it cannot be
substituted in the standard system.
Please refer to the attached note 42615 regarding this.
2) please check if any of these substitutions involved a modification
at callup point 3.
See the attached note 386896, where it states:
"As of Release ERP 2004, you can no longer use the source code
corrections as these can cause inconsistencies between the entry
view and the general ledger view.
As of Release ERP 2004 you can also use the AC_DOCUMENT BADI for
postings using the accounting interface."
Reg
Madhu M

Issue during automatic Creation of Work Order from Notification

Hi,
I have a issue during automatic Creation of Work Order from Notification.
BADI implemented: NOTIF_EVENT_POST
BAPI called in BADI: BAPI_ALM_ORDER_MAINTAIN
I am able to create Work Order successfully but after that i need to update notification header with created work order number.
But i am unable to update the same (VIQMEL-AUFNR).
Can anybody provide solution for the same!
Thanks,
Kumar.

Hi,
Any inputs on above posted issue!
Thanks in advance.
Thanks,
Kumar.

Hi Sanjeev : Validating PO during the creation of Sales Orders

Similar Messages

Maybe you are looking for