Item partner flag set in Orders06 Idoc

Hi,
I am trying to set the item partners flag in a sales order creation Idoc Order06. Unfortuantely I am not able to find a placeholder or a segment field to map this flag in the Orders06 Idoc. So I am not able to overwrite the ship to addresses coming inthrough the interfaces. Please advise.
Teresa

Thanks Ravi for response. i had super busy week could't get back.i think i could't not provide enough details about the issue.
we have maintained 6 different languages in material master in purchse order text tab-additional data Tab.
when i set the deletion flag in MDM .MATMASS idoc generates successfully and i can see field carrying deletion flag indicator and it does set deletion flag on ECC side but after that if i check the additional data tab where we have maintained the material description for 6 different languages i see only three left other three are wiped off.it also shows in change log that changes has been made in those value but not sure about the root cause.i want to set deletion flag but no change in description.
Thanks again for your interest.

Similar Messages

Mass Item OK flag in MIGO

Hi,
If a PO has multiple line items then during GR user has to click 'Item Ok' button one by one for every line item. To avoid manual selection by line item is there any mass 'Item OK' flag setting possibe in MIGO.
Thanks for help in advance.

Dear Zaman,
You can change the settings as suggested by Jurgen above, but it is highly not recommended. The main reason the item OK tab is left unchecked is to ensure the quality of goods received and place them in appropriate Storage Location and then check the item OK tab. Hope this helps.
Thanks
Murtuza

IDOC ORDERS05: Segment E1EDPA1Doc.item partner information is not filled

Hello,
I'm working on the AFS-Retail Interface for Orders.
In the first step we create a sales contract in AFS with the combined demand from a retail purchase order and in a second step the sales order call-offs which are the Retail orders for the stores (NB; one PO for one store).
The problem is in the sales order call-off. In the Retail outbound IDOC the information about the relevant ship-to stands only the header segment E1EDKA1 (PARVW = WE).
In the AFS IDOC inbound the ship-to is written in the header partners of the sales order. But because the information is missing on item level the information is copied from the sales contract which leads to the wrong ship-to for the items in the sales order.
For the communication we are using the basic type orders05. Is there a possibility to fill the item partner segments E1EDPA1 out of the standard or do I need to implement an user exit in the Retail IDOC outbound process so that the partner information is filled also on item level?
Thanks in advance.
Regards,
Christine

Hi Christine
I am working on SAP AFS 6.0.. I Had same issue.....When sales order ref to a contract....i resoved it
u need to write user exit for this....
Ramesh

Set item, partner data of sales order using BAPI_BUSPROCESSND_CREATEMULTI

hi all,
i am using BAPI_BUSPROCESSND_CREATEMULTI to create sales order in CRM. the order is created but i dont have the partner information, item data, organization and schedule line data even though i am passing them in the bapi.
I am generating a new guide each time for all these tables HEADER, ITEM, PARTNER, ORGANIZATION, SCHEDULELINE,u2026u2026
and finally in 'BAPI_BUSPROCESSND_SAVE i am passing the guide as the guide that i generated for HEADER table..I am i using the bapi in correct way?
I don't know why I dont see any partner data, product data i, item data n my saved order.i dont know what values i should pass to the PARTNER table for REF_GUID , REF_KIND, REF_PARTNER_HANDLE . please help me.
this is my code
*****Internal Tables
***TABLES
DATA: IT_HEADER TYPE TABLE OF BAPIBUS20001_HEADER_INS.
DATA: IT_INPUT_FIELDS_FILL TYPE TABLE OF BAPIBUS20001_INPUT_FIELDS.
DATA: IT_ITEM TYPE TABLE OF BAPIBUS20001_ITEM.
DATA: IT_PARTNER TYPE TABLE OF BAPIBUS20001_PARTNER_INS.
DATA: IT_ORGANISATION TYPE TABLE OF BAPIBUS20001_ORGMAN_INS.
***WORK AREA
DATA: WA_INPUT_FIELDS TYPE BAPIBUS20001_INPUT_FIELDS.
DATA: WA_HEADER TYPE BAPIBUS20001_HEADER_INS.
DATA: WA_ITEM TYPE BAPIBUS20001_ITEM.
DATA: WA_PARTNER TYPE BAPIBUS20001_PARTNER_INS.
DATA: WA_ORGANISATION TYPE BAPIBUS20001_ORGMAN_INS.
DATA: IT_EV_GUID_32 TYPE GUID_32.
DATA: IT_EV_GUID_32_1 TYPE GUID_32.
DATA: IT_EV_GUID_32_2 TYPE GUID_32.
DATA: IT_EV_GUID_32_3 TYPE GUID_32.
DATA: IT_OBJECTS_TO_SAVE TYPE STANDARD TABLE OF BAPIBUS20001_GUID_DIS WITH HEADER LINE.
DATA: IT_OBJECTS_TO_SAVE_1 TYPE STANDARD TABLE OF BAPIBUS20001_GUID_DIS WITH HEADER LINE.
CONSTANTS:true TYPE crmt_boolean VALUE 'X'.
*Create your own GUID for each order using function module GUID_CREATE (and use output field EV_GUID_32).
CALL FUNCTION 'GUID_CREATE'
IMPORTING
    EV_GUID_32       = IT_EV_GUID_32.
Fill of the HEADER the fields GUID, PROCESS_TYPE, DESCRIPTION and CREATED_BY,
do NOT fill HANDLE and OBJECT_ID, other fields if needed are allowed).
WA_HEADER-GUID                      = IT_EV_GUID_32.
WA_HEADER-PROCESS_TYPE              = 'ZWEB'.
WA_HEADER-DESCRIPTION               = 'WEB ORDER'.
WA_HEADER-CREATED_BY                = 'SAMJESI.
APPEND WA_HEADER TO IT_HEADER.
*For each FIELD of HEADER structure that has been filled also fill INPUT_FIELDS fields REF_GUID (header GUID),
*REF_KIND (header REF_KIND), LOGICAL_KEY (='1'), OBJECTNAME (='ORDERADM_H') and FIELDNAME (as text).
WA_INPUT_FIELDS-REF_GUID               = IT_EV_GUID_32.
WA_INPUT_FIELDS-REF_KIND               = 'A'.
WA_INPUT_FIELDS-OBJECTNAME             = 'ORDERADM_H'.
WA_INPUT_FIELDS-LOGICAL_KEY            = '1'.
WA_INPUT_FIELDS-CHANGEABLE             = ' '.
WA_INPUT_FIELDS-FIELDNAME              = 'PROCESS_TYPE'.
APPEND WA_INPUT_FIELDS TO IT_INPUT_FIELDS_FILL.
WA_INPUT_FIELDS-FIELDNAME              = 'GUID'.
APPEND WA_INPUT_FIELDS TO IT_INPUT_FIELDS_FILL.
WA_INPUT_FIELDS-FIELDNAME              = 'DESCRIPTION'.
APPEND WA_INPUT_FIELDS TO IT_INPUT_FIELDS_FILL.
WA_INPUT_FIELDS-FIELDNAME              = 'CREATED_BY'.
APPEND WA_INPUT_FIELDS TO IT_INPUT_FIELDS_FILL.
*Create your own GUID for each order using function module GUID_CREATE (and use output field EV_GUID_32).
CALL FUNCTION 'GUID_CREATE'
IMPORTING
    EV_GUID_32       = IT_EV_GUID_32_1.
*For each ITEM, create your own GUID and fill the fields GUID (item GUID), HEADER (header GUID),
*ORDERED_PROD, DESCRIPTION, ITM_TYPE, ORDER_DATE and MODE (='A').
WA_ITEM-GUID              = IT_EV_GUID_32_1.
WA_ITEM-NUMBER_INT        = '10'.
WA_ITEM-ORDERED_PROD      = '000000000090000230'.
WA_ITEM-ITM_TYPE          = 'ZTAN'.
WA_ITEM-MODE              = 'B'.
APPEND WA_ITEM TO IT_ITEM.
*For each FIELD of ITEM structure that has been filled also fill INPUT_FIELDS fields REF_GUID (header GUID),
*REF_KIND (header REF_KIND), LOGICAL_KEY (='1'), OBJECTNAME (='ORDERADM_I') and FIELDNAME (as text).
WA_INPUT_FIELDS-REF_GUID               = IT_EV_GUID_32_1.
WA_INPUT_FIELDS-REF_KIND               = 'B'.
WA_INPUT_FIELDS-OBJECTNAME             = 'ORDERADM_I'.
WA_INPUT_FIELDS-LOGICAL_KEY            = '1'.
WA_INPUT_FIELDS-CHANGEABLE             = ' '.
WA_INPUT_FIELDS-FIELDNAME              = 'GUID'.
APPEND WA_INPUT_FIELDS TO IT_INPUT_FIELDS_FILL.
WA_INPUT_FIELDS-FIELDNAME              = 'NUMBER_INT'.
APPEND WA_INPUT_FIELDS TO IT_INPUT_FIELDS_FILL.
WA_INPUT_FIELDS-FIELDNAME                 = 'ORDERED_PROD'.
APPEND WA_INPUT_FIELDS TO IT_INPUT_FIELDS_FILL.
WA_INPUT_FIELDS-FIELDNAME                 = 'ITM_TYPE'.
APPEND WA_INPUT_FIELDS TO IT_INPUT_FIELDS_FILL.
*For each PARTNER fill the fields REF_GUID (header GUID), REF_KIND, REF_PARTNER_HANDLE (start with 1, next 1 higher),
*KIND_OF_ENTRY, PARTNER_FCT, PARTNER_NO, NO_TYPE and DISPLAY_TYPE.
CALL FUNCTION 'GUID_CREATE'
IMPORTING
    EV_GUID_32       = IT_EV_GUID_32_2.
WA_PARTNER-REF_GUID                = IT_EV_GUID_32_2.
*WA_PARTNER-REF_KIND                = '1'
*WA_PARTNER-REF_PARTNER_HANDLE      = '1'.
WA_PARTNER-PARTNER_FCT             = '00000001'.
WA_PARTNER-PARTNER_NO              = '100000433'.
APPEND WA_PARTNER TO IT_PARTNER.
*For each FIELD of PARTNER structure that has been filled also fill INPUT_FIELDS fields REF_GUID (partner GUID),
*REF_KIND (partner REF_KIND), LOGICAL_KEY (='1'), OBJECTNAME (='PARTNER') and FIELDNAME (as text).
WA_INPUT_FIELDS-REF_GUID               = IT_EV_GUID_32_2.
WA_INPUT_FIELDS-REF_KIND               = 'A'.
WA_INPUT_FIELDS-OBJECTNAME             = 'PARTNER'.
WA_INPUT_FIELDS-LOGICAL_KEY            = '1'.
WA_INPUT_FIELDS-CHANGEABLE             = ' '.
WA_INPUT_FIELDS-FIELDNAME              = 'REF_GUID'.
APPEND WA_INPUT_FIELDS TO IT_INPUT_FIELDS_FILL.
*WA_INPUT_FIELDS-FIELDNAME              = 'REF_PARTNER_HANDLE'.
*APPEND WA_INPUT_FIELDS TO IT_INPUT_FIELDS_FILL.
WA_INPUT_FIELDS-FIELDNAME              = 'PARTNER_FCT'.
APPEND WA_INPUT_FIELDS TO IT_INPUT_FIELDS_FILL.
WA_INPUT_FIELDS-FIELDNAME              = 'PARTNER_NO'.
APPEND WA_INPUT_FIELDS TO IT_INPUT_FIELDS_FILL.
*Fill the ORGANISATION fields REF_GUID, REF_KIND, DIS_CHANNEL, DIVISION, SALES_ORG and MODE.
CALL FUNCTION 'GUID_CREATE'
IMPORTING
    EV_GUID_32       = IT_EV_GUID_32_3.
WA_ORGANISATION-REF_GUID = IT_EV_GUID_32_3.
*WA_ORGANISATION-REF_KIND
WA_ORGANISATION-DIS_CHANNEL = '20'.
WA_ORGANISATION-DIVISION     = '00'.
WA_ORGANISATION-SALES_ORG    = '228'.
WA_ORGANISATION-MODE         = 'A'.
APPEND WA_ORGANISATION TO IT_ORGANISATION.
*For each field of ORGANISATION structure that has been filled als fill INPUT_FIELDS. OBJECTNAME='ORGMAN'.
WA_INPUT_FIELDS-REF_GUID               = IT_EV_GUID_32_3.
WA_INPUT_FIELDS-REF_KIND               = 'A'.
WA_INPUT_FIELDS-OBJECTNAME             = 'ORGMAN'.
WA_INPUT_FIELDS-LOGICAL_KEY            = '1'.
WA_INPUT_FIELDS-CHANGEABLE             = ' '.
WA_INPUT_FIELDS-FIELDNAME              = 'REF_GUID'.
APPEND WA_INPUT_FIELDS TO IT_INPUT_FIELDS_FILL.
WA_INPUT_FIELDS-FIELDNAME              = 'DIS_CHANNEL'.
APPEND WA_INPUT_FIELDS TO IT_INPUT_FIELDS_FILL.
WA_INPUT_FIELDS-FIELDNAME              = 'DIVISION'.
APPEND WA_INPUT_FIELDS TO IT_INPUT_FIELDS_FILL.
WA_INPUT_FIELDS-FIELDNAME              = 'SALES_ORG'.
APPEND WA_INPUT_FIELDS TO IT_INPUT_FIELDS_FILL.
WA_INPUT_FIELDS-FIELDNAME              = 'MODE'.
APPEND WA_INPUT_FIELDS TO IT_INPUT_FIELDS_FILL.
REFRESH: CREATED_PROCESS.
               CALL FUNCTION 'BAPI_BUSPROCESSND_CREATEMULTI'
                 TABLES
                    HEADER                  = IT_HEADER
                    ITEM                    = IT_ITEM
                    PARTNER                 = IT_PARTNER
                    ORGANISATION            = IT_ORGANISATION
                    INPUT_FIELDS            = IT_INPUT_FIELDS_FILL
                    CREATED_PROCESS         = CREATED_PROCESS
                    RETURN                  = RETURN.
IT_OBJECTS_TO_SAVE-GUID = IT_EV_GUID_32.
IT_OBJECTS_TO_SAVE-OBJECT_TYPE = 'BAPIBUS20001'.
APPEND IT_OBJECTS_TO_SAVE TO IT_OBJECTS_TO_SAVE.
CALL FUNCTION 'BAPI_BUSPROCESSND_SAVE'
EXPORTING
    UPDATE_TASK_LOCAL       = true
    SAVE_FRAME_LOG          = true
IMPORTING
LOG_HANDLE              =
TABLES
    OBJECTS_TO_SAVE         = IT_OBJECTS_TO_SAVE
    SAVED_OBJECTS           = ITAB_SAVED_OBJECTS
    RETURN                  = itab_return.

Hi Jessica,
Please find an example of how the code is implemented.
DATA:    lt_saved   TYPE crmt_return_objects,
         lt_exc     TYPE crmt_exception_t,
         lt_not_saved TYPE crmt_object_guid_tab.
DATA:    lv_contact_guid TYPE crmt_object_guid.
DATA:    lt_headerx TYPE TABLE OF bapibus2000110_header_insx,
         ls_headerx TYPE bapibus2000110_header_insx,
         lt_reasonx TYPE TABLE OF bapibus2000110_reason_insx,
         ls_reasonx TYPE bapibus2000110_reason_insx,
         lt_reason   TYPE TABLE OF bapibus2000110_reason_ins,
         ls_reason   TYPE bapibus2000110_reason_ins,
         lt_text     TYPE TABLE OF bapibus20001_text_ins,
         ls_text     TYPE bapibus20001_text_ins,
         lt_textx    TYPE TABLE OF bapibus20001_text_insx,
         ls_textx    TYPE bapibus20001_text_insx,
         lt_outcome TYPE TABLE OF bapibus2000110_outcome_ins,
         ls_outcome TYPE bapibus2000110_outcome_ins,
         lt_outcomex TYPE TABLE OF bapibus2000110_outcome_insx,
         ls_outcomex TYPE bapibus2000110_outcome_insx,
         lt_status   TYPE TABLE OF bapibus20001_status_ins,
         ls_status   TYPE bapibus20001_status_ins,
         lt_statusx TYPE TABLE OF bapibus20001_status_insx,
         ls_statusx TYPE bapibus20001_status_insx,
         lt_return   TYPE TABLE OF bapiret2,
         BEGIN OF lv_reason,
           cat(2)        TYPE c,
           code_group(8) TYPE c,
           code(4)       TYPE c,
         END OF lv_reason,
         BEGIN OF lv_outcome,
           cat(2)        TYPE c,
           code_group(8) TYPE c,
           code(4)       TYPE c,
         END OF lv_outcome,
         lv_entry TYPE boolean.
DATA: ls_header TYPE bapibus20001_header_ins.
DATA: lt_header TYPE STANDARD TABLE OF bapibus20001_header_ins.
DATA: ls_input_fields TYPE bapibus20001_input_fields.
DATA: lt_input_fields TYPE STANDARD TABLE OF bapibus20001_input_fields.
data: lw_service_os type BAPIBUS20001_SERVICE_OS_INS.
data: lt_service_os type standard table of BAPIBUS20001_SERVICE_OS_INS.
DATA: guid type guid_32.
DATA LT_RRETURN TYPE STANDARD TABLE OF BAPIRET2.
CALL FUNCTION 'GUID_CREATE'
IMPORTING
    ev_guid_32 = guid.
lv_contact_guid = guid.
Description, objective, completion and priority
description
ls_header-guid            = guid.
ls_header-descr_language = sy-langu.
ls_header-description     = 'Test'.
ls_header-created_at      = sy-uzeit.
ls_header-created_by      = sy-uname.
ls_header-process_type    = 'ZPRI'.
APPEND ls_header TO lt_header.
APPEND ls_headerx TO lt_headerx.
ls_input_fields-ref_guid   = guid.
ls_input_fields-ref_kind = 'A'.
ls_input_fields-objectname = 'ORDERADM_H'.
ls_input_fields-fieldname = 'GUID'.
INSERT ls_input_fields INTO TABLE lt_input_fields.
ls_input_fields-fieldname = 'LANGUAGE'.
INSERT ls_input_fields INTO TABLE lt_input_fields.
ls_input_fields-fieldname = 'DESCRIPTION'.
INSERT ls_input_fields INTO TABLE lt_input_fields.
ls_input_fields-fieldname = 'CREATED_AT'.
INSERT ls_input_fields INTO TABLE lt_input_fields.
ls_input_fields-fieldname = 'CREATED_BY'.
INSERT ls_input_fields INTO TABLE lt_input_fields.
ls_input_fields-fieldname = 'PROCESS_TYPE'.
INSERT ls_input_fields INTO TABLE lt_input_fields.
lw_service_os-REF_HANDLE = guid.
lw_service_os-REF_GUID = guid.
lw_service_os-SUBJECT_PROFILE = 'ZSPTSKPRI'.
LW_SERVICE_OS-CAT_TYPE = 'A1'.
LW_SERVICE_OS-CODE_GROUP = 'ZCGPRI'.
LW_SERVICE_OS-CODE = 'P120'.
APPEND LW_SERVICE_OS TO LT_SERVICE_OS.
CALL FUNCTION 'BAPI_BUSPROCESSND_CREATEMULTI'
TABLES
    header                  = lt_header
ITEM                    =
ACTIVITY                =
SALES                   =
PARTNER                 =
ORGANISATION            =
SHIPPING                =
APPOINTMENT             =
TEXT                    =
   SERVICE_OS              = LT_SERVICE_OS
STATUS                  =
   input_fields            = lt_input_fields
CREATED_PROCESS         =
   RETURN                  = LT_RRETURN
LEAD                    =
OPPORTUNITY             =
PRODUCT                 =
SCHEDULELINE            =
CUSTOMER_HEAD           =
CUSTOMER_ITEM           =
PRICING                 =
PRICING_ITEM            =
CONDITION_CREATE        =
BILLING                 =
CONFIG_CFG              =
CONFIG_BLB              =
CONFIG_INS              =
CONFIG_PRT              =
CONFIG_VAL              =
CONFIG_VK               =
CONFIG_REF              =
ADDRESS                 =
BILLPLAN                =
BILLPLAN_DATE           =
EXTENSIONIN             =
DOCUMENT_FLOW           =
BATCH                   =
PRICING_AGR_CRM         =
FINPROD_ITEM            =
CANCEL                  =
CANCEL_IR               =
PRODUCT_LIST            =
PRODUCTS                =
OBJECTS                 =
PAYPLAN                 =
PAYPLAN_DATE            =
CONFIG_FILTER_CFG       =
CONFIG_FILTER_INS       =
CONFIG_FILTER_PRT       =
CONFIG_FILTER_VAL       =
ACTIVITY_I              =
EXT_REF                 =
DATA: lt_objects_to_save TYPE TABLE OF bapibus20001_guid_dis,
      ls_objects_to_save TYPE bapibus20001_guid_dis,
      lt_saved_objects    TYPE STANDARD TABLE OF bapibus20001_object_id,
      lt_return1        TYPE STANDARD TABLE OF bapiret2,
      lv_object_guid      TYPE crmt_object_guid.
build save table
ls_objects_to_save-guid = ls_header-guid.
ls_objects_to_save-object_type = 'BUS2000125'.
INSERT ls_objects_to_save INTO TABLE lt_objects_to_save.
CHECK lt_objects_to_save IS NOT INITIAL.
CALL FUNCTION 'BAPI_BUSPROCESSND_SAVE'
EXPORTING
UPDATE_TASK_LOCAL       = FALSE
SAVE_FRAME_LOG          = FALSE
IMPORTING
LOG_HANDLE              =
TABLES
    objects_to_save         = lt_objects_to_save
   saved_objects           = lt_saved_objects
   return                  = lt_return1

Item Partner Indicator at Item level

Hi,
We have two item in sales order.For second item user make following changes,
Requirements type changed
MRP area changed
Business Area changed
Material Number changed
Checking Group for Availability Check changed
Net price changed
Profit Center changed
Tax classification material changed
Shipping Point/Receiving Point changed
Plant (Own or External) changed
He has not done any changes in Partner Tab at Item level,then also indicator has been set for Item Partners.
He has not done any changes at Header Partners too.
Could you please help how this indicator has been set even he has not done any change in Partner TAB.
Is this indicator depends on other item level fields in sales order?
Thanks,
Lalit

In VA02, after entering the sales order number, go to menu Environment ->changes. Here you can find the details on whether the item partner has been changed by the users or not. Alternatively you can execute t.code AUT10 and check the change details. If the partner is changed manually (even address changes made), then the flag item partner is checked by the system.
For further details read OSS Note 380507 - SD partner determination: FAQ for the functions -POINT 2
Regards,

GL Open Item Managed Flag Changed Historically - Orphan items left on acct

Back in 2000 for some of our GLs the Open Item Managed flag was changed. Initially it was not checked but now it is. We know that SAP doesn't really let you do it anymore but apparently back then whoever did it didn't follow what was then the suggested procedure. As a result we have an account balance of say 500,000 which I can see in FS10N however if I run it for all open items in FBL3N I get 450,000 because 50,000 are not open or cleared. I can't go in and clear these off against anything because they are not open item managed. Is there a program that can be ran to make them open?
I thought RFSEPA01 would do the trick and after running it in our QA environment the log states:
Line Items Year Remark
         1 2000 Document selected
         1 2000 Document changed
However when I go to F-03 it still won't bring the documents in as it says they are not open item managed.
Sure enough if I go look in table BSIS at the document the Open Item Managed flag is not set.
What's the best procedure to resolve these? Do I have to create a Z program that will flag the Open Item Managed field (XOPVW) and then clear these documents off against something?
TIA

Hello,
Please check the SAP note 175960.
As explained in the note 175960, is not possible to subsequently
activate the open item management under some conditions.
With NewGL, the split information on open items is stored in
FAGL_SPLINFO and FAGL_SPLINFO_VAL which are only updated when the
document is being posted through active document split. Also RFSEPA02
does not update these tables.
If you are NOT using NEW/GL with doc split (inactive), you may create
add-on report by copying RFSEPA02 and adding modification on the report
per note 175960.
As the note states, if you decide to take RFSEPA02 approach,
please do so at your own risk. Possible problems (such as data
inconsistency) can only be handled by SAP within chargeable remote
consulting.
All important information is written on note 175960.
Regards,
REnan

Partners are grayed out in "item partner" in sales order.

Hi !
I want to change the partner funtions in ITEM Partner in sales order. As of now i can not do that for a consignment fill up type of Sales doc. Where in IMG (?) i can change the settings so that i can change them manually.
regards,
vijay

Hi,
Go to SPRO - SD - Basic Functions - Partner Determination
Under Sales Item Partner - you now have the option to either make the partner mandatory or editable in the document.
Based on that setting, try changing your partner at line item level. I am sure this should work.
Rewards points if helpful.
Regards
Ravi

Item lines do not appear in IDoc PRICECATALOGUE

Hi everyone,
I'm trying to set up for sending price catalog (to customers) using transaction VPRICAT (SAP 4.6). I've created assortment, assigned material group and assortment user to this assortment, and also created a requirements profile. I'm now able to create a price catalog using VPRICAT. The problem is when IDoc is created there is only the header information in that IDoc. No item line will appear in the IDoc. I appreciate if you could help me to locate the problem.
Thanks in advance!
BR,
/Shahryar

Any idea?
/Shahryar

GR Based INV flag set on Purchase Order

Hello,
We are on SRM 5.5 and R3 ECC 6.0 classic scenario. We want to swihtch off the GR Based Invoice flag which is maintained in de vendor master. Vendor has no info record or contract. When creating a PO directly in R3 the flag is also disabled on the PO. However, when we create a shopping cart, the system automatically creates the purchase req and when the purchaser creates the Purchase order the GR Based Inv. flag is set again ? Can anybody let me know how this is possible ?
Thanks as eve for your help.
Antoinette

Hi Antoinette Stork,
Here is the way we have achieved. I am not an ABAPer and hence providing you more concepts than code.
01) A custom program is written and is scheduled on hourly basis as a back ground job.
02) This program is executed after the BBP_VENDOR_SYNC is executed as a background job as well.
03) BBP_VENDOR_SYNC will bring the updates and new vendors from the R/3 back end.
04) This will bring the vendors with the confirmation flag set on SRM (no corresponding field exists on the R/3 side vendor master) and also will check the GR based invoice verification flag on (the corresponding field exists on the ECC vendor master).
05) After 15 minutes the custom program will read the BUT000 table for the total number of vendors changed or created between two successive jobs.
06) Then query on the VENMAP table to get the GUIDs of the corresponding vendors.
07) Within the custom program use the FMs
     BBP_BUPA_FRG0060_CHANGE and
     BAPI_TRANSACTION_COMMIT
to set the flags for
      goodsrec_confex = ' ' and
      GR_BASEDIV
Sorry for being unable to provide you the code dump. This is working perfectly fine for us.
Also, we have used the badi "BBP_ECS_PO_OUT_BADI" with the method "BBP_B46B_PO_OUTBOUND" as a safety net as our invoice processing is two way match and we do not absolutely want the flags to be set to the R/3 PO.
DATA: ls_bapi_poitem TYPE bbps_if_bapimepoitem_pi.
Loop through the item details that gets passed to Backend*
LOOP AT ct_bapi_poitem INTO ls_bapi_poitem.
Clear the GR and GR-Based Invoice Verification Indicator.*
    CLEAR : ls_bapi_poitem-gr_ind,
            ls_bapi_poitem-gr_basediv.
    MODIFY ct_bapi_poitem FROM ls_bapi_poitem
           TRANSPORTING gr_ind gr_basediv.
ENDLOOP.
ENDMETHOD.
Hope this helps,
DV

GR_NON_VAL flag setting in ECC for SRM PO

Hi all,
SRM 5.0 ECS Sp12.
When we create a PO with multiple a/c assgt,the ECC PO which gets created always has the GR_NON_VAL flag set as "X".
Now if I uncheck the indicators "Confirmation-Related Invoice Verification " and "Confirm Performance of Service/Goods Receipt   " in SRM PO,then the PO replication fails in ECC and in SRM I get the below error :
With non-valuated GR, please also enter GR indicator
When I check the data which is passed to ECC,the GR_NON_VAL flag is also blank for the PO after the indicators "Confirmation-Related Invoice Verification " and "Confirm Performance of Service/Goods Receipt   " are unchecked in SRM PO.
Can someone let me know if in ECS , the GR_NON_VAL flag is always passed as blank and gets set to "X"based on ECC settings.If so,which settings in ECC determine the GR_NON_VAL flag to be set?
Can someone explain the istd behaviour for the GR_NON_VLAg flag in ECC PO for ECS when SRM PO with multiple a/c assignnment is changed for indicators "Confirmation-Related Invoice Verification " and "Confirm Performance of Service/Goods Receipt   "so that they are set to blank,Please advise.

HI
in standard we canl fill the flag GR_NON_VAL in SRM side but
the itemx structure of PO in ERP system set to space. After this mapping
BAPIs will be called.
wa_bapi_poitemx-po_itemx = 'X'.
    wa_bapi_poitemx-no_more_gr = 'X'.
    wa_bapi_poitemx-final_inv = 'X'.
    wa_bapi_poitemx-gr_ind = 'X'.
    wa_bapi_poitemx-delete_ind = 'X'.
delivery tolerance has to be taken over
    wa_bapi_poitemx-over_dlv_tol = 'X'.
    wa_bapi_poitemx-unlimited_dlv = 'X'.
    wa_bapi_poitemx-under_dlv_tol = 'X'.
note 644721, the Goods receipt non-valuated should be set according
to the backend customizing for this we have to clear the x-flag
    wa_bapi_poitemx-gr_non_val = ' '.
    wa_bapi_poitem-gr_non_val = ' '.
The redetermination will happen in PO create / change process
(within BAPI_PO_CHANGE and BAPI_PO_CREATE1).
1353431    ECS: PO in ERP always created with GR_NON_V
Summer

Just bought a new mac mini, wireless keyboard, and track pad. My track pad will not synch. All advise I have been given is to change items in the setting menu, but I cant because I still have to get through the setup!!

Just bought a new mac mini, wireless keyboard, and track pad. My track pad will not synch. All advise I have been given is to change items in the setting menu, but I cant because I still have to get through the setup!!

The power button for the Trackpad is on the right hand end of the battery case. Press that button to initiate the pairing process. On the top of the Trackpad just above the power button is a tiny green light (you probably cannot see it unless it is lighted). That light will indicate ehther or not the Trackpad is discoverable. If the Trackpad has discoverable the green light will blink on and off. If it does not pair within 3 minutes you will have to press the power button again to re-initiate the pairing process. Once your Trackpad has paired, you can just leave it on and it will pair automatically when you reboot your Mac.
If you are having problems pairing, try turning off any other Bluetooth devices within 30 or so feet of your Mac mini. That includes other Computers, iPhones, iPads, etc. that may be in the area. Once your Trackpad has pairedwith your mini, you don't have to be concerned about other Bluetooth devices.
One other hint, I find that although the Wireless Trackpad does not eat batteries as fast as the Magic Mouse it still uses more than the Wireless Keyboard. It is a good idea to keep a supply of AA batteries around. I have used Apple's Rechargable batteries, but found they did not last that long before needing to be recharged. I have had the best battery life from Duracell Quantum batteries.

Open item managment is set to B/S accounts

Hi Guru's
I saw open item managment is set to B/S accounts only. Do we set for P&L accounts also? If so examples please.
Regards
Odaiah Pelley

Hi ,
OPEN ITEM MANAGMENT-Items posted to accounts managed on an open item basis are marked as open or cleared. The balance of these accounts is always equal to the balance of the open items.
Example:
A goods receipt/invoice receipt (GR/IR) clearing account should be managed on an open item basis so that you can check at any time whether invoices have been received for the goods received for an order.
Set up accounts without open item management if no offsetting entry is to be made against a posting to this account.
Examples
Accounts that are managed on an open item basis include:
Clearing accounts:
Bank clearing account
Payroll clearing account
Cash discount clearing account
GR/IR clearing account
Accounts that are not managed on an open item basis:
Bank accounts
Tax accounts
Raw material accounts
Reconciliation accounts
These are managed implicitly using the subledger open item function.
Profit and loss accounts
Materials Management (MM) accounts posted with a posting key that has account type 'M'
Hope this will help you
Regards

Email - Flag set to seen on server

Hi Experts,
In my application, the user reads his inbox in the Exchange Server for a particular mail. But some of the clients have their flags set as seen on the server when they recieve mails on outlook. In this case, the particular mail is unread in his Inbox, but the flags are set to seen on the server. My application access the mail server. The company policy does not allow most to keep a copy of their mail on the mail server. So how do I change my application in a way that this issue becomes solved.
Regards,
Abdullah

answered

Count for item records reaches 999 the second idoc gets triggered!

Hi Experts,
     I have an issue. Sender is file and receiver is idoc with a header and item level records. Only one header and n number of records can be there.
Now we want to make this way that as soon as the count for item records reaches 999 the second idoc gets triggered.
Hints / Solutions Pls.
Regards,
Arnab .

incorporate mapping logic such that for every 999 item records create new IDoc node
check with this UDF for IDoc node mapping, item records will be input to UDF
int count = a.length;
int k=999;
result.addValue("");
for(int i=0;i<count;i++)
      if (i>=k){
          result.addValue(""); // if records > 999, add IDoc node
          k=k+999;
Do rest of the mapping accordingly

Sales Order line item Partner Function issue.

Dear Guru's
I want to assign the (Employee response) partner function ER more than 5 times in Sales Order line partner function tab, but system is not accepting for that.
Please suggest me how to over come this issue with out assigning the u201CERu201D partner function more than 5 times in sales order line item Partner determination procedure.
Regards,
Hari Krishna

sent this to SD module (Sales and Distribution) Forum
this is PS module and we do not deal with this object

Item partner flag set in Orders06 Idoc

Similar Messages

Maybe you are looking for