PO output & release strategy

Good day all,
i do not know if this thread has been posted before but i could not find anything that could help me.
In SAP, the moment you release a PO , it is automatically sent to vendor. however, i do not want it to be sent to the vendor automatically when it is released. how do i achieve this?
please assistas i am new to SAP MM.
Regards and many thanks,
Evelyn

Please use T code MN05, enter output type maintained for PO.
Enter parameters for which output type is maintained & then execute.
Select "Send Application with own transaction" in Dispatch time format instead of "Send immediately on saving".
Regards
Bhavesh Mistry

Similar Messages

  • Re-set release strategy of rejected PO,after doing respective changes to po

    Hi friends,
    I have created release strategy for Purchase order with release indicator 6 (Changeable, new rel. if new strat. or value change/outputted), and with 3 release codes (3 approvers)..
    Now in this case, After Rejection of a approver (creator of po will get an mail telling that its rejected). After rejection, the creator has did required changes and save the PO.
    However the release strategy is not reset...So i want to know how to reset the release strategy in this case..
    Where as in case after the approval, if creator do any changes in purchase order then release strategy is resets...  
    Here PO printout is possible only after the final approval...
    Pls give some inputs in fixing this issue..
    Thanks in advance....
    Regards
    Shashidhar...

    Hi
    What are the characteristics of your strategy?
    Try to change one of them save and then rechange it to the original
    eg.
    If the strategy depends for example on the Purchasing Group (PG)
    i mean according to different PG's different strategies working
    then with ME22N change the PG save and rechange it again to the original.
    or
    for example If the strategy depends on Materail Groups (MG)
    then do the change with MG
    With ME22N change the MG save and rechange it again to the original.
    I guess this will trigger the strategy again.
    Hope it helps
    Best Regards

  • New Release Strategy in case of PO amendment

    Dear All,
    We have the release strategy at PO level on 3 parameters,
    Purchasing Group, Value and Document type.. for each parameter we have created the characteristics EKKO- EKGRP, EKKO-BSART, EKKO-GNETW. Till date system is working ok and trigreeeing the release strategy as per it should.
    When ever users edit the PO, again system sets the release strategy as per above logic.
    Now our requiremet is, when ever user edite the PO value or PO quantity, system should trigger a new release strategy.I come to know that, SAP have a provision to maintain the release strategy on "Version level also", I have tried the same but i facing one problem, when we try to create the characteristic based on Version , system creates it and put field name "REVNO", data types is coming "CHAR".
    Can any one send me a user manual and steps for this.
    Thanks in advance,.
    Vikas

    Hi,
    You can set a control within Config. there is a parameter called as release indicator.
    Follow this IMG path:
    SPRO> Materials Management>Purchasing>Purchase Order>Release Procedure for Purchase Orders>Define Release Procedure for Purchase Orders>Release indicator
    1     Cannot be changed
    2     Changeable, no new determination of strategy
    3     Changeable, new release in case of new strategy
    4     Changeable, new release in case of new strat. or val. change
    5     Changeable, new release if new strategy/outputted
    6     Changeable, new rel. if new strat. or value change/outputted
         Changeable, new release in case of new strategy
    Changeability of purchasing document during/after release which means how the system reacts if an internal or external purchasing document is changed after the start of the release procedure.
    Note that the values 1 to 4 apply to internal purchasing documents (purchase requisitions) and the values 1 bis6 to external purchasing documents.
    So you would need to set this Indicator for the specific release Id. which specifies whether the purchasing document can be processed in or is blocked for follow-on functions.
    Hope this explanation was clear.
    Prashant Rathore.

  • PO Release Strategy not changed after deletion of few line items with less

    Subject : PO Release Strategy not changed after deletion of few line items with less Total PO
    Dear Friends
    We have issue with PO Release strategy. We have created the PO. with release strategy  with multiple approvers.  After approval of first approval manager , one of the PO line item got deleted and Total PO value is reduced . The new PO value should have changed the PO release strategy. But it is not changed. Old release strategy only showing in the PO which is wrong. 
    Details of the PO
    PO no 4500000123 with 5 line items Total PO value : 100,000 USD Release strategy : AB
    PO line item 5 deleted. Now total PO value changed to 50,000 USD and the PO release strategy should have been changed to AA but not changed. Still showing PO release strategy AB only.
    Are there any OSS notes available to correct his bug.
    Please let me know if you need more details
    Thanks in Advance
    Thanks
    MVS

    Hi,
    release indicators  change it to 4.It may works. Please explore to all 6 indicators..........
    i.e,
    1-cannot be changed
    2-changable,no new determination of strategy
    3-changable,new release in case of strategy
    4-changable,new release in case of strategy or value change
    5-changable,new release if new strategy/outputted
    6-changable,new release if new strategy or value changed/ outputted......
    And check   Characteristic description and value in Classification  of Release strategies ........
    I hope this will help you. Thanking you.
    Regards,
    Venkat.

  • User Exit for Purchase Order Release Strategy

    Hi,
    I am a little new to this, how do I search for a user exit for purchase order release strategy (TCode ME29N).
    Thanks in advance.
    Mick

    Hi
    Check the following Exits and BADI for Pur Requisition
    Enhancement
    MEVME001 WE default quantity calc. and over/ underdelivery tolerance
    MM06E001 User exits for EDI inbound and outbound purchasing documents
    MM06E003 Number range and document number
    MM06E004 Control import data screens in purchase order
    MM06E005 Customer fields in purchasing document
    MM06E007 Change document for requisitions upon conversion into PO
    MM06E008 Monitoring of contr. target value in case of release orders
    MM06E009 Relevant texts for "Texts exist" indicator
    MM06E010 Field selection for vendor address
    MM06E011 Activate PReq Block
    MMAL0001 ALE source list distribution: Outbound processing
    MMAL0002 ALE source list distribution: Inbound processing
    MMAL0003 ALE purcasing info record distribution: Outbound processing
    MMAL0004 ALE purchasing info record distribution: Inbound processing
    MMDA0001 Default delivery addresses
    MMFAB001 User exit for generation of release order
    MRFLB001 Control Items for Contract Release Order
    AMPL0001 User subscreen for additional data on AMPL
    LMEDR001 Enhancements to print program
    LMELA002 Adopt batch no. from shipping notification when posting a GR
    LMELA010 Inbound shipping notification: Transfer item data from IDOC
    LMEQR001 User exit for source determination
    LMEXF001 Conditions in Purchasing Documents Without Invoice Receipt
    LWSUS001 Customer-Specific Source Determination in Retail
    M06B0001 Role determination for purchase requisition release
    M06B0002 Changes to comm. structure for purchase requisition release
    M06B0003 Number range and document number
    MEQUERY1 Enhancement to Document Overview ME21N/ME51N
    MELAB001 Gen. forecast delivery schedules: Transfer schedule implem.
    MEFLD004 Determine earliest delivery date f. check w. GR (only PO)
    MEETA001 Define schedule line type (backlog, immed. req., preview)
    ME590001 Grouping of requsitions for PO split in ME59
    M06E0005 Role determination for release of purchasing documents
    M06E0004 Changes to communication structure for release purch. doc.
    M06B0005 Changes to comm. structure for overall release of requisn.
    M06B0004 Number range and document number
    Business Add-in
    ME_PROCESS_REQ_CUST Enhancements for Processing Enjoy PReqs: Customer
    ME_PROCESS_REQ Enhancements for Processing Enjoy PReqs: Internal
    ME_PROCESS_PO_CUST Enhancements for Processing Enjoy Purchase Order: Customer
    ME_PROCESS_PO Enhancements for Processing Enjoy Purchase Order: Intern.
    ME_PROCESS_COMP Processing of Component Default Data at Time of GR: Custome
    ME_PO_SC_SRV BAdI: Service Tab Page for Subcontracting
    ME_PO_PRICING_CUST Enhancements to Price Determination: Customer
    ME_PO_PRICING Enhancements to Price Determination: Internal
    ME_INFOREC_SEND Capture/Send Purchase Info Record Changes - Internal Use
    ME_HOLD_PO Hold Enjoy Purchase Orders: Activation/Deactivation
    ME_GUI_PO_CUST Customer's Own Screens in Enjoy Purchase Order
    ME_FIELDSTATUS_STOCK FM Account Assignment Behavior for Stock PR/PO
    ME_DP_CLEARING Clearing (Offsetting) of Down Payments and Payment Requests
    ME_PURCHDOC_POSTED Purchasing Document Posted
    SMOD_MRFLB001 Control Items for Contract Release Order
    EXTENSION_US_TAXES Extended Tax Calculation with Additional Data
    ARC_MM_EKKO_WRITE BAdI: Enhancement of Scope of Archiving (MM_EKKO)
    ARC_MM_EKKO_CHECK BAdI: Enhancement of Archivability Check (MM_EKKO)
    MM_EDI_DESADV_IN Supplementation of Delivery Interface from Purchase Order
    MM_DELIVERY_ADDR_SAP Determination of Delivery Address
    ME_WRF_STD_DNG PO Controlling Reminder: Extension to Standard Reminder
    ME_TRIGGER_ATP Triggers New ATP for Changes in EKKO, EKPO, EKPV
    ME_TRF_RULE_CUST_OFF BADI for Deactivation of Field T161V-REVFE
    ME_TAX_FROM_ADDRESS Tax jurisdiction code taken from address
    ME_REQ_POSTED Purchase Requisition Posted
    ME_REQ_OI_EXT Commitment Update in the Case of External Requisitions
    ME_RELEASE_CREATE BAdI: Release Creation for Sched.Agrmts with Release Docu.
    ME_DEFINE_CALCTYPE Control of Pricing Type: Additional Fields
    ME_CHANGE_OUTTAB Enrich ALV Output Table in Purchasing
    ME_CHANGE_CHARACTER Customer-Specific Characteristics for Product Allocation
    ME_CCP_DEL_DURATION Calc. of Delivery Duration in CCP Process (Not in Standard)
    ME_CCP_BESWK_AUTH_CH BAdI for authorization checks for procuring plant
    ME_CCP_ACTIVE_CHECK BAdI to check whether CCP process is active
    ME_BSART_DET Change document type for automatically generated POs
    ME_BAPI_PR_CREATE_02
    ME_BAPI_PR_CREATE_01
    ME_BAPI_PO_CREATE_02
    ME_BAPI_PO_CREATE_01
    ME_BADI_DISPLAY_DOC BAdI for Internal Control of Transaction to be Invoked
    ME_ACTV_CANCEL_PO BAdI for Activating the Cancel Function at Header Level
    MEGUI_LAYOUT BAdI for Enjoy Purchasing GUI
    ME_CHECK_ALL_ITEMS Run Through Items Again in the Event of Changes in EKKO
    ME_COMMTMNT_REQ_RE_C Check of Commitment Relevance of Purchase Requisitions
    ME_COMMTMNT_REQ_RELE Check of Commitment Relevance of Purchase Requisitions
    ME_COMMTMNT_PO_REL_C Check for Commitment-Relevance of Purchase Orders
    ME_COMMTMNT_PO_RELEV Check for Commitment-Relevance of Purchase Orders
    ME_COMMITMENT_STO_CH BadI for checking if commitments for STOs are active
    ME_COMMITMENT_RETURN Commitment for return item
    ME_CIP_REF_CHAR Enables Reference Characteristics in Purchasing
    ME_CIP_ALLOW_CHANGE Configuration in Purchasing: Changeability Control
    ME_CIN_MM06EFKO Copy PO data for use by Country version India
    ME_CIN_LEINRF2V BADI for LEINRF03 excise_invoice_details
    ME_CIN_LEINRF2R BADI for CIN India - Delivery charges
    ME_CHECK_SOURCES Additional Checks in Source Determination/Checking
    ME_CHECK_OA Check BAdI for Contracts
    Reward points if useful
    Rgds,
    Naren

  • Purchase Order E-mailing with Release Strategy

    Hello,
        We are experiencing an issue when e-mailing a Purchase Order which has a release strategy. When the order is released, the confirmation e-mails are going to the person who releases it when it is supposed to go to the person who has created the P.O. We are using a Smartform P.O. based on /SMB11/BL_MM_PO_L and print program /SMB40/FM06P. I must note that there was a bug found in the aforementioned print program and before that was fixed e-mailing would not work at all.
      We have also attempted to use all combinations of standard unmodified print programs and standard unmodified smartforms and have had no luck at getting the confirmation e-mail to send to the correct person this way either.
      SAP has recommended that we use program SAPFM06P with form Medruck. While this combination does work correctly, Medruck is not a Smartform. Has anybody here used a smartform Purchase Order with a release strategy and had the confirmation e-mail send to the created and not the releasor?
      Below is a list of the print programs and forms we have tried in various combinations. We are running ECC6/Basis 7
    Print Programs:
    /SMB11/FM06P
    /SMB40/FM06P
    SAPFM06P (Sapscript Only)
    Forms:
    /SMB11/BL_MMPO_L
    /SMB11/MMPO_L
    /SMB40/MMPO_L

    Hi,
    Purchase order via e-mail in SAP sys,the configurations and pre-requisites are follow:
    1. You must maintain an e-mail address in the address in the vendor master.
    2. The same applies to your own user master. You also have to specify an e-mail address there in order to identify the sender.
    Note that it is not possible to change the e-mail address of the vendor via the SAP purchase order transaction (ME21N, ME22N, and so on). The system only uses the e-mail address of the vendor that is maintained in the vendor master!
    3. For the output type for default values, a communication strategy needs to be maintained in the Customizing that supports the e-mail. You can find the definition of the communication strategy in the Customizing via the following path: (SPRO -> IMG -> SAP Web Application Server -> Basic Services -> Message Control -> Define Communication Strategy). As a default, communication strategy CS01 is delivered. This already contains the necessary entry for the external communication. Bear in mind that without a suitable communication strategy it is not possible to communicate with a partner via Medium 5 (external sending).
    4. Use the standard SAP environment (program 'SAPFM06P', FORM routine 'ENTRY_NEU' and form 'MEDRUCK') as the processing routines.
    5. In the condition records for the output type (for example, Transaction MN04), use medium '5' (External send).
    6. You can use Transaction SCOT to trigger the output manually. The prerequisite for a correct sending is that the node is set correctly. This is not described here, but it must have already been carried out.
    7. To be able to display, for example, the e-mail in Outlook, enter PDF as the format in the node.
    For more details, check SAP note:191470
    Regards,
    Biju K

  • Chek budget in PO with release strategy

    Hi
    When i created a PO with a release strategy and the comand need it, the budget are not checking at the save, only when i release the PO.
    Is it possible to check the budget (on a PM order or on WBS element) at the PO save.
    Thank's
    serge

    Normally checks like those happen once the PO is released ( example  - output is not allowed etc)...
    You may need to add something in the PO release strategy user exit to do the check before release (after save), Look into the below to see if this works.
    Name of the Enhancement: - M06E0004
    Name of the function module: - EXIT_SAPLEBND_002
    Hope this helps

  • Release strategy for auto created PO's

    Hi Guys,
    I have a requirement to implement release strategy for automatically created PO's.
    PR's are created automatically and we have a program which create PO's automatically.
    we would want to release them before generating output to vendor.
    could anyone please have any inputs here.
    regards
    mittu

    Hi!
    You may use your existing release strategy or create a new one (depending on your requirement). You just have to add/ use the document type you used for your auto-generated POs.
    Hope this helps! =)

  • Document release strategy

    Dear Gurus,
    The question is regarding purchasing documents release procedure.
    According to workflow setup(SWDD T-code), the required document flow finishes when CONFIRMATION sent after document is released, thus if I've issued output from the released document further cancellation of release is not possible. Could you please advice whether this option can be turned off? And where I can define output type for this Confirmation?
    e.g. my requirements- to be able to release/cancel release for purch docs without any additional checks

    The way to achieve this requirement is to create a custom field in the PO header that signifies that the PO has been changed.
    It should be populated with a value say - X when a change is done and presence of this X should trigger release strategy. So you will need only this field in the characterisitcs and through user exit populate this field with X when PO was created and once released, make it blank. Then when changed repopulate with X
    In this way you can ensure that any change to PO will trigger the release strategy

  • Send purchase order e-mail with release strategy

    Hi!!
    I have a problem with sending e-mails in purchase order that are blocked with release strategy.
    I create a purchase order that is block for the release strategy, then I release it. This is working OK, but I can't send an e-mail with this released puchase order, to do it, I have to modify something in the purchase order.
    Somebody knows what is happening?
    I would like to send e-mails without previous modification of the purchase order.
    Thanks for your help.

    Hi,
    Purchase order via e-mail in SAP sys,the configurations and pre-requisites are follow:
    1. You must maintain an e-mail address in the address in the vendor master.
    2. The same applies to your own user master. You also have to specify an e-mail address there in order to identify the sender.
    Note that it is not possible to change the e-mail address of the vendor via the SAP purchase order transaction (ME21N, ME22N, and so on). The system only uses the e-mail address of the vendor that is maintained in the vendor master!
    3. For the output type for default values, a communication strategy needs to be maintained in the Customizing that supports the e-mail. You can find the definition of the communication strategy in the Customizing via the following path: (SPRO -> IMG -> SAP Web Application Server -> Basic Services -> Message Control -> Define Communication Strategy). As a default, communication strategy CS01 is delivered. This already contains the necessary entry for the external communication. Bear in mind that without a suitable communication strategy it is not possible to communicate with a partner via Medium 5 (external sending).
    4. Use the standard SAP environment (program 'SAPFM06P', FORM routine 'ENTRY_NEU' and form 'MEDRUCK') as the processing routines.
    5. In the condition records for the output type (for example, Transaction MN04), use medium '5' (External send).
    6. You can use Transaction SCOT to trigger the output manually. The prerequisite for a correct sending is that the node is set correctly. This is not described here, but it must have already been carried out.
    7. To be able to display, for example, the e-mail in Outlook, enter PDF as the format in the node.
    For more details, check SAP note:191470
    Regards,
    Biju K

  • The PO was printed straight away without going through Release Strategy.

    Hello,
    Purchase order was raised in March for over Rs 1,000,000/- and went through the Release Strategy for printing.
    The value of this order was changed today - about Rs 7,000/- was added in the purchase order.
    The Purchase Order was printed straight away without going through Release Strategy,
    In a customization we have maintained the Release strategy for the Purchase order
    Please provide the solution on this issue.
    Regards
    Sarin
    Edited by: sarin toms on Nov 26, 2008 1:57 PM

    Dear,
    Check at....OLME-->PO->Release Procedure->Configure Release procedure for PO> Release Indicator--> Pl. Check In Changebility of Release Procedure after release...here you have to give the option " 4".....and percentage of changebility also you have to take care...
    Apart from that...in OLME--> Messages--> Message output---> Message determination...you have to fine tune your message type for Change mode...
    Changeability 4 and percentage 0 will reset the release ONLY when the value of the PO increases. Any other change including decrease in value will not reset the release.
    You can use the release user exit. If the PO is in change mode and Save option is selected, then increase the value in the user exit (This does not increase the PO value actually, just fools the release strategy into thinking that the value has increased).
    Try with changeability 6 instead of 4. 4 will not reset the strategy if the PO is outputted (printed, emailed, etc)
    Please refer the note 662993 and  365604
    Regards,
    R.Brahmankar

  • Release Strategy - Reset

    Dear Team,
    My purchase order / PR release strategy should be reset, due to following reasons.
    1. Any changes in Item Text / Header Text
    2. Any changes in PVC / LD clauses & Base dates
    3. Any changes in Retention / Advance %
    4. Changes in Delivery Date
    Could any one pl suggest on this and how to do it.
    Thanks & Regards,
    R.Saravanan

    Hi,
    Put proper release indicator against the release group .
    You can set a control within Config. there is a parameter called as release indicator.
    Follow this IMG path:
    SPRO> Materials Management>Purchasing>Purchase Order>Release Procedure for Purchase Orders>Define Release Procedure for Purchase Orders>Release indicator
    1 Cannot be changed
    2 Changeable, no new determination of strategy
    3 Changeable, new release in case of new strategy
    4 Changeable, new release in case of new strat. or val. change
    5 Changeable, new release if new strategy/outputted
    6 Changeable, new rel. if new strat. or value change/outputted
    Changeable, new release in case of new strategy
    Changeability of purchasing document during/after release which means how the system reacts if an internal or external purchasing document is changed after the start of the release procedure.
    Note that the values 1 to 4 apply to internal purchasing documents (purchase requisitions) and the values 1 bis6 to external purchasing documents.
    So you would need to set this Indicator for the specific release Id. which specifies whether the purchasing document can be processed in or is blocked for follow-on functions.

  • What is the name of the table where Release Strategy changes are maintained

    Dear Friends,
                       Every time I make the changes in the Release Strategy Codes the Signature of the Approver changes in the Output. The problem is that it even changes for the Older PO's which are already approved by some other approver. Is there any way this problem can be sorted out? or can any one give the name of the table which records the changes made in the Release Strategy along with time and date? I will be really thankful if you guys can help me out!

    Hi Chintan,
    I hope you are talking about the release codes, which we attach later on to user Ids and signature means its description. I hope followed correctly.
    In standard system, as and when you change the description of release code at back end, it gets reflected on front end. No matter whether its old or new PO. There is no way out to stop this. Every time you display the purchase order, the release codes checks for description at back end and displayes the same. Still, it should not bother you, as the already released PO dosent get affected for any changes you do at back end in the entire release strategy.
    Beside the tables mentioned by other friends AUSP is the table where all release related entries gets stored.
    I hope it clarifies.
    Regards
    sachin

  • PR Release Strategy tab processor field is not getting displayed

    Hi Experts,
    While creating Purchase Requisition, In the Release Strategy tab processor field is not getting displayed which should be showing the name of the user id which has been configured in the SPRO.
    SPRO--> Rel Proc for PR > Rel Group> Rel Code--> Object type (US) and --> Agent (User id who has to approve the PR).
    release strategy - Release code  -work flow 1
    That processer name is not displaying
    Thanks
    chandoo

    This is the workflow forum.

  • Release strategy for purchase requisition does not kick in

    Hi Gurus!
    I've been struggling with this issue for some weeks now.
    I have set up the release strategy configuration for purchase requisitions with classifications.
    However, if I create a purchase requisition the release functionality is not taken into account by the system.
    See below some more information regarding my configuration:
    1. I've created a new characteristic "REL_PR_GROUP". Status: released, Multiple values, Number of Chars 3, 7 values (TR1, TR2, TR3....TR7), Table name: CEBAN, Field name: EKGRP, Procedure for value assignment set to not ready for input.
    2. I've created a new class: "REL_PR_ANPC". Class type 032, Status: released, Same classification: do not check, Char: "REL_PR_GROUP"
    3. I have one release group "T1", Rel. object 1, OverReqRel is marked, Class: "REL_PR_ANPC"
    4. I have 5 release codes. Grp: T1, Code: 01....05
    5. I have 2 release indicators:
    "R = Released", Rel. for ordering is marked, Changeabil: 4, Value chgs. 100,0
    "X = Blocked",  Changeabil: 4, Value chgs. 100,0
    6. I have 1 release strategy:
    "T1 with Grp T1"
    - one release group, 01 Manager
    - release prerequisites not applicable because of only one release group
    - release status, nothing marked = blocked, 01 marked = released
    - classification, purchasing group is TR1 or TR2 or TR3 or TR4 or TR5 or TR6 or TR7
    I intentionally kept the configuration as simple as possible so I can try to get it working first.
    Now if I create a purchase requisition for an item with release group T1, I would expect the release strategy to be activated. However, this is not the case. I don't see the "release status" tab in the PR, and if I try to relase via ME54 the system says the PR is not relevant for release.
    Could you please assist in getting this working?

    Hi,
    Have you checked in CL30/CL30N if your release strategy is derived successfully?
    See section 3 of Note 365604. A small section of it:
    You can use transaction CL30 search for an object using the data
    of the purchase requisition/purchase order. Here, it is important
    that the object search determines exactly one strategy. If this
    is not the case, this indicates that there are overlapping
    strategies in the system or that the release strategies in
    Customizing do not correspond with those from transaction CL24.
    See the previous point. If the object search returns more than
    one result, the system subsequently determines an incorrect
    release strategy or no release strategy at all.
    If it is derived successfully, next, check the user exit EXIT_SAPLEBND_001 as per Note 371667:
    The following assignment statement has to exist within activated SAP
    enhancements M06B0002 (include zxm06u13) and M06B0005 (include zxm06u31)
    for purchase requisitions:
         E_CEBAN = I_CEBAN.
    Regards,
    Purnima.

Maybe you are looking for

  • Variable input values issue with Portal reports in WAD

    Hi Gurus, We have issue with our reports which are created in WAD and when executed through CRM portal. We are executing the report with some selection criteria by changing default values, and once we get the out put we use SAVEAS option to save the

  • Problem when installing boXIwin_sp3

    Hi, I am trying to install the patch boXIwin_sp3 In installation start good, stop the services. During the backup of the orginal files, the installation stop without any error. Can somebody help me?

  • Creating Oracle service in Oracle 8i Client for Oracle 10g XE

    Hi all We tried Oracle 10g XE on one Machine X - OS Windows XP Professional SP2 , It had earlier Oracle 8i Client. It installed fine. It is wonderful and easy to install. Services started automatic for listner as well as OracleXE. We are able to crea

  • 1099 Reporting - New indicator in RFIDYYWT - Is Recipient ID truncated?

    As a part of the US 1099 Legal changes for 2010 (SAP Note 1535966), there is a new indicator in RFIDYYWT in the country specific selection labeled "Is Recipient ID trun".  Based on the description I thought this indicator was for the IRS option to tr

  • Getting the error during RCU installation

    Hi, I am facing the below error during the installation of RCU.I has given the sys user and the pwd which is working fine from DOSPROMPT.the same when i give in the the configuration during the installation of RCU ,i am getting the below error .Can a