Change of "Revenue posting" after the creation of an order

Hi all,
I would like to change the tick "Revenue posting" on the internal order level. There was a mistake in the setting while creating internal order type (I forgot to say "Revenue postings allowed" on the internal order type level). Since then many internal orders have been created and changing of this status on internal order type level does not help anymore for the created internal orders.
The SAP help says: You set the indicator in the order type. It is copied from the order type when you create new orders. Order that already exist are not changed when you set this indicator at a later date in the order type.
Do you have any experience with this? What did you do?
Thank you for any advice.
Vaclav Nemec

Hello Vaclav!
Please see SAP-note #332693 which should help resolve Your problem.
Best regards
Florian

Similar Messages

Gr is not posted after the conformation of Production order take place

Hi Gurus
I have created production order and conformation take placed but goods movement (GR) is not get posted. Stock quantity shows zero.
1.      I have set 'auto goods reciept' indicator in Control Key .
2.      Opl8 transaction for GR for production order.the indicator is active.
3.      I have set 'auto goods reciept' indicator in production scheduling profile
Pl give the solution
Narasingam

Hi Rohit
I have checked in COGI . i got message lile "cost element 875000 is not maintained at 30.07.2009 for controlling area T010"
Then i have created cost element .
I have already given storage location for FG material
I have checked the routing with Auto GR control key.
I have assigned only one operations in routing
But
I can able to post GR using mb31
Document 11058 posted
Regards
Narasingam

Account of the opportunity is not populated after the creation of a task

Hi,
In our project, we are using the Opportunity Object after the creation of a task. Our tasks are always related to an existing account.
I was wondering why when I create an opportunity from a task, the field "Account Name" is not populated by default with the account name related to the task.
Any ideas?
Regards,
Dara
Edited by: user6469826 on 2 août 2011 11:40

Contact an electronics repair shop.

[svn:osmf:] 15527: Fix bug FM-696: Capability change events being dispatched after the trait to which they refer has been modified .

Revision: 15527
Revision: 15527
Author:   [email protected]
Date:     2010-04-16 17:21:06 -0700 (Fri, 16 Apr 2010)
Log Message:
Fix bug FM-696: Capability change events being dispatched after the trait to which they refer has been modified. Updated unit tests.
Ticket Links:
    http://bugs.adobe.com/jira/browse/FM-696
Modified Paths:
    osmf/trunk/framework/OSMF/org/osmf/media/MediaPlayer.as
    osmf/trunk/framework/OSMFTest/org/osmf/media/TestMediaPlayer.as

Major Update: The G-Keys can now be edited without recompiling by editing shell scripts at "/usr/share/g15daemon/macros/"
Each button has it's own script file named by it's label (e.g. to edit the functionality of G1, open the script named G1.) The button will try to execute the scripts as programs, so make sure they are executable (chmod +x) and as long as the name remains the same, if you want to replace the files with something different, know that the arguments currently given to the files ($1 and $2) are ($1)on/off and ($2)0-2 (where 0 is M1 and 2 is M3)
To download the updated sources, go here (only the g15daemon source/patch was updated). This thread's OP has been updated.
Last edited by rabcor (2015-02-12 04:46:48)

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

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

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

Block the creation of planned order

Dear experts
How can I control the creation of planned order? I want to block the creation of planned order if the BOM or routing is not exist.
BRs

Hi,
I think this can be done using 'Material status' try the following and let me know if it works.
Create a new material status in transaction OMS4 (like R1 - "Created but BOM and Routing not maintained" )and in the details screen select Option "B" for MRP messages.
You designate a material as a "R1 -Created but BOM and Routing not maintained" In the master record.
MRP "B" = warning
Please try this and let me know the result.
Regards,
Prakash

How to switch on/off the creation of internal order at item level

Dear experts,
When create service order in CRM, is there any way to control the creation of internal order at item level?
For certain item category, the cost should be distributed to R/3 Back End system, but for others it should never be transferred.
Please advise, thanks in advance.

Hi Yukun,
We are also struggling with the same problem.
did you find any correct solution to the problem by now.
However one setting in backend r/3 is that of controlling scenario-- just check whether the controlilng scenario is set with the level 'transaction'
i guess if you set it to transcation and at the next level you create for a particular transaction type you need to create a controlling scenario then i guess the problem will be solved.. we tried tthe same settings however we are unable to find the result to the problem.
if you find something important do write back...
hope that your problem is solved...
and ours also...
surendra

Baseline date change after the creation of invoice list

When I create invoice document, the invoice date (vbrk-fkdat) is the end of the month and the invoice list date (VBRK-FKDAT_RL) is the next business day after the invoice date, the baseline date of the accounting document (bseg-zfbdt) is the document creation date and this is what I wanted.
However, when I start to create the invoice list, the baseline date on the accounting document (field bseg-ZFBDT) is changed to the invoice list date. Does anyone know why and how to fix and where to look in the configuration to see how invoice list date (vbrk-fkdat_rl) is populated? It seems to me that the baseline date default back to the invoice list date when invoice list document is created. Thanks for your help. I also posted this question in the ERP Financial thread.

Hi Valerie,
do you recall the User Exit?
Thanks

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.

Not allowing changes to payment terms after the AR document is released to accounting

Hi,
Anyone know the best way to not allow a user to change the payment terms after the AR document has been created in AR? This is affecting aging because users are changing the payment terms without permission. What is the best way to control that?
Thank you.
AK

Hi A K
Frequent change in payment terms is something business should introspect. Payment term is decided and agreed upon with customer/vendor during the initial stages.
However from IT perspective, it can be controlled keeping some system controls.
1. Limit the Customer master change transaction to very limited users or to a manager. There should be internal approvals by management for business to make a change. Bring this into force.
2. Regularly run the customer master change reports and provide the trend to management to restrict or limit the changes.
3. Use Change Message control for master data by providing necessary warnings or error messages when master data is changed.
4. In the sales order level, there is every possibility to change the payment term. Based on the user authorization get the payment term field greyed out and provide change access to accounting or to a specific user upon approvals. This is a bit complex process but I feel this brings up controls and stops the process from exploitation.
5. Also activate 'Sensitive fields' KNB1-ZTERM for payment term field in customer master. This brings up another layer of confirmation of change by other users.
6. Another back route, not recommended in all cases, is to subsititute the required payment term during accounting document posting.
Hope it helps.
Thanks,
Sekhar

Change documents in WTY after the Claim is "complete"

Dear All,
In WTY transaction, I am unable to view the change documents (Extras --> Change Documents) after the Claim is flagged off as "Complete"
Is there a way to overcome this ?
Thanks.
Raj

Thanks Vijayesh.
The problem is resolved by introducing Action T210 (Change Documents Claim) in the standard Action control matrix after status B060.
Regards,
Raj

Imessage changed my phone number after the ios7 update

after the ios7 update imessaging has changed my number to some weird 7 digit number with a +1 (1) infront of it. if someone txts my actual phone number the message wont deliver.. i have reset everything on the phone multiple times and have did alot of troubleshooting for this and nothing seems to work. i went to the apple store and they said to call the techs.. i did that before i even went to the store and they couldnt do anything for me. if anybody has any ideas on how to fix this please help! thank you

Hi mdfrommo,
You can't change it back by going to Settings>Phone, and then by clicking on your number at the top? It should take you to a screen that will allow you to delete what is there and type your own number in.
Cheers,
GB

Change RPM Item Type after Item creation

There is a requirement where RPM Item Type needs to be changed for an Item after it is created.
Using the Override in SPRO we can enable field for change. But it does not really change all Decision points etc. I think it would not happen since ITem type drives everything once the item is created.
Please correct me if I am wrong.
Also, any other alternatives for this requirement besides starting all over again to create the Item?
Thanks!

Hi,
1 - Map the permitted item types in the path: SAP Portfolio and Project Management > Portfolio Management > Global Customizing > Portfolio-Independent Settings > Define Portfolio Item Types
Select an item type, a decision point and then set the permitted item types for switch to.
2 - Make settings for process flow in the path: SAP Portfolio and Project Management > Portfolio Management > Global Customizing > Portfolio-Independent Settings > Process Flow for Items > Make Settings for the status mapping for itens
3 - In the portfolio item click in the "Change Process" yellow button.
3.1 Chosse the item type
3.2 Select "Delete previous decision points"
3.3 Save
Best regards,
Jonatan

Problem regarding the creation of sales order using bapi.

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

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

Changing DNS zone names after the fact

Over 3 months ago we started setting up our server network. After discussions with administration it was determined (at the time) that we would use and register a domain name with a .net extension. So we set up a primary server with this extension and had it registered with our ISP. We subsequently added 7 other servers to the mix and as they were installed they grabbed their names from the DNS zone we had setup *.net in our DNS zone in our primary nameserver system. It was all well the tests worked we had it all going and are moving our 130 machines (including about 60 users) over next few months (and have moved about 10 users and other machines so far.
My question is this. Back in beginning a *.org was the other option but we had problems with it and our ISP (could have been some error on our part) so we went with *.net for our domain and got that registered. Now all of a sudden as our management is wanting to move the organizational website (we are not doing that) to another service that service is tying to convince them we should have not used *.net but *.org.
The person in charge of us is strongly asking if we can go back and setup with *.org but as I understand it I cannot go in and delete my *.net DNS zone and then rename all the servers with a .org extension but as we understand it from lynda.com and other sources it appears that we probably would have to go back and reset all the machines back up by reinstalling them after I changed the first primary nameserver. And then register the new name and wait for it to propagate?
Are we wrong? Can we just go in and turn off the DNS in server admin and then change the zone name(s) to *.org and the host names of each server from *.net to *.org and restart DNS and find all to be well? As much as we can tell it appears that we would have to restart from scratch as all the documents and lynda.com imply we should have had our final domain name set and registered before we started to install and setup the primary and secondary servers?
I see some examples where it is said to make such changes something needs to be done with ipconfig and not the GUI in server admin. But again I am not sure that this will work with our primary nameserver and the 7 servers under it?
Any feedback or help about this would be appreciated. It is our preference to stay with *.net and not have to do major work as we are starting user and network migration to the new servers and hate to have have such a major setback just because one person and the web design service they want to use does not like *.net. to us it appears the horse is long out of the barn and when this was approved last fall we have gone to far to easily go back. But if it is easier to go back than we think then we are willing to try to change.
Thanks
russ

foilpan wrote:
first, what are these servers doing? are they all web servers, OD masters, simple file servers? depending on their roles, changing their names can be more or less of a problem.
The first server we set (the name server) does incoming mail, is the DNS server for local net and such. Then there is the outgoing mail server (one of 7) a web server (another of 7) and then the rest are mostly file servers for our setup.
second, work out that political stuff before making any changes. if everything's working fine as is, make a strong case for leaving things alone. if possible, estimate support costs for changing everything and troubleshooting, then see if management can justify it.
Sort of my feeling. We thought we had it all worked out but then they decided to abandon the old web site (managed by someone else but associated with the old mail/network somewhat) and have a new Web design company do it and this company complained about us having chose a .net for what reason I do not know so the administrator somehow was persuaded and had no idea of the can of worms she had opened up by changing her mind. If it is too much of a hassle and it appears so in terms of delays to move rest of organization over then I hope we can convince them.
are all these servers public facing or behind a firewall?
They are behind a firewall on a high speed cable modem ISP service (firewall is local ASTARO machine).
also, why not setup another dns zone for .org and point to the same hosts? that would allow you to use either .net or .org, for the most part. again, that depends on what these servers are doing.
We suggested that but the administrator did not like having two names we have a lot of users (volunteers and such) who are not really too savvy (the nature of free and partime help I guess) and she feels they will be confused by two extensions for network, mail and web. It sure does not bother me (I have about 8 email addresses for example now .
post more details without the political background and what the end result should be, and we'll be able to add more here.
Ok basically we want to know with the following:
1) main nameserver (the first server that provides the DNS zone for local *.net and serves the incoming mail)
2) A second outgoing SMTP server to split load and do outgoing work...
3) A third webserver doing all the web services (blog, wicki, and such)
4) 4 file servers that are going to provide a local file server for our 4 main departments
5) A final test server we are testing other things with-- so total of 8 servers.
6) 8 Users out of 60 now on the network with their personal desktops or laptop machines, and a few printers and other devices all on new network.
There are a total of 130 macs and pc's in our organization that will all eventually be on this new network with the above.
Basically we are wondering if the main (first) DNS and incoming mail sever, and the 7 other (web, SMTP out, and file server machines) will have to be set back up from reinstall if we are to make the change from the *.net zone we have now to a *.org one?
Any other details that would be of help?
Thanks
Russ
2) second

Change of "Revenue posting" after the creation of an order

Similar Messages

Maybe you are looking for