Update process for September NIC update?

The install help file says to create a boot disc from the included iso file and boot the server(s) to be updated. Is it really this easy to update the NIC drivers? We're running Zenworks 10.3.3.

Originally Posted by spond
Elphantasmo,
huh? I write those instructions, and I don't remember saying that...
Shaun Pond
Never mind... the pdf was corrupted; it only showed the first two or three pages. I re-downloaded it after your confused post and because I'm on a different computer. So, thanks for looking at me like you know something I don't.

Similar Messages

  • Creating process for multiple Date fields for update or insert in APEX

    hello there,
    could someone please help me?
    i have a form on Apex based on view that is based on three tables and updating and inserting ok using trigger instead of.
    i have a problem now as in my form i have around 75 fileds (items) incuding 30 or more date fields which could be populated or left blank or update later.
    so for each date field i have two boxs; one for date, input as dd/mm/yyyy (text field) and second for time, input as 23:45. All dates will be insert or update manually by user. so as i mentioned not all date fields could be poulated at one stage.
    so i have created some process and validations and all of them work fine but i came accross if date left blank then (:) giving me problem so i have done following further process for each date field. In real table all the date fields have data type date.
    declare
    v_my_var date; -- for first date field
    str_dy VARCHAR2(10);
    dt_indx date;
    str_tm VARCHAR2(20);
    tm_indx date;
    begin
    str_dy := :p4_first_date
    str_tm := str_dy||' '||substr(:p8_first_date_hh,1,2)||':'||substr(:p8_first_date_HH,4,2);
    dt_indx := to_date(str_tm,'DD/MM/YYYY HH24:MI');
    IF str_dy is not null then
    v_my_var :=dt_indx;
    ELSE
    v_my_var := NULL;
    END IF;
    update table 1 set my_date = v_my_var where d_id= :p4_d_id;
    end;
    above code work fine but one date field of course therefore i have to do same code for each date field with changes and initialise variable again and again for each field.
    so i like to ask is there any easy way that is more professional. i was thinking about the procedure and using collection or similar but honestly not much experience on that so could some one please help me?
    I will be very thankful.
    KRgds

    Hi,
    You can do the needful by re-using the code if you can give the item names as P8_DATE1, P8_DATE_hh1, P8_DATE2, P8_DATEhh2 etc..So your item name just differs by a sequence.
    Now you write function which will return desired date value taking above items as input. Pass item names to this function, get session state using APEX_UTIL.GET_SESSION_STATE('item_name') API.
    Now modify you code as
    FOR i IN 1..30
    LOOP
    v_date_array[i] = f_get_date('P8_DATE'||i, 'P8_DATEhh'||i);
    END LOOP;
    ....Now you have all date valus in array. Just write one update as follows
    UPDATE  TABLE1
    SET date1 = my_date_array[1], date2 = my_date_array[2]..
    WHERE ....Hope it helps :)
    Cheers,
    Hari

  • Order management header level updation process for iStore order.

    Hi all,
    I worked on OM header level updation process for iStore order.only card holder name,expiration date updated using OE_ORDER_PUB.process_order but Credit card number,card type not updated for istore order in OM.so please help to me.
    CODE:
    SET SERVEROUTPUT ON;
    DECLARE
    v_api_version_number NUMBER := 1;
    v_return_status VARCHAR2 (2000);
    v_msg_count NUMBER;
    v_msg_data VARCHAR2 (2000);
    -- IN Variables --
    v_header_rec oe_order_pub.header_rec_type;
    v_line_tbl oe_order_pub.line_tbl_type;
    v_action_request_tbl oe_order_pub.request_tbl_type;
    v_line_adj_tbl oe_order_pub.line_adj_tbl_type;
    -- OUT Variables --
    v_header_rec_out oe_order_pub.header_rec_type;
    v_header_val_rec_out oe_order_pub.header_val_rec_type;
    v_header_adj_tbl_out oe_order_pub.header_adj_tbl_type;
    v_header_adj_val_tbl_out oe_order_pub.header_adj_val_tbl_type;
    v_header_price_att_tbl_out oe_order_pub.header_price_att_tbl_type;
    v_header_adj_att_tbl_out oe_order_pub.header_adj_att_tbl_type;
    v_header_adj_assoc_tbl_out oe_order_pub.header_adj_assoc_tbl_type;
    v_header_scredit_tbl_out oe_order_pub.header_scredit_tbl_type;
    v_header_scredit_val_tbl_out oe_order_pub.header_scredit_val_tbl_type;
    v_line_tbl_out oe_order_pub.line_tbl_type;
    v_line_val_tbl_out oe_order_pub.line_val_tbl_type;
    v_line_adj_tbl_out oe_order_pub.line_adj_tbl_type;
    v_line_adj_val_tbl_out oe_order_pub.line_adj_val_tbl_type;
    v_line_price_att_tbl_out oe_order_pub.line_price_att_tbl_type;
    v_line_adj_att_tbl_out oe_order_pub.line_adj_att_tbl_type;
    v_line_adj_assoc_tbl_out oe_order_pub.line_adj_assoc_tbl_type;
    v_line_scredit_tbl_out oe_order_pub.line_scredit_tbl_type;
    v_line_scredit_val_tbl_out oe_order_pub.line_scredit_val_tbl_type;
    v_lot_serial_tbl_out oe_order_pub.lot_serial_tbl_type;
    v_lot_serial_val_tbl_out oe_order_pub.lot_serial_val_tbl_type;
    v_action_request_tbl_out oe_order_pub.request_tbl_type;
    v_msg_index NUMBER;
    v_data VARCHAR2 (2000);
    v_loop_count NUMBER;
    v_debug_file VARCHAR2 (200);
    b_return_status VARCHAR2 (200);
    b_msg_count NUMBER;
    b_msg_data VARCHAR2 (2000);
    BEGIN
    DBMS_OUTPUT.PUT_LINE('Starting of script');
    -- Setting the Enviroment --
    mo_global.init('ONT');
    fnd_global.apps_initialize ( user_id => 1013438
    ,resp_id => 21623
    ,resp_appl_id => 660);
    mo_global.set_policy_context('S',204);
    -- Header Record --
    v_header_rec := oe_order_pub.g_miss_header_rec;
    v_header_rec.request_date := SYSDATE;
    v_header_rec.header_id := 251413;
    v_header_rec.credit_card_holder_name :='esakki';
    v_header_rec.credit_card_number := 'XXXXXXXXXXXX3510';
    v_header_rec.credit_card_expiration_date := to_date('01-JAN-2014','dd-mon-yyyy');
    v_header_rec.credit_card_code := 'MASTERCARD';
    v_header_rec.payment_type_code := 'CREDIT_CARD';
    v_header_rec.sold_to_org_id := 131747;
    v_header_rec.sold_from_org_id := 204;
    v_header_rec.ordered_date := SYSDATE;
    v_header_rec.operation := OE_GLOBALS.G_OPR_UPDATE;
    v_action_request_tbl (1) := oe_order_pub.g_miss_request_rec;
    -- Line Record --
    v_line_tbl (1) := oe_order_pub.g_miss_line_rec;
    DBMS_OUTPUT.PUT_LINE('Starting of API');
    -- Calling the API to update the header details of an existing Order --
    OE_ORDER_PUB.PROCESS_ORDER (
    p_org_id =>204
    ,p_operating_unit => NULL
    p_api_version_number => v_api_version_number
    ,p_init_msg_list => fnd_api.g_false
    ,p_return_values => fnd_api.g_false
    ,p_action_commit => fnd_api.g_false
    , p_header_rec => v_header_rec
    , p_line_tbl => v_line_tbl
    , p_action_request_tbl => v_action_request_tbl
    , p_line_adj_tbl => v_line_adj_tbl
    -- OUT variables
    , x_header_rec => v_header_rec_out
    , x_header_val_rec => v_header_val_rec_out
    , x_header_adj_tbl => v_header_adj_tbl_out
    , x_header_adj_val_tbl => v_header_adj_val_tbl_out
    , x_header_price_att_tbl => v_header_price_att_tbl_out
    , x_header_adj_att_tbl => v_header_adj_att_tbl_out
    , x_header_adj_assoc_tbl => v_header_adj_assoc_tbl_out
    , x_header_scredit_tbl => v_header_scredit_tbl_out
    , x_header_scredit_val_tbl => v_header_scredit_val_tbl_out
    , x_line_tbl => v_line_tbl_out
    , x_line_val_tbl => v_line_val_tbl_out
    , x_line_adj_tbl => v_line_adj_tbl_out
    , x_line_adj_val_tbl => v_line_adj_val_tbl_out
    , x_line_price_att_tbl => v_line_price_att_tbl_out
    , x_line_adj_att_tbl => v_line_adj_att_tbl_out
    , x_line_adj_assoc_tbl => v_line_adj_assoc_tbl_out
    , x_line_scredit_tbl => v_line_scredit_tbl_out
    , x_line_scredit_val_tbl => v_line_scredit_val_tbl_out
    , x_lot_serial_tbl => v_lot_serial_tbl_out
    , x_lot_serial_val_tbl => v_lot_serial_val_tbl_out
    , x_action_request_tbl => v_action_request_tbl_out
    , x_return_status => v_return_status
    , x_msg_count => v_msg_count
    , x_msg_data => v_msg_data
    DBMS_OUTPUT.PUT_LINE('Completion of API');
    IF v_return_status = fnd_api.g_ret_sts_success THEN
    COMMIT;
    DBMS_OUTPUT.put_line ('Order Header Updation Success : '||v_header_rec_out.header_id);
    ELSE
    DBMS_OUTPUT.put_line ('Order Header Updation failed:'||v_msg_data);
    ROLLBACK;
    FOR i IN 1 .. v_msg_count
    LOOP
    v_msg_data := oe_msg_pub.get( p_msg_index => i, p_encoded => 'F');
    dbms_output.put_line( i|| ') '|| v_msg_data);
    END LOOP;
    END IF;
    END;
    OUTPUT:
    Starting of script
    Starting of API
    Completion of API
    Order Header Updation Success : 251413
    Thanks,
    saran

    Forgot to mention :Soruce is Oracle EBS

  • Hi I update my I Phone 3 GS for IOS 6.1. but he asking activate Iphone after we process for activation he shown error. please do the needfull

    hi I update my I Phone 3 GS for IOS 6.1. but he asking activate Iphone after we process for activation he shown error. please do the needfull

    Try to restart or - if necessary - to restore the iPhone: 
    See this document:  iPhone: Troubleshooting activation issues
    Disable your Firewall and Antivirus software - it may be blocking the access to the server. Wait a day, maybe the server is down.
    If your iPhone cannot be activated, because it has been modified, we cannot help, see:  http://support.apple.com/kb/HT3743

  • Change control process for updating the UPK topics

    Is anyone using a change control process for updating the UPK topics for JD Edwards EnterpriseOne?
    With publishing the whole module and everything linked, I am finding it difficult if a developer is updating a topic and maybe in the middle of it, but has it checked in to the server?
    I would like to hear what others may be doing to control this.
    Thank you,
    Linda Paar
    MOM Brands

    Hello,
    If you have not already joined the UPK community in My Oracle Support, I would recommend you ask your question in that forum as there is a lot of experience there. Additional information can be found in the announcement at the top of this forum: https://forums.oracle.com/forums/ann.jspa?annID=1175
    Best regards,
    Marc

  • OCM process for material revision update

    Hi
    Does anyone knows OCM process for material revision update?
    from what i saw OCM is not working for ECM which has only revision update.
    Is there any work around to update the production order?
    Thanks.

    Hi
    Read PP master data indeed update the revision, but i need to do the update in a mass process, and not for each order separably
    in addition there are some other advantages to OCM, like the ability to change even if suborder (of collective order) is already confirmed, which can't be done with read master data.

  • What is the process for SQL Server 2005 patch update

    hi,
    i have 2 production SQL Server2005  Database servers in cluster ,
    what is the process for applying patches.
    Saidireddy

    In 2005 you can do it in two ways...
    Method 1 :
    With SQL Server 2005,
    when you start installing cluster service pack (or hotfix), it must be launched on the active node(node
    that hosts the instance). When installing the Setup will launch simultaneously  "remote silence" on all passive nodes. All nodes in the cluster containing the SQL Server instance are updated in the same time.
    Method 2: First you can install in passive node then you can install in the active node, In this way you can save your down time ( If you start in the active node it will check in the passive, and if its installed already then it skips that
    and start applying in the active node ), but most of the DBA's follows only first method because they may not aware of this or just they follows Microsoft common method. 
    SQL 2008 and Later....
    1.  Apply the hotfix on pasive node N2
    2.  Reboot the passive node N2
    3.  Failover on SQL resource : the passive node become the active node
    4.  Apply the hotfix on the passive node N1
    5.  Reboot the passive node N1
    Raju Rasagounder Sr MSSQL DBA

  • Microsoft and Adobe Updates for September

    Microsoft
    Critical Updates
    MS13-067 Vulnerabilities in Microsoft SharePoint Server Could Allow Remote Code Execution (2834052) 
    MS13-068 Vulnerability in Microsoft Outlook Could Allow Remote Code Execution (2756473)
    MS13-069 Cumulative Security Update for Internet Explorer (2870699)
    MS13-070 Vulnerability in OLE Could Allow Remote Code Execution (2876217)
    Important Updates
    MS13-071 Vulnerability in Windows Theme File Could Allow Remote Code Execution (2864063)
    MS13-072 Vulnerabilities in Microsoft Office Could Allow Remote Code Execution (2845537)
    MS13-073 Vulnerabilities in Microsoft Excel Could Allow Remote Code Execution (2858300)
    MS13-074 Vulnerabilities in Microsoft Access Could Allow Remote Code Execution (2848637)
    MS13-075 Vulnerability in Microsoft Office IME (Chinese) Could Allow Elevation of Privilege (2878687)
    MS13-076 Vulnerabilities in Kernel-Mode Drivers Could Allow Elevation of Privilege (2876315)
    MS13-077 Vulnerability in Windows Service Control Manager Could Allow Elevation of Privilege (2872339)
    MS13-078 Vulnerability in FrontPage Could Allow Information Disclosure (2825621)
    MS13-079 Vulnerability in Active Directory Could Allow Denial of Service (2853587)
    Windows Malicious Software Removal Tool (MSRT) for September, version 5.4
    http://www.microsoft.com/en-us/download/malicious-​software-removal-tool-details.aspx 
    Note:The number of updates may vary depending on the operating system and last minute changes by Microsoft.
    ==========================================
    Adobe Products
    1. Sequential Patch for Adobe Reader for Windows (for those who have version 11.0.x installed) update to version 11.0.4
    http://www.adobe.com/support/downloads/detail.jsp?​ftpID=5637
    For more details, see http://www.adobe.com/support/security/bulletins/ap​sb13-22.html
    2. Adobe Flash Player 11.8.800.168
    Downloads for Windows 7 and earlier
    Users of IE10 on Win8 will receive their Flash update via Microsoft
    Internet Explorer - http://download.macromedia.com/get/flashplayer/cur​rent/licensing/win/install_flash_player_11_active_​...
    Plugin-based browsers (Firefox etc) - http://download.macromedia.com/get/flashplayer/cur​rent/licensing/win/install_flash_player_11_plugin.​...
    Uninstaller (if needed) : http://download.macromedia.com/get/flashplayer/cur​rent/support/uninstall_flash_player.exe 
     For more details, see http://www.adobe.com/support/security/bulletins/ap​sb13-21.html
    3. Adobe AIR 3.8.0.1430  http://get.adobe.com/air/ 
    4. Adobe Shockwave 12.0.4.144 http://get.adobe.com/shockwave/ 
    This update addresses vulnerabilities that could allow an attacker, who successfully exploits these vulnerabilities, to run malicious code on the affected system. 
    For more information, see http://www.adobe.com/support/security/bulletins/ap​sb13-23.html
    ThinkPad: T530 / X1 Gen 2 / Helix - Yoga: Tablet 2 Pro (Win) / Yoga 3 Pro
    If you find a post helpful and it answers your question, please click the "Accept As Solution" button.
    Lenovo Advocate ~ I am not employed by Lenovo or Microsoft. I am a volunteer.
    Microsoft MVP - Consumer Security
    SpywareHammer

    Adobe Flash Player 11.8.800.175
    So far this is for Internet Explorer. There is no update for plugin version for other browsers yet.
     Download for Windows 7 and earlier:
    http://download.macromedia.com/get/flashplayer/curr​ent/licensing/win/install_flash_player_11_active_x​...
    ThinkPad: T530 / X1 Gen 2 / Helix - Yoga: Tablet 2 Pro (Win) / Yoga 3 Pro
    If you find a post helpful and it answers your question, please click the "Accept As Solution" button.
    Lenovo Advocate ~ I am not employed by Lenovo or Microsoft. I am a volunteer.
    Microsoft MVP - Consumer Security
    SpywareHammer

  • Regarding Goods Reversal and Goods Issue process for Production orders

    Hi,
    I have a issue regarding <b>Goods Reversal</b> and <b>Goods Issue</b> process for <b>Production orders</b>.
    Actually I am having a Z - Function Module in that i am passing <b>production order number other details</b> to
    make the <b>Goods Reversal</b> happen.
    The code for the above is as below:
                       i_mvtit-material      = wa_mdfa-matnr.
                        i_mvtit-plant         = i_resb-werks.
                        i_mvtit-spec_stock    = 'Q'.          "New
                        i_mvtit-stge_loc      = 'ZWIP'.
                        i_mvtit-stge_type     = i_resb-lgtyp. "New
                        i_mvtit-batch         = i_resb-charg. "New
                        i_mvtit-orderid       = i_resb-aufnr.
                        i_mvtit-spec_stock    = i_resb-sobkz.
                        i_mvtit-entry_qnt     = i_resb-enmng.
                        i_mvtit-entry_uom     = i_resb-erfme.
                        i_mvtit-entry_uom_iso = i_resb-meins. "New
                        i_mvtit-wbs_elem      = v_frwbs.
                        i_mvtit-move_type     = '262'.
                        i_mvtit-xstob         = 'X'.
                        i_mvtit-gr_rcpt       = i_resb-aufnr. "New
                        i_mvtit-reserv_no     = i_resb-rsnum.
                        i_mvtit-res_item      = i_resb-rspos.
                        APPEND i_mvtit.
    * HEADER ELEMENTS
                        k_gmvt_code-gm_code    = '03'.
                        k_gmvt_head-pstng_date = sy-datum.
                        k_gmvt_head-doc_date   = sy-datum.
    * CREATE GOODS MOVEMENTS
                        CALL FUNCTION 'BAPI_GOODSMVT_CREATE'
                          EXPORTING
                            goodsmvt_header = k_gmvt_head
                            goodsmvt_code   = k_gmvt_code
                          TABLES
                            goodsmvt_item   = i_mvtit
                            return          = i_return.
    The Above code does the <b>Goods Reversal</b> but then i will update one Z Table with fields like
    Production Order Number[AUFNR], Number of Reservation[RSNUM], Item Number of Reservation [RSPOS], Material Number [MATNR], Requirement Quantity [BDMNG], WBS element[PSPNR] etc. If Above BAPI runs sucessfully.
    That is happening correctly.
    But Then actual issue is i have do <b>Goods Issue</b> for those Z-Table records.
    There i will give Production order Number's & Storage Location in Selection-Criteria.
    Then i need to do <b>Goods Issue</b> for that order.
    The code i had written as follows.
    * POPULATE VALUES FOR BAPI CALL
            i_mvtit-material      = i_zpsi7603_01-matnr.
            i_mvtit-plant         = i_resb-werks.
            i_mvtit-spec_stock    = 'Q'.                "New
            i_mvtit-stge_loc      = p_sloc.
            i_mvtit-stge_type     = i_resb-lgtyp.       "New
            i_mvtit-batch         = i_resb-charg.
            i_mvtit-orderid       = i_resb-aufnr.
            i_mvtit-spec_stock    = i_resb-sobkz.
            i_mvtit-entry_qnt     = i_resb-enmng.
            i_mvtit-entry_uom     = i_resb-erfme.
            i_mvtit-entry_uom_iso = i_resb-meins.       "New
            i_mvtit-wbs_elem      = v_frwbs.
            i_mvtit-move_type     = c_261.
            i_mvtit-mvt_ind       = 'F'.                "New
            i_mvtit-xstob         = c_x.
            i_mvtit-gr_rcpt       = i_resb-aufnr.       "New
            i_mvtit-reserv_no     = i_resb-rsnum.
            i_mvtit-res_item      = i_resb-rspos.
            APPEND i_mvtit.
    * HEADER ELEMENTS
            k_gmvt_code-gm_code    = c_03.
            k_gmvt_head-pstng_date = sy-datum.
            k_gmvt_head-doc_date   = sy-datum.
    * CREATE GOODS MOVEMENTS
            CALL FUNCTION 'BAPI_GOODSMVT_CREATE'
              EXPORTING
                goodsmvt_header = k_gmvt_head
                goodsmvt_code   = k_gmvt_code
              TABLES
                goodsmvt_item   = i_mvtit
                return          = i_return.
            CALL FUNCTION 'BAPI_TRANSACTION_COMMIT'
              EXPORTING
                wait = c_x.
            READ TABLE i_return INDEX 1.
            IF i_return-type EQ c_s.
              DELETE FROM zpsi7603_01 WHERE aufnr = i_resb-aufnr AND
                                            rsnum = i_resb-rsnum AND
                                            rspos = i_resb-rspos.
            ENDIF.
    If i run above code for <b>Goods Issue</b> it is giving error can anybody tell me what changes i need to do to make it work.
    The <b>Error Message</b> i am getting is as below:
    <b>Qty and / or "delivery completed" ind. or final issue ind. are missing</b>
    <b>Error Number for the above is : 264.</b>
    Can anybody solve my issue.
    Any help will be appreciated.
    Thanks in advance.
    Thanks & Regards,
    Rayeez.

    Hi,
    Thanks boss.
    It is working now correctly.
    The issue is the  i_mvtit-XSTOB should be equal space in case of Goods issue while incase of Reversal it should be equal to X.
    Thanks for ur efforts.
    I had awarded you points.
    Thanks a lot.
    Thanks & Regards,
    Rayeez.

  • Increase the number of portions in process for each conversion object

    I experts,
    I configured SAP TDMS 3.0 with SP 14 to transfer test data from QAS to DEV (both is ECC 6.0) for the first test with TDMS TIM (Time Based Reduction).
    The data transfer phase is still running (99% - 60hs running). We analyzed the Display Runtime Information report and see that objects of conversion with similar calc. records and calc. GBytes have very different the Net Runtime.
    TMDS currently is working with four objects of conversion, processing a portion of each.
    Conversion objects that are running are:
    - Z_LTBP_002
    - Z_TSEGE_002
    - Z_VEVW_002
    - Z_YST27_002
    We check in the receiver system, and we see that is use only one DIA process to update the each table.
    How can increase the performance of the update? Is correct that use only 1 DIA process for this??
    Can I increase the number of portions in process for each conversion object?
    Any help is greatly appreciated.
    Regards,
    Sergio

    Hi,
    Check SAP Note 916763 - TDMS performance composite SAP note
    Note 890797 - SAP TDMS - required and recommended system settings
    Thanks
    Sunny

  • Return Process for Depot Excise Billing.

    Hi,
    We are following Depot Excise Billing Process. Where we are using Stock Transport Purchase Order Process for transferring the goods from Mfg.Plant to Depot.
    Now, we require return process for returning the Goods from Depot to Mfg. Plant. Please also confirm Excise Register needs to be updated? If yes, please tell us the transaction for the same.
    For satisfactory answer ful points will be rewarded.
    Thanks and Regards,
    Dilip Shende

    Hi Murali,
    I have followed the procedure given. However, in J1IEX transaction system gives me error message "Excise Invoice 9001000027 28.05.2008 of plant 410027 does not exist"
    Where Excise Invoice 9001000027/28.05.2008 is the number generated in T.Code J1IJ. And 410027 is Vendor code.
    Please give your valuable suggession to solve the issue.
    Thanks and Regards 
    Dilip Shende

  • SQL Server 2012 installation failure An error occurred for a dependency of the feature causing the setup process for the feature to fail.

    I am installing SQL Server 2012 Developer (from ISO image written on DVD), my machine has Windows 7 (Edit: Windows 7 with service pack 1) on it. This machine already has SQL Express and SQL 2008 R2 Express installed in it.
    On running 2012 setup it goes fine from Setup Support Rules to Installation Progress. In  Installation Progress after some progress installation fails.
    Windows show the following components couldn't installed:
    Managment Tools Complete  Failed. Client Tools Connectivity Failed. Client Tools SDK Failed. Client Tools Backwards Compantibility Failed. Managment Tools Basic Failed. SQL Server Data Tools Failed. Reporting Services -Native Failed. Database Engine
    Services Failed. Data Quality Services Failed. full-Text and Semantic Extractins for Search Failed. SQL Server Replication Failed. Integration Services Failed. Analysis Services Failed. SQL Client Connectivity SDK Failed.
    In detail for failure of every component it provide these details:
    Action required:
    Use the following information to resolve the error, and then try the setup process again.
    Feature failure reason:
    An error occurred for a dependency of the feature causing the setup process for the feature to fail.
    In summary log file it provide the following details:
    Overall summary:
      Final result:                  Failed: see details below
      Exit code (Decimal):           -2068643839
      Start time:                    2012-07-31 16:23:37
      End time:                      2012-07-31 16:33:32
      Requested action:              Install
    Setup completed with required actions for features.
    Troubleshooting information for those features:
      Next step for Adv_SSMS:        Use the following information to resolve the error, and then try the setup process again.
      Next step for Conn:            Use the following information to resolve the error, and then try the setup process again.
      Next step for SDK:             Use the following information to resolve the error, and then try the setup process again.
      Next step for BC:              Use the following information to resolve the error, and then try the setup process again.
      Next step for SSMS:            Use the following information to resolve the error, and then try the setup process again.
      Next step for BIDS:            Use the following information to resolve the error, and then try the setup process again.
      Next step for RS:              Use the following information to resolve the error, and then try the setup process again.
      Next step for SQLEngine:       Use the following information to resolve the error, and then try the setup process again.
      Next step for DQ:              Use the following information to resolve the error, and then try the setup process again.
      Next step for FullText:        Use the following information to resolve the error, and then try the setup process again.
      Next step for Replication:     Use the following information to resolve the error, and then try the setup process again.
      Next step for IS:              Use the following information to resolve the error, and then try the setup process again.
      Next step for AS:              Use the following information to resolve the error, and then try the setup process again.
      Next step for SNAC_SDK:        Use the following information to resolve the error, and then try the setup process again.
    Machine Properties:
      Machine name:                  Haansi-PC
      Machine processor count:       4
      OS version:                    Windows 7
      OS service pack:               Service Pack 1
      OS region:                     United States
      OS language:                   English (United States)
      OS architecture:               x64
      Process architecture:          64 Bit
      OS clustered:                  No
    Product features discovered:
      Product              Instance             Instance ID                   
    Feature                                  Language            
    Edition              Version         Clustered
      SQL Server 2005      SQLEXPRESS           MSSQL.1                       
    Database Engine Services                 1033                 Express Edition     
    9.4.5000        No        
      SQL Server 2005      SQLEXPRESS           MSSQL.1                       
    SQL Server Replication                   1033                 Express Edition     
    9.4.5000        No        
      SQL Server 2005      SQLEXPRESS           MSSQL.1                       
    SharedTools                              1033                
    Express Edition      9.4.5000        No        
      SQL Server 2005                                                         
    Tools                                    1033                
    Express Edition      9.4.5000        No        
      SQL Server 2005                                                         
    ToolsClient                              1033                
    Express Edition      9.4.5000        No        
      SQL Server 2005                                                         
    ToolsClient\Connectivity                 1033                 Express Edition     
    9.4.5000        No        
      SQL Server 2008 R2   SQLSERVER08EXPR2     MSSQL10_50.SQLSERVER08EXPR2    Database Engine Services                 1033                
    Express Edition      10.50.1617.0    No        
      SQL Server 2008 R2   SQLSERVER08EXPR2     MSSQL10_50.SQLSERVER08EXPR2    SQL Server Replication                   1033                
    Express Edition      10.50.1617.0    No        
      SQL Server 2008 R2                                                      
    Management Tools - Basic                 1033                 Express Edition     
    10.50.1617.0    No        
      SQL Server 2012                                                         
    LocalDB                                  1033                
    Express Edition      11.0.2318.0     No        
      SQL Server 2012                                                         
    Reporting Services - SharePoint                                                   
    11.0.2100.60    No        
    Package properties:
      Description:                   Microsoft SQL Server 2012
      ProductName:                   SQL Server 2012
      Type:                          RTM
      Version:                       11
      SPLevel:                       0
      Installation location:         F:\x64\setup\
      Installation edition:          Developer
    Product Update Status:
      None discovered.
    User Input Settings:
      ACTION:                        Install
      ADDCURRENTUSERASSQLADMIN:      false
      AGTSVCACCOUNT:                 NT Service\SQLAgent$SS2012
      AGTSVCPASSWORD:                *****
      AGTSVCSTARTUPTYPE:             Manual
      ASBACKUPDIR:                   C:\Program Files\Microsoft SQL Server\MSAS11.SS2012\OLAP\Backup
      ASCOLLATION:                   Latin1_General_CI_AS
      ASCONFIGDIR:                   C:\Program Files\Microsoft SQL Server\MSAS11.SS2012\OLAP\Config
      ASDATADIR:                     C:\Program Files\Microsoft SQL Server\MSAS11.SS2012\OLAP\Data
      ASLOGDIR:                      C:\Program Files\Microsoft SQL Server\MSAS11.SS2012\OLAP\Log
      ASPROVIDERMSOLAP:              1
      ASSERVERMODE:                  TABULAR
      ASSVCACCOUNT:                  NT Service\MSOLAP$SS2012
      ASSVCPASSWORD:                 <empty>
      ASSVCSTARTUPTYPE:              Manual
      ASSYSADMINACCOUNTS:            PC\Haansi
      ASTEMPDIR:                     C:\Program Files\Microsoft SQL Server\MSAS11.SS2012\OLAP\Temp
      BROWSERSVCSTARTUPTYPE:         Automatic
      CLTCTLRNAME:                   <empty>
      CLTRESULTDIR:                  <empty>
      CLTSTARTUPTYPE:                0
      CLTSVCACCOUNT:                 <empty>
      CLTSVCPASSWORD:                <empty>
      CLTWORKINGDIR:                 <empty>
      COMMFABRICENCRYPTION:          0
      COMMFABRICNETWORKLEVEL:        0
      COMMFABRICPORT:                0
      CONFIGURATIONFILE:             C:\Program Files\Microsoft SQL Server\110\Setup Bootstrap\Log\20120731_161013\ConfigurationFile.ini
      CTLRSTARTUPTYPE:               0
      CTLRSVCACCOUNT:                <empty>
      CTLRSVCPASSWORD:               <empty>
      CTLRUSERS:                     <empty>
      ENABLERANU:                    false
      ENU:                           true
      ERRORREPORTING:                false
      FEATURES:                      SQLENGINE, REPLICATION, FULLTEXT, DQ, AS, RS, BIDS, CONN, IS, BC, SDK, SSMS, ADV_SSMS, SNAC_SDK
      FILESTREAMLEVEL:               0
      FILESTREAMSHARENAME:           <empty>
      FTSVCACCOUNT:                  NT Service\MSSQLFDLauncher$SS2012
      FTSVCPASSWORD:                 <empty>
      HELP:                          false
      INDICATEPROGRESS:              false
      INSTALLSHAREDDIR:              C:\Program Files\Microsoft SQL Server\
      INSTALLSHAREDWOWDIR:           C:\Program Files (x86)\Microsoft SQL Server\
      INSTALLSQLDATADIR:             <empty>
      INSTANCEDIR:                   C:\Program Files\Microsoft SQL Server\
      INSTANCEID:                    SS2012
      INSTANCENAME:                  SS2012
      ISSVCACCOUNT:                  NT Service\MsDtsServer110
      ISSVCPASSWORD:                 <empty>
      ISSVCSTARTUPTYPE:              Automatic
      MATRIXCMBRICKCOMMPORT:         0
      MATRIXCMSERVERNAME:            <empty>
      MATRIXNAME:                    <empty>
      NPENABLED:                     0
      PID:                           *****
      QUIET:                         false
      QUIETSIMPLE:                   false
      ROLE:                          <empty>
      RSINSTALLMODE:                 DefaultNativeMode
      RSSHPINSTALLMODE:              DefaultSharePointMode
      RSSVCACCOUNT:                  NT Service\ReportServer$SS2012
      RSSVCPASSWORD:                 <empty>
      RSSVCSTARTUPTYPE:              Manual
      SAPWD:                         <empty>
      SECURITYMODE:                  <empty>
      SQLBACKUPDIR:                  <empty>
      SQLCOLLATION:                  SQL_Latin1_General_CP1_CI_AS
      SQLSVCACCOUNT:                 NT Service\MSSQL$SS2012
      SQLSVCPASSWORD:                <empty>
      SQLSVCSTARTUPTYPE:             Automatic
      SQLSYSADMINACCOUNTS:           Haansi-PC\Haansi
      SQLTEMPDBDIR:                  <empty>
      SQLTEMPDBLOGDIR:               <empty>
      SQLUSERDBDIR:                  <empty>
      SQLUSERDBLOGDIR:               <empty>
      SQMREPORTING:                  false
      TCPENABLED:                    0
      UIMODE:                        Normal
      UpdateEnabled:                 true
      UpdateSource:                  MU
      X86:                           false
      Configuration file:            C:\Program Files\Microsoft SQL Server\110\Setup Bootstrap\Log\20120731_161013\ConfigurationFile.ini
    Detailed results:
      Feature:                       Management Tools - Complete
      Status:                        Failed: see logs for details
      Reason for failure:            An error occurred for a dependency of the feature causing the setup process for the feature to fail.
      Next Step:                     Use the following information to resolve the error, and then try the setup process again.
      Feature:                       Client Tools Connectivity
      Status:                        Failed: see logs for details
      Reason for failure:            An error occurred for a dependency of the feature causing the setup process for the feature to fail.
      Next Step:                     Use the following information to resolve the error, and then try the setup process again.
      Feature:                       Client Tools SDK
      Status:                        Failed: see logs for details
      Reason for failure:            An error occurred for a dependency of the feature causing the setup process for the feature to fail.
      Next Step:                     Use the following information to resolve the error, and then try the setup process again.
      Feature:                       Client Tools Backwards Compatibility
      Status:                        Failed: see logs for details
      Reason for failure:            An error occurred for a dependency of the feature causing the setup process for the feature to fail.
      Next Step:                     Use the following information to resolve the error, and then try the setup process again.
      Feature:                       Management Tools - Basic
      Status:                        Failed: see logs for details
      Reason for failure:            An error occurred for a dependency of the feature causing the setup process for the feature to fail.
      Next Step:                     Use the following information to resolve the error, and then try the setup process again.
      Feature:                       SQL Server Data Tools
      Status:                        Failed: see logs for details
      Reason for failure:            An error occurred for a dependency of the feature causing the setup process for the feature to fail.
      Next Step:                     Use the following information to resolve the error, and then try the setup process again.
      Feature:                       Reporting Services - Native
      Status:                        Failed: see logs for details
      Reason for failure:            An error occurred for a dependency of the feature causing the setup process for the feature to fail.
      Next Step:                     Use the following information to resolve the error, and then try the setup process again.
      Feature:                       Database Engine Services
      Status:                        Failed: see logs for details
      Reason for failure:            An error occurred for a dependency of the feature causing the setup process for the feature to fail.
      Next Step:                     Use the following information to resolve the error, and then try the setup process again.
      Feature:                       Data Quality Services
      Status:                        Failed: see logs for details
      Reason for failure:            An error occurred for a dependency of the feature causing the setup process for the feature to fail.
      Next Step:                     Use the following information to resolve the error, and then try the setup process again.
      Feature:                       Full-Text and Semantic Extractions for Search
      Status:                        Failed: see logs for details
      Reason for failure:            An error occurred for a dependency of the feature causing the setup process for the feature to fail.
      Next Step:                     Use the following information to resolve the error, and then try the setup process again.
      Feature:                       SQL Server Replication
      Status:                        Failed: see logs for details
      Reason for failure:            An error occurred for a dependency of the feature causing the setup process for the feature to fail.
      Next Step:                     Use the following information to resolve the error, and then try the setup process again.
      Feature:                       Integration Services
      Status:                        Failed: see logs for details
      Reason for failure:            An error occurred for a dependency of the feature causing the setup process for the feature to fail.
      Next Step:                     Use the following information to resolve the error, and then try the setup process again.
      Feature:                       Analysis Services
      Status:                        Failed: see logs for details
      Reason for failure:            An error occurred for a dependency of the feature causing the setup process for the feature to fail.
      Next Step:                     Use the following information to resolve the error, and then try the setup process again.
      Feature:                       SQL Client Connectivity SDK
      Status:                        Failed: see logs for details
      Reason for failure:            An error occurred during the setup process of the feature.
      Next Step:                     Use the following information to resolve the error, and then try the setup process again.
    Rules with failures:
    Global rules:
    Scenario specific rules:
    Rules report file:               C:\Program Files\Microsoft SQL Server\110\Setup Bootstrap\Log\20120731_161013\SystemConfigurationCheck_Report.htm

    Please help. 
    I did what you suggested, but, still got error message to install SQL server data tools: Here is the log.
    Overall summary:
      Final result:                  Failed: see details below
      Exit code (Decimal):           -2068037632
      Start time:                    2014-09-29 15:05:38
      End time:                      2014-09-29 15:15:55
      Requested action:              Install
    Setup completed with required actions for features.
    Troubleshooting information for those features:
      Next step for SSDTBI_VS2012:   Use the following information to resolve the error, and then try the setup process again.
    Machine Properties:
      Machine name:                  MSBI
      Machine processor count:       4
      OS version:                    Future Windows Version
      OS service pack:               
      OS region:                     United States
      OS language:                   English (United States)
      OS architecture:               x64
      Process architecture:          32 Bit
      OS clustered:                  No
    Product features discovered:
      Product              Instance             Instance ID                    Feature                
                     Language             Edition              Version         Clustered  Configured
      SQL Server 2008                                                          Management Tools - Basic  
                  1033                 Express Edition      10.0.1600.22    No         Yes       
      SQL Server 2012      MSSQLSERVER          MSSQL11.MSSQLSERVER            Database Engine Services                 1033      
              Enterprise Evaluation Edition 11.0.2100.60    No         Yes       
      SQL Server 2012      MSSQLSERVER          MSSQL11.MSSQLSERVER            SQL Server Replication                   1033      
              Enterprise Evaluation Edition 11.0.2100.60    No         Yes       
      SQL Server 2012      MSSQLSERVER          MSSQL11.MSSQLSERVER            Full-Text and Semantic Extractions for Search 1033                
    Enterprise Evaluation Edition 11.0.2100.60    No         Yes       
      SQL Server 2012      MSSQLSERVER          MSSQL11.MSSQLSERVER            Data Quality Services                    1033    
                Enterprise Evaluation Edition 11.0.2100.60    No         Yes       
      SQL Server 2012      MSSQLSERVER          MSAS11.MSSQLSERVER             Analysis Services                        1033  
                  Enterprise Evaluation Edition 11.0.2100.60    No         Yes       
      SQL Server 2012      MSSQLSERVER          MSRS11.MSSQLSERVER             Reporting Services - Native              1033        
            Enterprise Evaluation Edition 11.0.2100.60    No         Yes       
      SQL Server 2012                                                          Management Tools - Basic  
                  1033                 Enterprise Evaluation Edition 11.0.2100.60    No         Yes       
      SQL Server 2012                                                          Management Tools - Complete  
               1033                 Enterprise Evaluation Edition 11.0.2100.60    No         Yes       
      SQL Server 2012                                                          Client Tools Connectivity  
                 1033                 Enterprise Evaluation Edition 11.0.2100.60    No         Yes       
      SQL Server 2012                                                          Client Tools Backwards Compatibility
        1033                 Enterprise Evaluation Edition 11.0.2100.60    No         Yes       
      SQL Server 2012                                                          Client Tools SDK      
                      1033                 Enterprise Evaluation Edition 11.0.2100.60    No         Yes       
      SQL Server 2012                                                          SQL Server Data Tools    
                   1033                 Enterprise Evaluation Edition 11.0.2100.60    No         Yes       
      SQL Server 2012                                                          Integration Services    
                    1033                 Enterprise Evaluation Edition 11.0.2100.60    No         Yes       
      SQL Server 2012                                                          Reporting Services - SharePoint
                                                       11.0.2100.60    No         Yes    
    Package properties:
      Description:                   Microsoft SQL Server 2012 Service Pack 1
      ProductName:                   SQL Server 2012
      Type:                          RTM
      Version:                       11
      Installation location:         C:\9f7a58aa5d6d76ffe6be968a4ad339f5\x86\setup\
      Installation edition:          Express
      Slipstream:                    True
      SP Level                       1
      Patch Level:                   11.1.3128.0
    Product Update Status:
      Success: KB 2674319, KB 2793634
    Product Updates Selected for Installation:
      Title:                         Service Pack 1
      Knowledge Based Article:       KB 2674319
      Version:                       11.1.3000.0
      Architecture:                  x86
      Language:                      1033
      Title:                         SQL Server 2012 SP1 GDR Product Update
      Knowledge Based Article:       KB 2793634
      Version:                       11.1.3128.0
      Architecture:                  x86
      Language:                      All
      Update Source:                 MU
    User Input Settings:
      ACTION:                        Install
      ADDCURRENTUSERASSQLADMIN:      true
      AGTSVCACCOUNT:                 <empty>
      AGTSVCPASSWORD:                <empty>
      AGTSVCSTARTUPTYPE:             Manual
      ASBACKUPDIR:                   Backup
      ASCOLLATION:                   Latin1_General_CI_AS
      ASCONFIGDIR:                   Config
      ASDATADIR:                     Data
      ASLOGDIR:                      Log
      ASPROVIDERMSOLAP:              1
      ASSERVERMODE:                  MULTIDIMENSIONAL
      ASSVCACCOUNT:                  <empty>
      ASSVCPASSWORD:                 <empty>
      ASSVCSTARTUPTYPE:              Automatic
      ASSYSADMINACCOUNTS:            <empty>
      ASTEMPDIR:                     Temp
      BROWSERSVCSTARTUPTYPE:         Disabled
      CLTCTLRNAME:                   <empty>
      CLTRESULTDIR:                  <empty>
      CLTSTARTUPTYPE:                0
      CLTSVCACCOUNT:                 <empty>
      CLTSVCPASSWORD:                <empty>
      CLTWORKINGDIR:                 <empty>
      COMMFABRICENCRYPTION:          0
      COMMFABRICNETWORKLEVEL:        0
      COMMFABRICPORT:                0
      CONFIGURATIONFILE:             
      CTLRSTARTUPTYPE:               0
      CTLRSVCACCOUNT:                <empty>
      CTLRSVCPASSWORD:               <empty>
      CTLRUSERS:                     <empty>
      ENABLERANU:                    false
      ENU:                           true
      ERRORREPORTING:                true
      FEATURES:                      SSDTBI_VS2012, SNAC_SDK
      FILESTREAMLEVEL:               0
      FILESTREAMSHARENAME:           <empty>
      FTSVCACCOUNT:                  <empty>
      FTSVCPASSWORD:                 <empty>
      HELP:                          false
      IACCEPTSQLSERVERLICENSETERMS:  true
      INDICATEPROGRESS:              false
      INSTALLSHAREDDIR:              C:\Program Files\Microsoft SQL Server\
      INSTALLSHAREDWOWDIR:           C:\Program Files (x86)\Microsoft SQL Server\
      INSTALLSQLDATADIR:             <empty>
      INSTANCEDIR:                   C:\Program Files (x86)\Microsoft SQL Server\
      INSTANCEID:                    <empty>
      INSTANCENAME:                  <empty>
      ISSVCACCOUNT:                  NT AUTHORITY\Network Service
      ISSVCPASSWORD:                 <empty>
      ISSVCSTARTUPTYPE:              Automatic
      MATRIXCMBRICKCOMMPORT:         0
      MATRIXCMSERVERNAME:            <empty>
      MATRIXNAME:                    <empty>
      NPENABLED:                     0
      PID:                           *****
      QUIET:                         false
      QUIETSIMPLE:                   false
      ROLE:                          AllFeatures_WithDefaults
      RSINSTALLMODE:                 DefaultNativeMode
      RSSHPINSTALLMODE:              DefaultSharePointMode
      RSSVCACCOUNT:                  <empty>
      RSSVCPASSWORD:                 <empty>
      RSSVCSTARTUPTYPE:              Automatic
      SAPWD:                         <empty>
      SECURITYMODE:                  <empty>
      SQLBACKUPDIR:                  <empty>
      SQLCOLLATION:                  SQL_Latin1_General_CP1_CI_AS
      SQLSVCACCOUNT:                 <empty>
      SQLSVCPASSWORD:                <empty>
      SQLSVCSTARTUPTYPE:             Automatic
      SQLSYSADMINACCOUNTS:           <empty>
      SQLTEMPDBDIR:                  <empty>
      SQLTEMPDBLOGDIR:               <empty>
      SQLUSERDBDIR:                  <empty>
      SQLUSERDBLOGDIR:               <empty>
      SQMREPORTING:                  true
      TCPENABLED:                    0
      UIMODE:                        AutoAdvance
      UpdateEnabled:                 true
      UpdateSource:                  MU
      X86:                           false
      Configuration file:            C:\Program Files (x86)\Microsoft SQL Server\110\Setup Bootstrap\Log\20140929_150412\ConfigurationFile.ini
    Detailed results:
      Feature:                       SQL Server Data Tools - Business Intelligence for Visual Studio 2012
      Status:                        Failed: see logs for details
      Reason for failure:            An error occurred for a dependency of the feature causing the setup process for the feature to fail.
      Next Step:                     Use the following information to resolve the error, and then try the setup process again.
      Component name:                Microsoft Visual Studio Tools for Applications 2012
      Component error code:          0x80044000
      Component log file:            C:\Program Files (x86)\Microsoft SQL Server\110\Setup Bootstrap\Log\20140929_150412\VSTA2012_LangsSupport_Cpu32_1.log
      Error description:             VS Shell 2012 installation has failed with exit code -2147205120.
      Error help link:               http://go.microsoft.com/fwlink?LinkId=20476&ProdName=Microsoft+SQL+Server&EvtSrc=setup.rll&EvtID=50000&ProdVer=11.0.3436.0&EvtType=VSTA2012_LangsSupport%40Install%400x-2147205120
      Feature:                       SQL Client Connectivity
      Status:                        Passed
      Feature:                       SQL Client Connectivity SDK
      Status:                        Passed
    Rules with failures:
    Global rules:
    Scenario specific rules:
    Rules report file:               C:\Program Files (x86)\Microsoft SQL Server\110\Setup Bootstrap\Log\20140929_150412\SystemConfigurationCheck_Report.htm

  • Regarding Goods Reversal & Goods Issue Process for PO

    Hi Experts,
               Could you any one tel me what is Goods Reversal and Goods Issue process for PO...
    How to create the FM & detailed Procedure Pls?....
    Please any one tel me.......
    Thanks & Reagards
    HB

    Hi Hans,
    SOURCE : HELP.SAP
    Purpose
    Inventory Management uses this process in such a way that the goods issue posting is divided into two parts that run in separate systems. Posting the GI document in the supplying plant results in a message to the receiving plant. The receiving plant then performs a complementary posting. The physical goods receipt takes place as usual.
    Prerequisites
    When using batch processing, the following prerequisites must be fulfilled:
    Both the original and target systems have the same batch definition level.
    The batch definition level is either the material or the client.
    An ALE scenario exists for materials and classes (characteristics).
    Unique batch numbers exist cross-system.
    Batches can only be changed in their original system when they are not decoupled. From an organizational point of view, this must also lead to the batch status being changeable in a local SAP R/3 system. For example, this is impossible when transfer posting to a new batch and results in further actions, for example, relabeling containers, palettes and so on.
    Characteristics
    As for the purchase order in a one-system situation, the system should automatically post the material into the stock in transit at the receiving profit center and the corresponding Profit Center Accounting using intra-CC transfer prices at goods issue for the purchase order and the unchecked delivery. This requirement is valid for one-system situations as well as for two-system situations where there is an ALE interface. No internal billing document should be created.
    In a two-system case, the receiving profit center should be derived at goods issue from the unchecked delivery. Profit Center Accounting then takes place with
    Stock change transfer price to stock
    Internal expense to internal sales
    Internal clearing account to stock change transfer price.
    Account determination in a purchase order for an intra-company-code transaction must be different from account determination in external transactions. Automatic GR/IR account clearing is required in both one-system and two-system situations.
    The stock in transit must be visible in the receiving profit center.
    The system must send a shipping notification at goods issue in one-system and two-system situations.
    You need to create an invoice document for the internal and external trading statistics for cross-boundary deliveries as well as for customs purposes.
    GR/GI slips are created.
    Process Flow
    Goods Issue Posting for Stock Transfers
    The delivery triggers the goods issue in the issuing system.
    The call contains the stock transport order data known in the delivery, including the PO item and the logical system of the recipient.
    The transaction (quantity and value updates) is selected using the movement type:
    Movement Type     
    Function
    641     
    Goods issue with UB logic (Creation of stock in transit at recipient, immediate value posting).
    647     
    As 641, however the goods receipt line (movement type 101) is added automatically, so that the goods receipt is posted at the same time as the goods issue (one-step procedure).
    You determine the movement type according to the schedule line category in Sales and Distribution. The goods issue for a cross-system stock transfer must be different from the integrated transaction. This is achieved by adding a new movement type.
    You post quantities and values at goods issue in the same way as a goods issue for a sales order. That is to say, the quantity is posted in the supplying plant and the value is adjusted to that of the stock account. The offsetting posting is made to a clearing account. The known data from the delivery is copied to Accounting to balance the account where necessary.
    The system creates a message to the appropriate receiving system for all items with reference to a cross-system purchase order. The system does not perform any validity checks on the recipient’s data before posting begins. Incorrect Customizing results in the update being terminated.
    If a goods issue has receiving plants in different logical systems, an IDoc is sent for each system.
    In order that the goods receipt is able to use the values on the receiver side, you must add the values used to post the goods movement, in particular the transfer prices, to the IDoc.
    The logic for recognizing the profit center switch functions as follows: At goods issue, the system recognizes that the profit center of the issuing plant is different from the profit center of the receiving plant. The system derives the profit center node from the relevant profit center.
    Data Transfer
    The IDocs sent by the issuing plant trigger the goods issue postings in the receiving plant.
    Background Posting in the Receiving System
    The goods receipt is posted in the receiving system using the IDoc. The interface receives the data from the goods issue in the supplying plant. The following processes now run at the recipient:
    The system finds the update control for the GR part of the posting.
    The goods movement is posted with the new movement type.
    During valuation of the goods receipt, the system might, where necessary (UB logic), refer to the values (legal value and the value from the parallel valuation type, if you are using the transfer price function) from the IDoc.
    The PO history is updated. The PO history is updated with the material document number from the second part of the GI posting. The GI document number is not stored in the supplying plant, because there is no way to display this document.
    In two-step procedures the goods receipt is posted to the stock in transit.
    Reversal
    You can only reverse this goods issue for the PO using the cancellation transaction in SD. You cannot reverse the GI in Inventory Management.
    The material document that is automatically created in the receiving system cannot be canceled. This reversal is triggered by the sending system (the actual reversal of the GI document takes place there) and transmits the data, including the reversal movement type, to the receiving system. No actual reversal is posted in the receiving system, because the material document number of the original document does not exist in this system. This scenario is applicable for cases where you use the two-step procedure (with stock in transit).
    Distribution of Batch Master Data and Characteristics
    The batch information is transported using the message category BATMAS.
    When you create a cross-system goods issue, the system creates the corresponding IDoc using the message category BATMAS.
    When the delivery arrives in the target system, the batch and all the information is already present in the system.
    Changes to the batch data are also distributed using the message category BATMAS.
    The batch can be decoupled in the receiving SAP R/3 system. This means that the batch can have a different status in the receiving system than in the original system. By setting an indicator at material level, you decide whether the batch can be decoupled or whether the batch and all its attributes are copied from the original system. "Decoupled" i.e. "locally independent" batches are no longer distributed from its own system.
    The batch data does not need to be available before the physical goods receipt takes place. The goods receipt into the stock in transit does not usually refer to the batch unless you are working with batches with assigned active ingredient values.
    If the GI cannot be posted for organizational reasons, for example because the goods cannot be loaded onto a truck until 10pm, then you can post the goods into the GR blocked stock. This stock is also non-batch-specific.
    In cases where the GI IDoc arrives before the batch IDoc, then the GI IDoc can be subsequently posted by a periodically scheduled report (transaction BD87). A program like this exists in the SAP standard system. In Customizing for MM Inventory Management (activity Copy, Change Movement Types), you should make settings to define that manual creation of batches at goods receipt is not allowed.
    Shipping Notification
    The shipping notification is required in the receiving system due to its relevance for MRP. In this way, for example, a change in delivery date determined at goods issue is sent to the receiving system using the shipping notification. The shipping notification can also be used when posting the GR batches.
    Reward if found helpfull,
    Cheers,
    Chaitanya.

  • TS4057 I did this and now my videos are not working. They show the pictures aren't there on some and on others it shows they are there, but doesn't show them in the player. When I try to Share anything it just says Waiting for Processing for hours. What d

    I did this and now my videos are not working. They show the pictures aren't there on some and on others it shows they are there, but doesn't show them in the player. When I try to Share anything it just says Waiting for Processing for hours. What do I do?
    I also got Motion and can't figure out how to use it with Final Cut Pro X. Any help woud be great. Thanks

    I have no idea what may have caused your MacBook to stop working, but from your description it kind of sounds like it may have started before you ran Software Update and installed the new Apps. Just the general slow feeling and bugginess is what tips me off. You said that you weren't sure if you had closed all open windows, that doesn't matter if the computer restarts itself. It automatically closes all other open applications when restarting.
    As to your data being retrievable, if when you take it in they do a fresh install of the OS, then no, it will not be unless you want to pay several thousand dollars to a software retrieval company.
    I am glad to hear that you have taken into the Apple Store to get it fixed, and that you have all of your purchased music backed up to your iPod. You should be able to just transfer it all back to iTunes once you get your computer back should it be necessary.
    As a side note, the proper place for this topic would probably in the MacBook forums, not iTunes since there is no evidence that iTunes started the issue.

  • Guidelines required to analyze the extraction process for 2LIS_02_SCL.

    Hi All,
    I have a problem here regarding the extraction process for the DataSource 2LIS_02_SCL. The values posted by date fields like
    Posting Date (0PSTNG_DATE)
    Schedule Line Delivery Date (0SCL_DELDAT)
    Statistics Date  (0STAT_DATE)
    In BW are suspected to be wrong values.
    So I am supposed to check the extraction process for PO Schedule Line (2LIS_02_SCL).
    So how can I proceed with this analysis in BW side as well as in SAP R/3.
    Can anyone please help with the process.
    Thanks in advance.

    Hi,
    In Bw thre is always confusion about following Dates.
    Posting Date (0PSTNG_DATE)
    Schedule Line Delivery Date (0SCL_DELDAT)
    Statistics Date (0STAT_DATE)
    So ask Functional Consultants and Business USers and Identify the corretc Date in ECC and then Change the Mapping In UPdate Rules in BW. i.e. What date USer is wanting and accordingly we nee dtgo change the mapping in UPdate Rules in Time Char Tab in UpdateRules.
    Thanks
    Reddy

Maybe you are looking for