Blocking of a cost center in the creation of a Purchase Order

Hi All,
Some cost centesr are obsolete and mustn't be used in the creation of a Purchase Requisition (or Purchase Order).
Block
Could anyone suggest me how to do it?
Thanks a lot
G.

Hi Rossi ,
Please go to the Cost Center Master Data -> Control tab -> Block all the indicators..
You will not be able to use these Cost Centers in Future..
Regards
Sarada

Similar Messages

Blocking the filling of a cost center in the creation of a Purchase Order

Hi All,
I've some cost center which are obsolete and mustn't be used in the creation of a Purchase Requisition (or Purchase Order).
Could anyone suggest me how to do it?
Thanks a lot
G.
Edited by: Jeyakanthan A on Jun 2, 2011 1:28 PM

Hi,
The transaction me21n uses the authorization object A_S_KOSTL for cost
center. However, the authorization object A_S_KOSTL is not related to
the cost center that is displayed in the account assignment view of th
purchase order item, but its scope is to limit the access to fixed
assets belonging to the specified cost center (see the note 856248).
There is no standard authorization object that you can use from
transaction me21n to validate the cost center that you see in the
account assignment view at item level. The same can be said about the
purchase requisition creation (me51n).
So, I have three options for you to consider.
First Option:
There is an existing possibility to perform user defined checks during
all kinds of postings which finally lead costs in CO. With transaction
OKC7 you may define a validation which is also processed during
purchasing. You can explore the possibility of achieving the
functionality you need by making customizing changes using transaction
OKC7.
Second Option:
You could use userexit enhancement MEREQ001. For further information
please see note 310154.
Third Option:
Also, you may consider instead of an authorization check for cost
centers you can activate an authorization check for G/L accounts.
Therefore the following settings are required:
I. Customizing -> Materials Management -> Purchasing -> Purchase
    Order -> Set Up Authorization Check for G/L Accounts:
    activate the G/L account authorization check for the required
    company code
II. Transaction FS02 -> View: Control data: enter the authorization
    group
BR
Nadia Orlandi

IDOC creation after the creation of a purchase order

Hi everybody,
            I want some configuration details regardign IDOC creation. The requirement is, once i create a purchase order in one system, the details should automatciaclly transfer to other system through IDOC. could any one suggest any document or detailed procedure to accomplish the task. Thanks in advance,
         Santosh.

hi santosh kumar,
Creating an IDoc Segment WE31:
The segment defines the structure of the records in an IDoc. They are defined with transaction WE31.
We will define a structure to send a text from the text database.
Transaction WE31 calls the IDoc segment editor. The editor defines the fields of a
single segment structure. The thus defined IDoc segment is then created as a data
dictionary structure. You can view the created structure with SE11 and use it in an
ABAP as any TABLES declaration.
To demonstrate the use of the IDoc segment editor we will set up an example, which
allows you to send a single text from the text pool (tables STXH and STXL) as an
IDoc. These are the texts that you can see with SO10 or edit from within many
applications.
We will show the steps to define an IDoc segment YAXX_THEAD with the DDic
structure of THEAD.
To facilitate our work, we will use the "copy-from-template-tool", which reads the
definition of a DDIC structure and inserts the field and the matching definitions as
rows in the IDoc editor. You could, of course, define the structure completely
manually, but using the template makes it easier.
The tool in release 4.0b lets you use both DDIC structures or another IDoc segment
definition as a template.
The thus created structure can be edited any time. When saving, it will create a data
dictionary structure based on the definition in WE31. The DDIC structure will retain
the same name. You can view the structure as a table definition with SE11 and use it
in an ABAP the same way.
Defining the Message Type (EDMSG)
The message type defines the context under which an IDoc is transferred to its destination. It allows for using the same IDoc file format for several different applications.
Imagine the situation of sending a purchase order to a supplier. When the IDoc with
the purchase order reaches the supplier, it will be interpreted as a sales order
received from a customer, namely you.
Simultaneously you want to send the IDoc data to the supplier's warehouse to inform
it that a purchase order has been issued and is on the way.
Both IDoc receivers will receive the same IDoc format; however, the IDoc will be
tagged with a different message type. While the IDoc to the supplier will be flagged
as a purchase order (in SAP R/3 standard: message type = ORDERS), the same IDoc
sent to the warehouse should be flagged differently, so that the warehouse can
recognize the order as a mere informational copy and process it differently than a
true purchase order.
The message type together with the IDoc type determine the processing function.
The message types are stored in table EDMSG.
Defining the message type can be done from the transaction WEDI
EDMSG: Defining the message type (1)
The entry is only a base entry which tells the system that the message type is
allowed. Other transactions will use that table as a check table to validate the entry.
IT is as shown .
EDMSG: Defining the message type (1):
The entry is only a base entry which tells the system that the message type is
allowed. Other transactions will use that table as a check table to validate the entry.
Sales Orders are being created through inbound IDocs using FM 'EDI_DATA_INCOMING'. Now a Report is required to check the status of these Inbound IDocs along with Sales Orders generated against customer Purchase Orders.
Requirement:
Sales Orders are being created through inbound IDocs using FM 'EDI_DATA_INCOMING'. Now a Report is required to check the status of these Inbound IDocs along with Sales Orders generated against customer Purchase Orders.
Processing:
The report selects, 'ORDERS' IDoc numbers & status, generated between given time range, from table EDIDC. Further, it calls Function Module 'IDOC_READ_COMPLETELY' to get the IDoc details. Then required information is extracted by reading relevant field data of IDoc segments.
sampl code:
REPORT Z_EDI_FILE_LOAD_STATUS_REPORT           .
Staus Report for Inbound IDOCs ( Sales Orders )
Program        : Z_EDI_FILE_LOAD_STATUS_REPORT
Presented By   : www.rmtiwari.com
TABLES : EDIDC.
ALV stuff
TYPE-POOLS: SLIS.
DATA: GT_FIELDCAT TYPE SLIS_T_FIELDCAT_ALV,
      GS_LAYOUT   TYPE SLIS_LAYOUT_ALV,
      GT_SORT     TYPE SLIS_T_SORTINFO_ALV,
      GT_LIST_TOP_OF_PAGE TYPE SLIS_T_LISTHEADER.
DATA : BEGIN OF T_REPORT OCCURS 0,
         IDOC_NO       TYPE EDI_DOCNUM,
         IDOC_DATE     TYPE SY-DATUM,
         IDOC_TIME     TYPE SY-UZEIT,
         SORDER_NO     TYPE VBELN,
         STP_NO        TYPE KNA1-KUNNR,
         STP_NAME(35) TYPE C,
         STP_PHONE(12) TYPE C,
         PO_NO(15)     TYPE C,
         STATUS        TYPE C,
         S_TEXT(70)    TYPE C,
         ERROR(70)     TYPE C,
       END OF T_REPORT.
--PARAMETER--
selection-screen begin of block date with frame title TEXT-S01.
select-options: UDATE for EDIDC-UPDDAT
                      default SY-datum obligatory,    "Changed On
                UTIME for EDIDC-UPDTIM .             "Changed Time
selection-screen end   of block date.
INITIALIZATION.
START-OF-SELECTION.
PERFORM SHOW_STATUS_REPORT.
*&      Form alv_grid
      text
-->   p1        text
< -- p2        text
FORM ALV_GRID.
IF GT_FIELDCAT[] IS INITIAL.
    PERFORM FIELDCAT_INIT.
    PERFORM LAYOUT_INIT.
    PERFORM SORT_INIT.
ENDIF.
PERFORM GRID_DISPLAY.
ENDFORM.                    "alv_grid
*&      Form layout_init
FORM LAYOUT_INIT.
GS_LAYOUT-ZEBRA             = 'X'.
GS_LAYOUT-CELL_MERGE        = 'X'.
GS_LAYOUT-COLWIDTH_OPTIMIZE = 'X'.
GS_LAYOUT-NO_VLINE          = ' '.
GS_LAYOUT-TOTALS_BEFORE_ITEMS = ' '.
ENDFORM.                    " layout_init
*&      Form fieldcat_init
FORM FIELDCAT_INIT.
DATA: LS_FIELDCAT TYPE SLIS_FIELDCAT_ALV.
   CLEAR LS_FIELDCAT.
LS_FIELDCAT-FIELDNAME    = 'IDOC_NO'.
LS_FIELDCAT-KEY          = 'X'.
LS_FIELDCAT-REPTEXT_DDIC = 'IDOC'.
LS_FIELDCAT-OUTPUTLEN    = 10.
Fix for ALV print bug, which puts 'N/A' over last digit
Set inttype to 'N' to stop corruption of printed ALV cell.
LS_FIELDCAT-INTTYPE = 'N'.
APPEND LS_FIELDCAT TO GT_FIELDCAT.
CLEAR LS_FIELDCAT.
LS_FIELDCAT-FIELDNAME    = 'IDOC_DATE'.
LS_FIELDCAT-REPTEXT_DDIC = 'Creation Date'.
LS_FIELDCAT-OUTPUTLEN    = 10.
APPEND LS_FIELDCAT TO GT_FIELDCAT.
CLEAR LS_FIELDCAT.
LS_FIELDCAT-FIELDNAME    = 'IDOC_TIME'.
LS_FIELDCAT-REPTEXT_DDIC = 'Creation Time'.
LS_FIELDCAT-OUTPUTLEN    = 8.
APPEND LS_FIELDCAT TO GT_FIELDCAT.
CLEAR LS_FIELDCAT.
LS_FIELDCAT-FIELDNAME    = 'STATUS'.
LS_FIELDCAT-REPTEXT_DDIC = 'St'.
LS_FIELDCAT-OUTPUTLEN    = 2.
APPEND LS_FIELDCAT TO GT_FIELDCAT.
CLEAR LS_FIELDCAT.
LS_FIELDCAT-FIELDNAME    = 'ERROR'.
LS_FIELDCAT-REPTEXT_DDIC = 'Message'.
LS_FIELDCAT-OUTPUTLEN    = 70.
APPEND LS_FIELDCAT TO GT_FIELDCAT.
CLEAR LS_FIELDCAT.
LS_FIELDCAT-FIELDNAME    = 'STP_NO'.
LS_FIELDCAT-REPTEXT_DDIC = 'S.T.Party No'.
LS_FIELDCAT-OUTPUTLEN    = 10.
APPEND LS_FIELDCAT TO GT_FIELDCAT.
CLEAR LS_FIELDCAT.
LS_FIELDCAT-FIELDNAME    = 'STP_NAME'.
LS_FIELDCAT-REPTEXT_DDIC = 'Sold to Party Name'.
LS_FIELDCAT-OUTPUTLEN    = 35.
APPEND LS_FIELDCAT TO GT_FIELDCAT.
CLEAR LS_FIELDCAT.
LS_FIELDCAT-FIELDNAME    = 'PO_NO'.
LS_FIELDCAT-REPTEXT_DDIC = 'Purch Order'.
LS_FIELDCAT-OUTPUTLEN    = 15.
APPEND LS_FIELDCAT TO GT_FIELDCAT.
CLEAR LS_FIELDCAT.
LS_FIELDCAT-FIELDNAME    = 'STP_PHONE'.
LS_FIELDCAT-REPTEXT_DDIC = 'S.T.Party Phone'.
LS_FIELDCAT-OUTPUTLEN    = 15.
APPEND LS_FIELDCAT TO GT_FIELDCAT.
ENDFORM.                    "fieldcat_init
*&      Form sort_init
FORM SORT_INIT.
DATA: LS_SORT TYPE SLIS_SORTINFO_ALV.
CLEAR LS_SORT.
LS_SORT-FIELDNAME = 'IDOC_DATE'.
LS_SORT-SPOS      = 1.
LS_SORT-UP        = 'X'.
APPEND LS_SORT TO GT_SORT.
CLEAR LS_SORT.
LS_SORT-FIELDNAME = 'IDOC_TIME'.
LS_SORT-SPOS      = 2.
LS_SORT-UP        = 'X'.
APPEND LS_SORT TO GT_SORT.
CLEAR LS_SORT.
LS_SORT-FIELDNAME = 'STATUS'.
LS_SORT-SPOS      = 3.
LS_SORT-UP        = 'X'.
APPEND LS_SORT TO GT_SORT.
CLEAR LS_SORT.
LS_SORT-FIELDNAME = 'IDOC_NO'.
LS_SORT-SPOS      = 4.
LS_SORT-UP        = 'X'.
APPEND LS_SORT TO GT_SORT.
ENDFORM.                    "sort_init
*&      Form grid_display
FORM GRID_DISPLAY.
CALL FUNCTION 'REUSE_ALV_GRID_DISPLAY'
    EXPORTING
      IS_LAYOUT     = GS_LAYOUT
      IT_FIELDCAT   = GT_FIELDCAT
      IT_SORT       = GT_SORT
      i_callback_program      = SY-REPID
      I_CALLBACK_TOP_OF_PAGE = 'TOP_OF_PAGE'
      I_DEFAULT     = ' '
      I_SAVE        = 'X'
    TABLES
      T_OUTTAB      = T_REPORT
    EXCEPTIONS
      PROGRAM_ERROR = 1
      OTHERS        = 2.
ENDFORM.                    "grid_display
*&      Form COMMENT_BUILD
      Processing of listheader
FORM COMMENT_BUILD USING P_FK_LIST_TOP_OF_PAGE TYPE SLIS_T_LISTHEADER.
DATA: LS_LINE TYPE SLIS_LISTHEADER.
REFRESH P_FK_LIST_TOP_OF_PAGE.
List Heading : Typ H
CLEAR LS_LINE.
LS_LINE-TYP = 'H'.
LS_LINE-INFO = 'Sales Order Interface: Z_EDI_FILE_LOAD'.
APPEND LS_LINE TO P_FK_LIST_TOP_OF_PAGE.
List : Typ S
clear LS_LINE.
LS_LINE-typ = 'S'.
LS_LINE-key = 'Date Range:'.
LS_LINE-info = UDATE-low.
if not UDATE-high is initial.
    write ' To ' to LS_LINE-info+30.
    LS_LINE-info+36 = UDATE-high.
endif.
APPEND LS_LINE TO P_FK_LIST_TOP_OF_PAGE.
ENDFORM.                               " COMMENT_BUILD
      FORM TOP_OF_PAGE                                              *
      Ereigniss TOP_OF_PAGE                                       *
      event     TOP_OF_PAGE
FORM TOP_OF_PAGE.
PERFORM COMMENT_BUILD USING gt_LIST_TOP_OF_PAGE[].
CALL FUNCTION 'REUSE_ALV_COMMENTARY_WRITE'
    EXPORTING
      IT_LIST_COMMENTARY = GT_LIST_TOP_OF_PAGE.
ENDFORM.                    "TOP_OF_PAGE
*&      Form show_status_report
FORM SHOW_STATUS_REPORT .
Report to show status.
DATA: BEGIN OF T_TEDS2 OCCURS 0.
          INCLUDE STRUCTURE TEDS2.
DATA: END OF T_TEDS2.
DATA: BEGIN OF T_IDOC_CONTROL_TMP OCCURS 0.
          INCLUDE STRUCTURE EDIDC.
DATA: END OF T_IDOC_CONTROL_TMP.
CONSTANTS: C_STATUS_IN_IDOC_POSTED       LIKE EDIDC-STATUS VALUE '53'.
DATA : T_EDIDS TYPE STANDARD TABLE OF EDIDS WITH HEADER LINE.
DATA : T_EDIDD TYPE STANDARD TABLE OF EDIDD WITH HEADER LINE.
DATA : GV_PARTNER_SEG TYPE E1EDKA1,
         GV_PO_REF_SEG TYPE E2EDK02.
Get text for status values
SELECT * FROM TEDS2 INTO TABLE T_TEDS2 WHERE LANGUA = SY-LANGU.
Read the IDoc's status after processing
SELECT * FROM EDIDC
    INTO TABLE T_IDOC_CONTROL_TMP
   WHERE UPDDAT IN UDATE
     AND UPDTIM IN UTIME
     AND MESTYP = 'ORDERS'.
LOOP AT T_IDOC_CONTROL_TMP.
IDoc has been processed, since control record changed.
    READ TABLE T_TEDS2 WITH KEY STATUS = T_IDOC_CONTROL_TMP-STATUS.
    T_REPORT-IDOC_NO = T_IDOC_CONTROL_TMP-DOCNUM.
    T_REPORT-IDOC_DATE = T_IDOC_CONTROL_TMP-CREDAT.
    T_REPORT-IDOC_TIME = T_IDOC_CONTROL_TMP-CRETIM.
    T_REPORT-S_TEXT = T_TEDS2-DESCRP.
    IF T_IDOC_CONTROL_TMP-STATUS = C_STATUS_IN_IDOC_POSTED.
    ok status
      T_REPORT-STATUS = 'S'.
    ELSE.
    error status
      T_REPORT-STATUS = 'E'.
    ENDIF.
    Get IDoc details.
    CALL FUNCTION 'IDOC_READ_COMPLETELY'
      EXPORTING
        DOCUMENT_NUMBER         = T_REPORT-IDOC_NO
      TABLES
        INT_EDIDS               = T_EDIDS
        INT_EDIDD               = T_EDIDD
      EXCEPTIONS
        DOCUMENT_NOT_EXIST      = 1
        DOCUMENT_NUMBER_INVALID = 2
        OTHERS                  = 3.
Get Error status
    READ TABLE T_EDIDS WITH KEY STATUS = T_IDOC_CONTROL_TMP-STATUS.
    IF SY-SUBRC EQ 0.
      REPLACE FIRST OCCURRENCE OF '&1' IN T_EDIDS-STATXT
                            WITH T_EDIDS-STAPA1.
      REPLACE FIRST OCCURRENCE OF '&2' IN T_EDIDS-STATXT
                            WITH T_EDIDS-STAPA2.
      REPLACE FIRST OCCURRENCE OF '&3' IN T_EDIDS-STATXT
                            WITH T_EDIDS-STAPA3.
      REPLACE FIRST OCCURRENCE OF '&4' IN T_EDIDS-STATXT
                            WITH T_EDIDS-STAPA4.
      REPLACE FIRST OCCURRENCE OF '&' IN T_EDIDS-STATXT
                            WITH T_EDIDS-STAPA1.
      REPLACE FIRST OCCURRENCE OF '&' IN T_EDIDS-STATXT
                            WITH T_EDIDS-STAPA2.
      REPLACE FIRST OCCURRENCE OF '&' IN T_EDIDS-STATXT
                            WITH T_EDIDS-STAPA3.
      REPLACE FIRST OCCURRENCE OF '&' IN T_EDIDS-STATXT
                            WITH T_EDIDS-STAPA4.
      T_REPORT-ERROR = T_EDIDS-STATXT.
    ENDIF.
    LOOP AT T_EDIDD.
      CASE T_EDIDD-SEGNAM.
        WHEN 'E1EDKA1'.
          GV_PARTNER_SEG = T_EDIDD-SDATA.
          CLEAR : T_REPORT-STP_NAME.
          CALL FUNCTION 'CONVERSION_EXIT_ALPHA_INPUT'
            EXPORTING
              INPUT = GV_PARTNER_SEG-PARTN
            IMPORTING
              OUTPUT = T_REPORT-STP_NO.
          SELECT SINGLE NAME1 TELF1
            INTO (T_REPORT-STP_NAME,T_REPORT-STP_PHONE)
            FROM KNA1
           WHERE KUNNR = T_REPORT-STP_NO.
        WHEN 'E1EDK02'.
          GV_PO_REF_SEG = T_EDIDD-SDATA.
          T_REPORT-PO_NO = GV_PO_REF_SEG-BELNR.
      ENDCASE.
    ENDLOOP.
    APPEND T_REPORT.
ENDLOOP .
SORT T_REPORT BY STATUS IDOC_NO.
Show Report
PERFORM ALV_GRID.
ENDFORM.                    " show_status_report
thanks
karthik
reward me points if usefull.

Co code not seen for cost center master data creation in OKEON

hI:
In org tab of Cost center master data creation while configuring cost center hierarchy in OKEON i can not see organization tab. I have checked in OKKP Co area is assigned to co code but still the issue persist.
Br

hi
you mean the tab is not displayed? strange, it seems that there should be a screen layout to control the ui, or any transaction variant is recorded. I tried in my side, the tab is there.
@ Murali, you are right, but in that tab, not only company code can be configured, but also business area, functional area etc.
best regards, Lawrence

Open field for cost center on the material master

We have a unique requirement in a facility we intend to implement plant maintenance in to track a cost center to a material by including the cost center on the material master somewhere. Cost center is not a field on any of the material tabs we use for maintenance materials, but the requirement is just that it is tracked in a field, even if it's just an open field like a "user defined field" or another field not used often. We realize there are disadvantages such as the field not being checked against active cost centers, but we are looking at options short of adding cost center as a field manually to a tab (which I believe would require ABAP assistance). I don't think there are any other fields/tabs we are currently not utilizing but I could be wrong... The best option we can think of is adding it in a material characteristic so it shows on the classifications tab, but I thought I would see if anyone has any other ideas.
Thanks

Not sure what is the need of cost center on material master when you want to implement Plant maintenance module. Do you have any specific requirement for this?
Ideally cost center will be derived from either functional location/ equipment (equivalent of material master) on to PM work order or notification.
Can you elaborate the requirement?
After all if you wish to go with cost center, then I suggest it should be at plant level as PM requires plant level distribution. You can add up a custom field and give the reference of cost center data element with help of developer.

How to block the creation of a Sales Orders without a linked Purchase Order

Hi. I'm trying to block the creation of a Sales Order that doesn't have a linked Purchase Order. The first thing I did is using the SBO Transaction Notification as follows:
IF @transaction_type = 'A' AND @object_type='17'
BEGIN
     IF (SELECT PoPrss FROM ORDR WHERE DocEntry = @list_of_cols_val_tab_del) = 'N'
     BEGIN
          SET @error = 1
          SET @error_message = 'Purchase Order Missing...'
     END
END
This works good. I create the Sales Order, I tick the purchase order field on the logistics tab, I click Add, and then the purchase order window appears...
Then, the problem begins... If I click the Cancel button, the purchase order is obviously not created, but the Sales Order is created.
Can someone tell me how to block the creation of the sales order If the user press the cancel button on the purchase order window (and the purchase order is not created)
As far as I can see, after clicking the add button in the sales order document, the Sales Order is created on the DB. If there's no way of blocking the creation of the Sales Order, can I avoid closing the purchase order window by the SBO_TransactionNotification? (if the purchase order has not been created)
Thanks...

Hi Yail,
I think you can't close the purchase order with the stored procedure.
Try to catch the Event when the user click on Cancel button.
So you can list the vents with event logger : https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/ede3be37-0e01-0010-1883-cd1b5293473e
You can block the cancel button and force the user to create the purchase order.
Hope i help you
Best regards
Michael

How to get the cost center for the retro balance.

Hi All
I have this report that gives the retro balance. I get the information from RT and BAL. The problem is it doesn't show the Cost Center for the retro amounts. C1 holds the current periods payments not the retro ones.
Does any one know how can i get the Cost Center of the the amounts that wage type /552 is showing in the RT?
Please Help!!!

Hi
I am not sure on the requirement. You are developing a FI report and accessing VA03 which is sales transaction. Anyway for getting cost center you can go to table VBAK,VBAP for line items.
Hope solves ur problem
Thiru

Cost center receiving the real posting even WBS Element are present

Dear All
As per standard SAP documentation, when both cost center and WBS elements are present in the same accounting document, WBS element will take real posting and cost center will take statistical posting.
But in the MIRO document cost center took the real posting even the WBS element is present in the line item of the accounting document.
Regards
Partha Pratim Bhar

Hi
If the WBS element is not statistical, then the real posting should be to the WBS element. However, if you see, when the WBS element becomes a statistical,(when the check mark is added in the control tab) the field cost center becomes active and needs to be input.
In your case since you are deriving the cost center through a substitution rule. Normally if you rules of priority during a document posting, the substitution and validation rules takes a higher priority. So apparently the cost center will get the real posting!! Since the real posting is already made to the cost center, the entry to the WBS element would become a statistical one...
Thats the reason why the situation changes when you deactivate the substitution rule. I am not sure about the entry in the WBS element...My guess is that you would not be able to settle the costs in the WBS Elements.
Hope this clarifies.
Karthik

What is the impact of business area and cost center in the sales document

Hi all
I have small doubt regarding what is the impact of bussiness area and cost center in the sales document... what is the uses of these (bussiness area, cost center) is help full for sd module
can any one reply plz....
Thanking you

Hi,
Business Area determines where the revenue should be allocated when you sell a material or a service.
For eg: If your customer is in say Mumbai and he is ordering for a service in Delhi (say DIAL - Delhi International Airport Limited) then based on the terminology.
Your customer would belong to B Basis Business Area - WHERE THE REVENUE IS COMING FROM or WHERE YOUR CUSTOMER BELONGS TO (SALES OFFICE).
Whereas your DIAL sales will belong to A Basis Business Area - WHERE THE REVENUE IS GOING TO.
Cost Center would determine where your allocate your cost to.
Say Rounding Off can be used as a cost element, because some sort of revenue is lost when figures are roudned off..
Hope it clarifies your doubt.
Reward points if satisfactory
Regards
Ravi.D.Mansharamani

How to change Cost center in the statistical internal Order_Urgent

Hi,
Is it possible to change the Cost Center assigned in Control Tab of internal order. Internal order is a statistical order and posting are already made to that internal order.If it is not possible please let me know what procedure needs to be followed for rectifying same.
Please suggest...
Regards,
Lalatendu

Hi,
When you post next time provide the new cost center with this Internal order. I hope the cost center will change automatically.
If you get any error find the message type through "change message control" option in SPRO you can change from 'ERROR" message to "WARNING".
Regards,
Murali

How to assign default cost center and G/L account in Purchase requisition

Hi,
While creating the purchase requisition ME51N in account assignment we have to enetr cost center name and G/L account but every time we have to enter this how to assign this as defaut value , like cost center : MSMISC and account 42XXXXX.
REGARDS,
ZAFAR

hi
if the field is required then u have to enter them manually
so if this are not required then goto OKB9 here give the default cost center for the Gl acct

FM or BAPI for date and time for the creation of a Purchase Requisition

Hi people:
Does anybody knows about a FM, BAPI or table in which i have de detail for the date and hour of the creation of a Purchase requisition?
Points for helpfull answers.
Thanks in advanced

Hi,
If you want to get the time along with the creation date then use the tables CDHDR and CDPOS, but be careful while passing the data need to pass the entire primary fields data else it will fail in the performance test.
Reward points if useful.
Regards,
Suman

Ecatt: how to test the creation of a purchase requisistion (ME51N)

Hello ecatt-experts,
I have some questions concerning the creation of a purchase requisition with ecatt:
- is it possible to use TCD recording instead of sapgui recording for ME51N ?
(as far as I've seen it's not possible with TCD as I didn't get back the field-values)
- Is it possible to record the creation of a PR with 1 item and to write a script which can be used for the creation of a PR with n items ?
For this I would need to cread GUIElement- Parameters dynamically.
Or is the only solution to this problem to register a sapgui with n items and to define n parameters ?
regards,
monika

HI Monika,
It is difficult to use TCD for creating a Purchase Requisition (I am not telling you that it is impossible, you can do it, but its really hard to manipulate screen elements and to pass values to them).
One thumb rule is to use SAPGUI for all Enjoy transactions(ME21N, ME51N, MIGO....)
Answer to your second question is YES. You can use the single recording for N number of items without creating multiple parameters.
You have to create a parameter with the parameter reference as the table/structure mentioned in the transaction grid(Press F1 on the TA screen and then go to technical help and copy the table/structure name and paste it in the parameter reference area of the eCATT parameter ending with [] like <b><I_MARA> <Description> <MARA[]></b> ).
Then create another local parameter of type numeric(may be V_COUNT )
In the eCATT, use a GETLENGTH (I_MARA, V_COUNT).
Then loop the grid values like
DO (V_COUNT).
SAPGUI RECORDING <b>ONLY</b> FOR THE ITEMS..
Here map the values with the values of the St. Parameter
like I_MARA[&LPC]-MATNR.
ENDDO.
This way, you can pass multiple values to the grid to the parameter I_MARA in the runtime and also use a single line recording for passing multiple values.
This thread might help you in a way.
Re: Secatt doubt
Hope the solution helps.
Best regards,
Harsha
PS: Reward points accordingly for all responding.

Creation of a purchase order triggers the event ReleaseStepCreated twice

Hello,
I tried to use the standard workflow for the approval of a purchase order and noticed that i am receiving twice the same mail.
As you know, the workflow is triggered by the event ReleaseStepCreated. After I created a purchase order, i saw that the event is triggered twice, so that is why i am receiving two emails.
I believe this is wrong, Has anyone noticed this problem?
Thanks,
Efren

Hello,
The event linkage contains only one record, which is the one that connects my workflow to the event. This is not the cause.
What do you mean by delegations? Are you talking about delegated objects? If yes, i do not have any.
I looked in transaction SWEC(events for changed documents), and i guess i found the cause. There is a record with change doc. object EINKBELEG with the event ReleaseStepCreated of the object BUS2012. It has the trigger event "On Create", and in the Function Module, in Event Container it has function FRE_ORD_EVENT_PO_DB.
I removed this record and now the event RELEASESTEPCREATED is triggered only once, so i think it is ok.
I guess this record existed before there. Do you have that record with the function module FRE_ORD_EVENT_PO_DB?Or do you know what is the use of this function?

Standalone Scenario - Error during Creation of Local Purchase Order

Hi All,
I am trying to setup Standalone Scenario, i have created all the master data locally, i am able to Order SC, but after workflow approval SC goes into error 'Error during creation of local purchase order from shopping cart XXXXXXXXX'
I have created following configuration setting for local PO number
1) In SPRO -> Cross-Application Basic Settings -> Number Ranges -> Define Number rang. for Schopping Carts and Follow-on Doc. --- i have number ranges for PO follow-on doc. i.e.
inrerval No = PO, from number = 0004000000, to number = 0004999999, ext. = unchecked
2) In SPRO -> Cross-Application Basic Settings -> Number Ranges -> Define Ranges per backend system for follow-on documents PO, PR etc
3) In sourcing (SPRO -> Cross-Application Basic Settings -> Sourcing -> Define Interactive Sourcing for product categories) --- sourcing is never carried out.
Can anybody help?
Regards,
SAP Guy.
Edited by: SAP Guy on Apr 23, 2008 2:32 AM

Hi SAP Guy,
Following steps are must for Local number range
1) Create number range for local PO
2) Maintain your logical system in 'Define number range per backend system for follow on document'
3) Define Transaction Type for BUS2201, define document type (e.g. EC1)
4) Assign Document type (EC1) in Org attribute BSA.
Hope this helps.
Regards,
Manish.

Blocking of a cost center in the creation of a Purchase Order

Similar Messages

Maybe you are looking for