"No item partner".

Dear experts!
Thank you for your attention!
When I was checking item categroy for "Sales Processing using Third Party (w. Shipping Notification)", I discovered the
partner determination procedure is " T: No item partner".
Then I check the " T No item partner", there is no partner function in this proc.
Is that mean: item with this partner determination proc. will not be proposed or checked in partner function at item level??
Best regard!
Tangdark
Edited by: tang dark on Sep 19, 2008 9:22 AM

Yes, no partner at item level only header level, i.e. partner funcitons will be determined at header and replicated to all the items

Similar Messages

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

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

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

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,

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

Change Date for Order Item Partner Changes

When I make a change to a partner on an Order Item the Change Date VBAP-EDATU is not populated. can anyone recommend a way to have this field filled for all changes to any fields on an Order (header and Item)?

It can be done by WF, Why you need a warning message?
Anyhow check badi
PT_GEN_REQ or PT_ABS_REQ,

Pop up when Sales order item partner is changed

Hi,
Can we get a pop up when a partner function in sales order item line is changed which should display the text maintained for the customer in XD02??
If so please let me know..
Thanks & regards,
Santhosh
Edited by: SS on Jun 8, 2009 3:27 PM

Hi..
Put option C there & save.
This filed defines result of ava chk in sales order.
(Rule for transferring the results of the availability check
Specifies for a particular sales area how the system reacts when the availability check determines that the inventory is insufficient to satisfy the order quantity.
Use
When inventory is insufficient, the system can react in one of two ways:
The system presents a pop-up window and you choose from different alternatives, or
The system automatically proposes one of the alternatives (no pop-up window appears)
Example
The system can, for example, automatically confirm the delivery proposal. The delivery proposal consists of the quantity that is available for delivery by the requested delivery date.)
Also make sure in OVZ8 you have ticked Av Chk for your schedule line category
Regds
MM
Edited by: MANOJ MAHAJAN on Oct 26, 2009 12:21 PM

Sales Order Line Item Partner Address overrides in VA01/VA02

Dear All.
I noticed that I can not update the address details of the standard ship-to on the line item level of the sales order (VA01/VA02) without first typing over the ship-to account number. If I do this, then it's possible.
I found an OSS note on the subject ( 380507 -#2 ), which basically states the reason for this.
While it's a little inconvenient for the online business user, this is really troubling for interfaces where we can't manually type over the account number.
Does anyone have any ideas on getting around this without major design changes? Could there be a customer function, userexit, other as a way of opening this up?
Many Thanks!

Hi,
It is difiicult for the system to determine which address you are typing in, if you dont specify a ship to party.
What you could do is assign the SH to you SP in master data and maintain the delivery/shipping address in the SH.
As soon as you enter the SP you SH would be populated automatically with the address.
You may also have multiple SH's for the same SP. The system would ask you to choose your SH during Order processing.
Hope that helps.
Regards,
Amit

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.

Mandatory partner function at sales order item level

Hi all,
I'm customizing partner schema at item level for sales order. I have created a custom partner function, I put it in a new sales order item partner procedure and i set this partner function as mandatory (I want that system show me a message if this function is missing at item level in sales order). This partner function is defined only at sales order item level (not at header level or customer master).
If i create and save a sales order with an item type that use the item partner procedure I have created, system don't show me any message for the item custom partner function missing, else if it is set as mandatory in sales order item partner procedure.
I have read some posts in these forums about this functionality, but it seems a different situation.
Someone had a similar type of problem?
Thank you in advance for any possible suggestion.
Regards
Gianpaolo

Hi,
First you have to create a new partner function.
Then assign that partner function to the account group.
Then assign that partner function to partner determination procedure for the item category.
Over here click on the mandatory button also.
Then assign that partner determination procedure to item category.
Then to XD02 and give your customer number and in the partner tab maintain the data for that partner function.
Now go to VA01 and create your sales order you will see you partner function.
If you wont have maintained it in the customer master then it will prompt an error.
Regards
Raj.

Need a user exit to add custom partner function in sales order @ item level

Hi,
Need a user exit to add custom partner function in sales order at item level. Goto --> Item --> Partner.
Thanks,
Thiyagi

HI Leo
To add a condition price for a condition type, this has to be assigned in the pricing procedure. For each condition type in a pricing procedure, we will have access sequences. If we follow this approch, the price is automatically extracted basing on the access sequences when condition records are maintained. For this, no coding is required and everything can be done by configuration by Functional consultant.
Naren is right to point out on the same.
If you need to change the price for a particular condition which already exists, you can go by pricing routines. Go through transaction VOFM for the same.
I advice you to discuss with your functional consultant and understand the requirement and then go for modifying accordingly.
Kind Regards
Eswar

Partner Function Address change at line item level - Item Partners checkbox

Hi guru, we have a requirement that we need to change the address for partner function at line item level without changing the partner number. Currently the ship-to partner function address is automatically coming from the header although the number is modifiable but not the address (when double click into the partner number, the pop-up is grayed out). It is probably because the Item partner check box for the shipto partner is not checked (field name: SD_PARTNER_POSFLAG). However that field is not modifiable in VA02 either.
If the shipto partner number is overwritten, then the item partner check-box is automatically checked and allows address chanage. Is there a way in the configuration that can default the 'item partners' checkbox for certain partner so the address can be changed without the need to overwrite the account?
Any advice is appreciated.
Thank you.

If the item level ship-to party is derived from header partner function, but you want to change the address at item screen rather than header level. On item screen, enter the same function, the same number again in a new line, "item partner SD_PARTNER_POSFLAG" is then ticked. Then proceed to the address change.
No need to do modification.

Some items doesnt get copied with header partner

Hi ,
I have a issue with an order, where when teh order header partners are redetermined, (ship to), some of the items on the order doesnt get copied with the new ship to.
There is a check box at the item partner screen which is been ticked only for the items where thsi change doesnt take place.
It indicates that 'Partner valid at item level, if this indicator has been activated, the partner is valid at item level.'.
Could someone please advice the reason as to whta the check box means as well as the reason as to why the header partner doesnt get copied to the line item partner.
Thanks,
Keshini

Hi,
Read OSS Note 550073 - FAQ: SD Partner Determination I, points 1 and 2.
The description from the note is,
1. Question: Why is a new partner determination not executed when I change the partner ?
Answer: The partner determination always runs when you create a document. Then dependent partners are automatically determined and checked. If in the existing document you change a partner, the system does not run a redetermination of the partners (except when the sold-to party is changed). This works as designed and possible dependent partners are not redetermined.
2. Question: Does the partner determination take place on item level ?
Answer: An item partner determination is not provided in the standard system. You can enter item partners manually. Here, in Customizing of the item partners you can specify which partner functions should be allowed on item level and which not. The header partner functions are always allowed on item level. On item level, if you enter a partner, it is visualized by the item partner flag. For an item partner you can change the address data, header partner addresses cannot be changed on item level. The logic of the item partners is: If for an item there is no partner, the header partners are displayed. If as described above you enter a partner on item level, this partner exists on item level. If for a partner you enter an address differing from the header but the partner should stay the same, you can just enter the partner again manually for the respective item. Thus the partner becomes an item partner and the address can be changed.
Regards,

Necessity of the Partner Determination Procedure at Item Level

Hi Gurus,
What is the necessity of the Partner Determination Procedure at Item Level and in what case it is useful?
Regards,
Sarosh.

Dear,
It may happen that in a business transaction the partner in the document header does not apply to all items, for example, if specific goods for a customer are normally delivered to another ship-to party.
In sales documents and billing documents you can enter one of the deviating partners from the document header at item level.
You have planned to have the partner function in the partner determination procedure for sales document items or billing items.
When creating a document , the system copies the document header partners to the items. If you want to define another partner than the one in the document header at item level, overwrite the proposal from the item partner screen.
You have planned the partner function ship-to party in the partner determination procedure in Customizing for sales document items and have defined this as changeable.
Create a customer sales order as usual.
The system copies the partner from the customer master into the document header and then from the document header into the items.
Select the item, that should receive a deviating partner.
Choose Goto --> Item --> Partners.
The partner screen for the item appears. Here you can overwrite the changeable partner functions.
Try to read the SAP help. U will find some more info.
reward if helpful
Krishna Chaitanya

"No item partner".

Similar Messages

Maybe you are looking for