S6 Active sales

Would anyone who sells AT&T phones care to comment on the daily sales of the S6 Active? Have S6 Active sales improved over previous Active phones?

Hi there! @Carrboro_NC
Thanks for posting your question. Since we want to remain unbiased on the phones we sell, unfortunately we won’t be able to provide that information.
Thanks!
Charise

Similar Messages

Mi iphone se restauro y no se activa, sale un mensaje que el servidor no esta disponible que hago...

mi iphone se restauro y no se activa, sale un mensaje que el servidor no esta disponible que hago...

Hola, está con jailbreak? Si es así, es normal que pase a ser un sistema inestable. Si no es así restauralo y luego dale a la copia de seguridad que tenías del iPhone en iTunes.
Acá te dejo un link de Apple... Ojalá te ayude
http://support.apple.com/kb/HT1808?viewlocale=es_ES

Adding lines to the currently active sales order

I need to add lines to the order currenlty being entered by the user based upon various rules that i have created in an addon. I can call the addon and calculate the values I require but I cannot see how to poke a number of libes and quantities back into the calling sales order.
Can anyone advise please?
Gordon Wood

Gordon,
If you search this forum on something like "add lines", you will find many posts that will assist you with your question such as this post ...
Re: Add order lines to Existing order
HTH,
Eddy

Sales office is active/inactive

HI all,
in my requirement i had to find out the sales offices which are active...
please tell me how can i find active sales offices...

hi all,
i got the solution to this .....
as our client is maintaining a Ztable for inactive sales offices...
so now i have to take all the sales offices from TVKBT table and subtract the inactive sales offices which r in the Ztable..
thank u very much for responding me.....

Reg: AR customer activity

Hi Consultants ,
i have requirement to report the ar customer who has any activity(sales,payment ,adjustment,or misc receipt ) in last 7 days.
does anyone help me on this query ? if you have any query please post here
Thanks in advance
Anu.

Hi siva,
For Year End 1999, SAP provides a robust new utility to perform Year End Reporting . As in previous years, the new utility can be accessed under the following menu path:
Human resources -> Payroll -> Subs.activities -> Annual -> End of year -> Processing -> Year End Reporting
In 1999, SAP supports processing for the T4, T4A, T4A-NR, Relevé 1, and Relevé 2. For further information on the Year End Reporting utility, refer to the report documentation.
regards........ Sri

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

Sale Order flow to CO-PA

Hi All,
We have activated Sales Order value flow to CO-PA (COPA doc.type "A"). We also have credit management activated.
When I create a sales order which has the credit status "not approved", then the order does not post any COPA document. Once the credit block is released in VKM1 for the sale order, the credit status changes to "Released" and COPA document is generated immediately.
The requirement is...the user wants to have COPA document generated irrespective of the credit status. i.e. even if the credit status is "not approved", it should create a COPA document.
Pl.let me know if anybody has come across this situation and how to solve it.
Regards
Srinivasan G

Hi
There is a note (Note No.214059) which gives us the option of using posting to CO-PA for credit blocked orders
I tried this and it works fine.
There is also one BADI available which can be used as an alternative to this note.
The advantage of BADI is that it can be used for any specific criteria like company, sales org., etc. whereas if you apply the above note, then this feature is applicable to all sale orders.
Regards
Srini

Header Details of pending * open Sales Order.

HY All Experts.
PL Read Follwing Code. i wnt to Header data of pending and open SO.
i used vbuk-lfstk. for So status. it is right.
FORM data_retrieval.
SELECT VBELN NETWR KUNNR FROM VBAK INTO (ITAB-VBELN,ITAB-NETWR,ITAB-KUNNR) WHERE VBELN IN VBELN.
SELECT NAME1 FROM KNA1 INTO (ITAB-NAME1) WHERE KUNNR = ITAB-KUNNR .
SELECT BSTKD BSTDK FROM VBKD INTO (ITAB-BSTKD,ITAB-BSTDK) WHERE VBELN = ITAB-VBELN.
SELECT VSNMR_V FROM VBAK INTO (ITAB-VSNMR_V) WHERE VBELN = ITAB-VBELN.
*SELECT EDATU FROM VBEP INTO (ITAB-EDATU) WHERE VBELN = ITAB-VBELN.
SELECT LFSTK FROM VBUK INTO (ITAB-LFSTK) WHERE VBELN = ITAB-VBELN and lfstk not like 'C'.
APPEND ITAB.
ENDSELECT.
ENDSELECT.
ENDSELECT.
ENDSELECT.
ENDSELECT.

Hello anjana,
   Actually your question is some confusing, but if u want to get eldest change as active sales order then logic is as follows:
1. On base of OBJNR u have to get UDATE from JCDS table
2. then write logic as:
SORT i_jcds BY objnr stat chgnr DESCENDING.
      LOOP AT i_jcds INTO wa_jcds1.
        CLEAR lv_stat.
        lv_stat = wa_jcds1-stat.
        AT NEW objnr.
          AT NEW stat.
            CLEAR: wa_tab.
            wa_tab-objnr = wa_jcds1-objnr.
            wa_tab-stat = lv_stat.
          ENDAT.
        ENDAT.
        IF wa_jcds1-inact = 'X'.
          CLEAR lv_tabix.
          IF sy-tabix > 1.
            lv_tabix = sy-tabix - 1.
          ELSE.
            lv_tabix = 1.
          ENDIF.
          READ TABLE i_jcds INTO wa_jcds2 INDEX lv_tabix.
          IF sy-subrc = 0.
            wa_tab-chgnr = wa_jcds2-chgnr.
            wa_tab-udate = wa_jcds2-udate.
            wa_tab-utime = wa_jcds2-utime.
            APPEND wa_tab TO i_tab.
          ENDIF.
          CONTINUE.
        ELSE.
          wa_tab-chgnr = wa_jcds1-chgnr.
          wa_tab-udate = wa_jcds1-udate.
          wa_tab-utime = wa_jcds1-utime.
        ENDIF.
        AT END OF objnr .
          AT END OF stat.
            APPEND wa_tab TO i_tab.
          ENDAT.
        ENDAT.
      ENDLOOP.
      DELETE ADJACENT DUPLICATES FROM i_tab COMPARING objnr stat.
      SORT i_tab BY objnr stat udate utime.
      DELETE ADJACENT DUPLICATES FROM i_tab COMPARING objnr.
3. now in i_tab table u'll get eldest UDATE
Hope its work for u.
Thanks & Regards,
Sumit Joshi

Set sales employee as inactive

Hello,
in SAP BO you can add sales employee, but can not be erased. Number of buyers is growing - when you create a document (invoice, ...) list of sales employees becomes confusing. We would welcome the possibility of setting sales employee as INACTIVE. The documents would then be offered only to active sales employees.
Many thank.
Alexandra Herichová

Hi,
thank you very much for your comment. I would like to inform you we are currently working on de-activation of Sales Employee (S.E.) in B1, where option to define active / inactive S.E. will be available. Consequently inactive S.E. will be by default not visible in all relevant lists, however user will have an option to report all data for all existing S.E. due to backward compatibility.
Other areas are planned to be covered in a future as well. Please consider this as a potential Patch candidate and not as an SAP commitment.
In case of any questions, feel free to contact me.
Best Regards,
Martin Pavlinsky
B1 Product Definition

Sales information systems

please help me in SIS how i can configure the system so that based on the order type say OR standard order type i can get all the related information in SIS based on the order type

Hi Vikas,
Please find below the complete document on SIS:
Step-by-Step Guide to Activating a Self-Defined SIS Structure
IMG menu path for SIS: IMG>Logistics General>Logistics Information System (LIS)
Figure 1: IMG menu path for SIS configuration steps
Task 1: Create Self-Defined Information Structure
Use transaction code MC21 (menu path Logistics Data Warehouse>Data Basis>Information Structures>Maintain self-defined information structures> Create) to create a Self-Defined Information Structure. Give a customer-range number 990 (any available number between 501 and 999). To make it easier, use copy from to copy structure from S001.
Figure 2: Create a Self-Defined Info Structure
Figure 3: Structure S990 is created as a copy of S001
Structure S990 is created as a copy of S001. Accordingly, you will see defaulted characteristics and key figures. Review various settings (unit, sum, etc.).
Add two more characteristics: Sales Order Number and Item Number.
Click on Choose Characteristics Icon and then click on Selection List icon to choose fields from field catalogs.
Choose field catalog SD: Bus transaction (order) by double-clicking it. Double-click on Sales Document and Sales document item from field catalog fields (you may need to scroll-down).
Figure 4: Choose fields Sales Document and Sales Document Item from Field Catalog
You can view technical names by toggling the Switch Display icon.
Figure 5: Switch display to view technical names
Make sure that you have selected correct characteristics as: MCVBAK-VBELN and MCVBAP-POSNR.
Click on Copy + Close icon and then click on Copy icon to accept the changes.
Review information
Double-click on characteristics and key figures to review technical information. This step is not mandatory, just for information.
Figure 6: Review technical field information for characteristics: Customer (KUNNR), Sales Order (VBELN), Item (POSNR) and Key figures: Incoming Order (AENETWR), Open Order (OAUWE)
System displays the generation log.
Figure 7: Generation log for Structure S990. Table S990E is Structural Information for Table S990
Task 2: Maintain Update Groups
SIS IMG>Logistics Data Warehouse>Updating>Updating Definition>General Definition Using Update Groups>Maintain Update Groups
Figure 8: Update Groups for Sales and Distribution
No new entries need to be created. You can use the existing system-delivered update groups. Use Update Group (UpdGrp) 1 for the standard order process of: SIS: Sales Document, Delivery, Billing Document and use UpdGrp 2 for the SIS: Returns, Returns Delivery, Credit Memo.
Task 3: Maintain Update Rules
SIS IMG>Logistics Data Warehouse>Updating>Updating Definition>Specific definition using Update Rules>Maintain Update Rules>Display
Info Structure S001 and Update Group 1.
Before we create update rules for S990, let's review how update rules are defined for S001. Review rules for Characteristics and key figures.
Figure 9: Update Rules for combination of Structure S001 and Update Group 1
Double-click to review specific details of the update rule for Key Figure Incoming Orders. Note that the event is VA Sales Order creation.
Figure 10: Update rules for Key Figure Incoming Orders
Figure 11: Characteristics for Incoming Orders
Similarly review details of Key Figure Sales. Note that the Invoiced Amount (Sales Amount) is updated by event VD Billing Document.
Figure 11: Update rules for Key Figure Sales
Figure 12: Characteristics for Sales
Similar to Update Rules of S001, we need to create Update Rules for our Self-Defined Structure S990.
SIS IMG>Logistics Data Warehouse>Updating>Updating Definition>Specific definition using Update Rules>Maintain Update Rules>Create (transaction code MC24). To make it easier, use copy from to copy update rules from S001.
Figure 13: Create Update Rules for Structure S990
Please make sure the Source information is properly updated for all the characteristics. Since you copied the rules, the sales order and item rules are defaulted too. Make sure appropriate changes are made for events VC (delivery) and VD (Invoice).
Figure 14: Source Characteristics for Sales Document and Item
Since we copied the Update Rules, the source field and table information is also copied. We need to change appropriately to make sure correct source information is populated. Click on Rules for charact and verify source information for every key figure, by clicking on previous key figure and next key figure.
Figure 15: For Event VD Billing Document, Sales Document and Item are present in MCVBRP table
Figure 16: For Event VC Shipping, Sales Document and Item are present in MCLIPS table
Change Source information for following to MCVBRP-AUBEL and MCVBRP-AUPOS:
o Sales
o Gross Invoiced Sales
o Net Invoiced Sls 1
o Net Invoiced Sls 2
o Inv freight Chrgs
o Bill Docmnt PS5
o Bill Docmnt PS6
o Invoiced Qty
o Invoiced sls cost
Change Source information for following to MCLIPS-VGBEL and MCLIPS-VGPOS:
o Open Orders
o Open Order Qty
- Save and Generate by clicking on the Generate icon.
Similarly, copy update rules for Update Group 2. Transaction Code MC24.
Repeat these rules for the combination of information structure S990 and update group 2. (Copy from info structure S001 and Update group 2).
Figure 17: Maintain Update Rules for Structure S990 and Update Group 2
Again, click on Rules for charact and verify source information for every key figure, by clicking on previous key figure and next key figure.
Change Source information for following to MCVBRP-AUBEL and MCVBRP-AUPOS:
o Credit Memos
o Gross Credit Memos
o Net Credit Memos 1
o Net Credit Memos 2
o Credit memos freight
o Credit memos subtotal 5
o Credit memos subtotal 6
o Credit memos qty
o Credit memos cost
Task 4: Maintain Statistics Groups
Maintain Statistics Groups
Maintain Statistics Groups for Customers, Materials, SD Document Types etc. Most of the pre-defined settings are enough. Make sure that settings are updated for customized objects too, e.g., SD document types for your organizations.
Also, make sure that the customer (sales view) and material Master records are updated with appropriate Statistics Groups.
Figure 18: Maintain and assign statistics groups. IMG path: Updating> Updating Control> Settings: Sales> Statistics Groups
- Maintain Statistics Groups for Customers (OVRA)
Figure 19: Statistics Groups for Customers
- Maintain Statistics Groups for Material (OVRF)
Figure 20: Statistics Groups for Materials
- Maintain Statistics Groups for Sales Document
Figure 21: Statistics Groups for Sales Documents
- Assign Statistics Groups for relevant Sales Document Type
Figure 22: Assign Statistics Groups to relevant Sales Documents
- Assign Statistics Groups for each Sales Document Item Type
Figure 23: Assign Statistics Groups to relevant Item Categories
-Assign Statistics Groups to each Delivery Type
Figure 24: Assign Statistics Groups to relevant Delivery Types
-Assign Statistics Groups to each Delivery Item Type
Figure 25: Assign Statistics Groups to relevant Delivery Item Categories
- Determine Billing Document Types Relevant to Statistics
Figure 26: Assign Statistics Groups to relevant Billing Types
Note: As mentioned earlier, most of the settings are already set in standard system. Make sure that customized objects specific to your company are also updated appropriately.
- Update Customer Master for Statistics Relevancy
Transaction Code XD02 (Sales view, field Cust stats.Grp)
Figure 27: Assign Statistics Groups to Customer Master Records (Sales view)
- Update Material for Statistics Relevancy
Transaction Code MM02 (Sales 2 view, field Matl statistics grp)
Figure 28: Assign Statistics Groups to Material Master Records (Sales view)
Task 5: Assign Update Groups to Header and Item Levels
Assign Update Groups on Header and Item levels
For combinations of Sales Area (Sales Org, Distribution Channel, Division), assign Update groups (transaction codes OVRO and OVRP).
SIS IMG>Logistics Data Warehouse>Updating>Updating Control>Settings: Sales>Update Group
- Update Groups at Item Level
Figure 29: Update Groups at Item Level
Figure 30: Update Groups at Item Level - details
- Update Groups at Header Level
Figure 31: Update Groups at Header Level
Figure 32: Update Groups at Header Level - details.
Task 6: Activate SIS Update
Lastly, Activate SIS Update for the Structure (transaction code OMO1)
SIS IMG path: Logistics Data Warehouse>Updating>Updating Control>Activate Update>Choose Activity as Sales and Distribution.
Let's update our SIS structure S990 with period as Month and update option of Asynchronous Updating (2).
Figure 33: Activate SIS Update for S990
SIS tests with Sales Order Processing (Order>Delivery>Invoice)
Create a Sales Order, transaction code VA01
Figure 34: Create a standard Sales Order and Sales Order 6437 is saved
(Pricing details)
Figure 35: Pricing Details for the Sales Order
Execute transaction MC30 to find out which information structures are updated. Please note that this step is not mandatory.
Transaction code MC30 is worth mentioning here. This transaction code, provided user parameter MCL is set to X in users master record, provides analysis of which structures are updated for the activity. It generates a log of updates to Information Structures and detailed analysis. Since, it can take resources, it is advisable not to set user parameter MCL in productive system.
Figure 36: Transaction MC30 lists that Structure S990 is updated
Double-click on S990 line to view more details.
Figure 37: Transaction MC30 details for Structure S990
Execute Standard Analysis Report.
SAP>Logistics>Sales & Distribution>Sales Information System>Standard Analyses>Self defined analysis (transaction code MCSI). (Choose Structure S990). Enter appropriate values and execute.
Figure 38: Standard Analysis report for Structure S990
Figure 39: Standard Analysis report for Structure S990 for given criteria
Create a Delivery/PGI and review its impact on Standard Analysis Report.
Delivery 80007493 Saved, execute MC30 to review the update log.
Figure 40: At the time of Delivery/PGI, Structure S990 is updated
Figure 41: At the time of delivery, since Order is no more open, Open Order value is reduced
Please note in the Standard Analysis report that the Open Order value is reduced accordingly.
Figure 42: Standard Analysis report reflects correct Open Order value
Create an Invoice and review SIS report.
Invoice 90021696 saved. Review Update log with MC30.
Figure 43: Invoiced/Sales amount is updated at the time of invoice
Note that in the Standard Analysis report, Sales value has increased.
Figure 44: Standard Analysis report reflects correct Sales Amount
Summary changes in Information structure depending upon Sales activity
Sales Order: Note Open Order has EUR 49.60 value.
Delivery: Note Open Order value is reduced.
Invoice: Note Sales column reflects correct invoiced amount.
Figure 45: Summary Information Structures reflects correct values depending upon the status of transaction: whether order created, shipped or invoiced
Please Reward If Really Helpful,
Thanks and Regards,
Sateesh.Kandula

Sales Organization merger

Hello All,
I would like to merge Sales org 0410 and 0420 together and will handle through single sales organization only.
I know that each sales org have their own Company code.
Could anyone please tell me how can I proceed for this requirement.
User has created a huge document for various module of each sales organization.
This will help me if I will get relevant information in Step.
Regards
Ajit

Earlier both the Sales Organizations 0410 and 0420 were active & business has created Document in respective Sales Orgns?? Correct.
Now in future you want to have all the Transactions in only single Sales Organizaton.
But the Document Created in past are legally acceptable documents & Sales Organizations cannot be merged with effect from past date. Means the document created in past will remain under respective Sales Organizations & cannot be changed.
If in future you want only one Sales Organization, say you have to close 0420 Sales Orgn & only keep 0410 as active Sales Orgn.
Now close all the open documents in 0420 (Open Orders, Deliveries, Invoice & other docs). Once everything is closed, assgn the Organizations elements (divisions, distn channels, etc of 0420 to 0410) & instruct the users to use 0410 henceforth.
If required delete the assignments of 0420, but it is not advisable.
Hope this helps,
Thanks,
JIgnesh Mehta

Sales Group - sales allocation

hi ,this is regarding the sales allocation among a members of the sales team.i have configured sales teams as Sales Group in SAP.
Now the what ever the sales ,,this sales group does goes as the teams achievement.
Now the requirement is ,is there any way that we can allocate the the total sales among the teams members(can be 3 or 5 or 6 individualscould be 10 also ) % wise in SAP.
like for example , if the sale is of rs100 which slaes group (of 4 members) has achived then can we assign
this 100rs as 10% to A,20% to B,50% c,20% to d .
I have activated sales infotype with help of MY HR consultant ,but we can only assign as employee resposible (any numbers)as partner functions in the Customer master, but how do we allocate the sales in % wise among th teams mebers.
any one please advice ,if this canbe addressed in SAP.
shashi

thanks sanjay for your reply.This sales allocation they want to calculate for sake of incentive calculations.
For example in a sales team or sales pool (the sales target will be a teams target,that is target divided by number of people).So should be the achievment as well(that is waht ever the total sales are ,should be divided by number of people equally).
But the scenario here is different ,though the team has one target ,the achivement has to divided according to the allocation of the Say area manager or sales manager.
This allocation percentages ar decided bythe management.
So if we assign the employee responsible at the partner functions during the sale sorder processing the credit goes to that peticular employee,but since it is pool or teams target ,then the sales has to go to every one in team.
so if we assign all the team members as employee responsible for that perticular sale ,then if the sale is of say 100INR then all the team members will get sales credit of 100inr each ,so the sales figure will be 500inr but not 100inr.
Hope You have understood the scenario.
shashi

Help needed in BI content sales over view cube

We have activated sales over view cube. Just wondering about update routines for each of KFs. They all have similar logical patterns in examples below
Could any one explain me why this logic of multiplying by -1 is applied for each KF.
Also, I need to know, if I should use same routines for updating in ODS in place of updating directly in sales overview cube.
Example - 1
RESULT = COMM_STRUCTURE-/BIC/ZSHIPQTY.
IF COMM_STRUCTURE-DOC_CATEG CA DEB_CRED.
    RESULT = RESULT * ( -1 ).
ENDIF.
RETURNCODE = 0.
Example - 2
RESULT = COMM_STRUCTURE-ACT_DL_QTY.
IF COMM_STRUCTURE-DOC_CATEG CA CREDIT.
    RESULT = RESULT * ( -1 ).
ENDIF.
Example -3
CLEAR RESULT.
RESULT = COMM_STRUCTURE-NO_DEL_IT.
IF COMM_STRUCTURE-DOC_CATEG CA CREDIT.
    RESULT = RESULT * ( -1 ).
ENDIF.
RETURNCODE = 0.
Points will be awarded for good answers.
Thanks
Jeff
Edited by: Jeff Edwards on Aug 11, 2008 7:00 AM
Edited by: Jeff Edwards on Aug 11, 2008 7:00 AM

So instead of putting update routine in ODS update rule, I can put it between ODS and cube.
yes.
Now, question is.. is 1:1 KF mapping in ODS is fine.
yes.
Initial ODS KF value:     30
ODS set to overwrite: credit posting 10
KF value in ODS: 10
Update to cube: -10
values of KF in cube:    30
second value:             -10
during reporting 30 + (-10) = 20.
All this is hypothetical for your understanding. The real data model should be based on ur requirements. This is one way of doing it.

Error while loading data from sales order header via LO-Cockpit extraction

Hi Guys
I activated sales order header d/source 2lis_11_vhdr using 3x funtionality ontop of BI 7.0 dataflow. While creating infocube I am getting an error saying that " Infoobject 0RATE_TYPE is onl allowed as an attribute (not in infoprovider)"
Also while creating the same cube I am not able to move UNIT objects to UNIT dimension (as it dont allow me to drag and drop)
Can anyone please advise me why I am not able to activate cube based on above mentioned error.
Thanks in advance.
regards

Hi,
To be able to load transaction data for 2010, you should have the master data for that in the time dimension. For this, you need to go to BPC admin and add the dimension members in the time dimension manually.
Alternatively, you can have a process to import master data from BI system also. You can do some more research on this. Please refer to the below link from help.sap:
http://help.sap.com/saphelp_bpc75_nw/helpdata/en/46/fcc2ef34ee439aaa56a4f6ba001e4d/content.htm
http://help.sap.com/saphelp_bpc75_nw/helpdata/en/e0/532af2d0804218a59157136bb63a98/content.htm
http://help.sap.com/saphelp_bpc75_nw/helpdata/en/73/0f917879fd416099d04fb4c49889e0/content.htm
http://help.sap.com/saphelp_bpc75_nw/helpdata/en/88/e16046853041b391314a91bfe3618b/content.htm
Hope this helps.

Sales Order Creation for Contracts

Hi,
When I execute FM 'CRMXIF_ORDER_SAVE', it is going to dump with error
"Inconsistency between Dictionary types "CRMXIF_BUSTRANS_ITEM_T". "
if someone could help me sorting this out that would be great.
I would also like to know if there is any other FMs for creation of order for contracts.
Thx,
Vinod

Hi Vinod,
You need to pass the input fields for every field you populate.
Here is the corrected code. I have marked the modifications in BOLD.
**Passing sample data to those internal tables to test.
it_organisation-dis_channel = '01'.
it_organisation-division = '01'.
it_organisation-sales_org = 'PAT'.
it_organisation-sales_org_resp = 'PAT'.
APPEND it_organisation.
*it_products-partner_prod = '28811'.
*APPEND it_products.
CALL FUNCTION 'GUID_CREATE'
IMPORTING
EV_GUID_16 =
EV_GUID_22 =
ev_guid_32 = zguid_32.
it_header-guid = zguid_32.
it_header-process_type = 'ZWK8'.
it_header-logical_system = 'C4DCLNT200'.
it_header-posting_date = '20060525'.
APPEND it_header.
<b>*HEADER INPUT FIELDS
IT_INPUT_FIELDS-REF_GUID = ZGUID_32.
IT_INPUT_FIELDS-OBJECTNAME = 'A'. (A for header and B for item)
IT_INPUT_FIELDS-OBJECTNAME = 'ORDERADM_H'.
IT_INPUT_FIELDS-FIELDNAME = 'GUID'.
APPEND IT_INPUT_FIELDS.
IT_INPUT_FIELDS-REF_GUID = ZGUID_32.
IT_INPUT_FIELDS-OBJECTNAME = 'A'. (A for header and B for item)
IT_INPUT_FIELDS-OBJECTNAME = 'ORDERADM_H'.
IT_INPUT_FIELDS-FIELDNAME = 'PROCESS_TYPE'.
APPEND IT_INPUT_FIELDS.
IT_INPUT_FIELDS-REF_GUID = ZGUID_32.
IT_INPUT_FIELDS-OBJECTNAME = 'A'. (A for header and B for item)
IT_INPUT_FIELDS-OBJECTNAME = 'ORDERADM_H'.
IT_INPUT_FIELDS-FIELDNAME = 'LOGICAL_SYSTEM'.
APPEND IT_INPUT_FIELDS.
IT_INPUT_FIELDS-REF_GUID = ZGUID_32.
IT_INPUT_FIELDS-OBJECTNAME = 'A'. (A for header and B for item)
IT_INPUT_FIELDS-OBJECTNAME = 'ORDERADM_H'.
IT_INPUT_FIELDS-FIELDNAME = 'POSTING_DATE'.
APPEND IT_INPUT_FIELDS.
ORGMAN INPUT FIELDS
IT_INPUT_FIELDS-REF_GUID = ZGUID_32.
IT_INPUT_FIELDS-OBJECTNAME = 'A'. (A for header and B for item)
IT_INPUT_FIELDS-OBJECTNAME = 'ORGMAN'.
IT_INPUT_FIELDS-FIELDNAME = 'DIS_CHANNEL'.
APPEND IT_INPUT_FIELDS.
IT_INPUT_FIELDS-REF_GUID = ZGUID_32.
IT_INPUT_FIELDS-OBJECTNAME = 'A'. (A for header and B for item)
IT_INPUT_FIELDS-OBJECTNAME = 'ORGMAN'.
IT_INPUT_FIELDS-FIELDNAME = 'DIVISION'.
APPEND IT_INPUT_FIELDS.
IT_INPUT_FIELDS-REF_GUID = ZGUID_32.
IT_INPUT_FIELDS-OBJECTNAME = 'A'. (A for header and B for item)
IT_INPUT_FIELDS-OBJECTNAME = 'ORGMAN'.
IT_INPUT_FIELDS-FIELDNAME = 'SALES_ORG'
APPEND IT_INPUT_FIELDS.
IT_INPUT_FIELDS-REF_GUID = ZGUID_32.
IT_INPUT_FIELDS-OBJECTNAME = 'A'. (A for header and B for item)
IT_INPUT_FIELDS-OBJECTNAME = 'ORGMAN'.
IT_INPUT_FIELDS-FIELDNAME = 'SALES_ORG_RESP'.
APPEND IT_INPUT_FIELDS.</b>
CALL FUNCTION 'BAPI_BUSPROCESSND_CREATEMULTI'
TABLES
header = it_header
ITEM =
ACTIVITY =
sales = it_sales
PARTNER =
organisation = it_organisation
SHIPPING =
APPOINTMENT =
TEXT =
SERVICE_OS =
STATUS =
<b>INPUT_FIELDS = IT_INPUT_FIELDS</b>
CREATED_PROCESS =
RETURN = it_return
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 = it_products
OBJECTS =
PAYPLAN =
PAYPLAN_DATE =
CONFIG_FILTER_CFG =
CONFIG_FILTER_INS =
CONFIG_FILTER_PRT =
CONFIG_FILTER_VAL =
ACTIVITY_I =
it_objectstosave-guid = it_header-guid.
APPEND it_objectstosave.
CALL FUNCTION 'BAPI_BUSPROCESSND_SAVE'
EXPORTING
update_task_local = ' '
save_frame_log = 'X'
IMPORTING
log_handle = l_log_handle
TABLES
objects_to_save = it_objectstosave
saved_objects = it_savedobjects
return = it_return.
IF NOT it_savedobjects[] IS INITIAL.
CALL FUNCTION 'BAPI_TRANSACTION_COMMIT'
EXPORTING
wait = 'X'.
IMPORTING
RETURN =
ENDIF.
IF sy-subrc = 0.
ENDIF.

S6 Active sales

Similar Messages

Maybe you are looking for