CUTOVER PR PO

1.In our legacy system we donot have any Acct.Assingment field. in PR/PO ,how we should take care will uploading of cutover data
2. Which PR should i take whether all approved ,or pendings also
3.what about PO
rEGARDS
SAM

Hi,
1.In legassy system if there are no consumption PO's you can upload the PR/PO's in SAP as stock one's only.
2.It depends on the company requirement.If company wants the history records of PR's and PO's in SAP from perticular date onwards then you need to load all the PR's and PO's from that date.Or if the company wants only PR's or PO's which are open only then you have to load the PR's or PO's for open quantities (even partial quantities) only.
3.In case of PO's if want the total history of the PO's that you are loading (i.e.GR's done against the PO's and invoices verified against the PO's) then you need to load the PO's for the total quantities. And up load the GR's and invoices against the PO's.
Regards,
Rambhupal reddy

Similar Messages

  • FM Cutover : Open PR, PO

    Hello Experts
    We are planning to Go Live with FM module at the start of fiscal year. As part of Cutover Activity,
    how should open PO, PR and Invoices be treated if they are not to be short closed.
    Do we have to Reconstruct open PO, PR and Invoices using FMN3N, FMN4N etc or it is not required.
    We are using BCS and ECC 6.0
    Please suggest
    Thanks and Regards
    Miten Shah

    Thanks Eli
    a) run FMAF transaction and then again FMAVCREINIT; check if the issue is solved
    Issue didnt get solved
    b) if not, then create a PO with a link to PR and check the data in FMIOI table: is the field VREFBN filled?
    Yes the field VREFBN (Pred doc no.) was filled with PR number
    Interesting thing found that this PR had two line items, when PO made linking with the PR, one line item of PR got reduced by PO(t code me21n) found this info from fmioi table but the second line item of PR was not reduced as it still showed t code as fmn3n.
    Regards
    Miten

  • Plano de Cutover/Credenciamento

    Ola colegas,
    Aqui na nossa empresa ja somos credenciados junto com a SEFAZ-SP pois esta em uso o proprio sistema da SEFAZ para emitir as NFe.  Em aproximadamente 40 dias, estamos entrando em producao com o sistema GRC do SAP.  Gostaria de saber se alguem tem alguma sugestao de como eu deveria proceder com o plano de cutover.  Quais sao os passo que tenho que tomar para habilitar o SAP com o ambiente produtivo da SEFAZ-SP.  No momento o sistema esta funcionando com o ambiente de homologacao da SEFAZ-SP.  Alguem comenta?
    Abs,
    Phil

    Olá Phil,
    do ponto de vista da SEFAZ, creio que é transparente em termos de solucao.
    A SEFAZ-SP nao requer nenhum tipo de cadastramento de solucao (até onde sei), ao contrario da SEFAZ-PR por exemplo.
    Como plano de cutover interno, vai depender de como vc faz o envio das notas do SAP ERP para a solucao externa da SEFAZ.
    É um passo automatizado (e.g. gera um txt que envia pra ele)?. Se sim, o ideal seria definir um horario de baixo volume de faturamento (em geral perto de meia noite, madrugada etc, principalmente no Fim de Semana) para fazer o "switch" desse programa, em producao, q envia os txts para a configuracao standard que vai enviar pro GRC.
    É um passo manual (e.g. usuario gera manualmente a nota na ferramenta externa)? Se sim, vai ser mais uma questao de treinamento dos usuarios a priori, para que no momento do switch, eles estejam alinhados em termos de o que fazer.
    Att.
    Henrique.

  • SAP WM cutover open orders

    While doing cutover activity what should be the status of the Open production order, open purchase order &  open deliveries for sales.
    We are using fixed bin for production staging  so release production order etc it will not create transfer requirement.
    So as per my understanding if I have open production order or purchase order then no issues.
    Also I should not have any open delivery while migrating to wm.
    Kindly confirm your views.

    what do you mean by "as I am using fixed bin in production staging"
    Does this mean that you are not going to take into consideration the BOM quantity required from production order / process order ? or are you going to transfer a fixed quantity every time to the line side irrespective of the qty required by process order / production order

  • Cutover plan

    We have few sales orders with future delivery dates in production system. We are implementing customer collaboration with SNC5.1.
    There are few OPEN SALE  orders in R/3. We want to plan for cutover so how we should plan this.
    Details approach will be appreciated.
    Regards,
    Vaibhav

    you can recreate the orders in SNC, once you have your production system setup with all masterdata and customizing, and PI is up and running, you can send all orders to SNC, and they will be re-created by the Replenishment order confirmation XML interface.

  • Workflow Upgrade 4.6C to ECC6 - manual settings during Cutover

    Hello Guys,
    We are upgrading to ECC 6 from 4.6C  and we are on release 701 & support pack SAPKB70106.
    I would like to know which are the "Manual activities" that needs to done during cutover and WHEN should these should be done (eg. before ECC6 upgade, or after ECC6 upgrade but before config/dev transports, or after config/dev transports).
    I have looked on few SDN threads and found the following info. Please correct me or add extra info if i have missed something:
    1. Configure RFC destination & WF user info in Transaction SWU3.
    2. Run Transaction SWU_OBUF to clear the runtime buffers before users start Testing.
    I assume rest of changes would be imported with transports, but i have read through lot of SDN threads that all custom Workflow definitions needs to be ACTIVATED in each system (DEV - QAS-  PRD)  and custom BOR objects needs be REGENERATED in each system (DEV - QAS-  PRD). Also, do I have manually set the agent assignement for Customer Task as GENERAL TASK in each system?  Are above stated 3 steps needs to be manually done in each system or transports take care of them ? I am bit confused. Could anybody please advise me regarding the Manual Task/activities that needs to done in each system during cutover during WF upgrade from 4.6 C to ECC6.
    Thanks for posting excellent stuff regarding the Workflow Upgrades on SDN. It really helped me in resolving most of my issues.
    Thanks in advance
    Kind Regards
    Sam

    Helli Viji,
    Thanks for the information. I still have some doubts.
    Yes , as you have mentioned there are many other mandatory settings in Transaction SWU3 that needs to be maintained in each system. I hope these settings are imported with the Customizing tranport request created in DEV or Do we have to maintain these manually just in case of Upgrade.
    For transporting the Agent assignment from one system to another, can we use Transaction RE_RHMOVE30 ? Or this functionality do not works when upgrading to ECC 6 from 4.6 C.
    Is there any other activity I am missing that needs to done during Cutover when upgrading from 4.6C to ECC 6 with regard to Workflows.
    Thanks
    Regards
    Sam.

  • Cutover approach - new fields added to existing DataSources / DSOs / Cubes

    My current project has been phased across multiple releases. The phase 1 go-live was a few months ago and there is already a reasonable amount of data in the production environment. We will soon cutover from our QA to production environment. Some of our developments involve the addition of new fields (not key fields) to datasources.
    For existing delta-enabled DataSource we are going to adopt the following approach:
    1- Source system transports deployed
    2- DataSources replicated in BI system
    3- Before InfoObject / InfoProvider transports are sent we will delete data
    4- The INIT flag will be deleted
    5- Full Repair loads will be executed
    6- INIT without Data Transfer will be executed
    For new delta-enabled DataSources we are going to:
    1- Source system transports deployed
    2- DataSources replicated in BI system
    3- INIT loads executed
    4- DELTA loads executed
    Does this approach seem correct? Does this avoid the risk of losing any data? Will it lead to delta loads functioning correctly? Will we get data loaded in the new fields for existing records?

    One approach that we used for getting around having to delete and re-fill setup tables (which, by the way can be done without downtime - I wrote a blog on that about 1 year or more ago), is to create generic DataSources (some with generic deltas) for the additional data, ensuring that we had the keys for the target InfoProviders in the DataSource and then used those as an additional transformed source to the InfoProviders.
    Example:
    Was
    2LIS_XX_XXX -> 0XX_DSXX
    Now
    2LIS_XX_XXX  \
                              >    0XX_DSXX (with appended columns)
    ZLIS_XX_XXX /
    Edited by: Dennis Scoville on Oct 13, 2010 10:28 AM

  • Vendor cutover / open items upload

    Dear SAP Gurus,
    I am going to upload vendor open items / cutover data on the server before GOLIVE. I just need to know whether the open items are to be uploaded :
    inclusive of the TDS i.e the Gross amount
    OR
    It has to be without the TDS amount and the TDS amount is uploaded seperately.
    Regards
    Nikit

    Dear Chintan,
    Thanks a lot for your prompt reply. But tell me one thing, that if I upload the balances w/o the TDS amount what posting keys are to be used. If i use keys 31 for vendor and 40 for GL upload account and upload through F-02, then the system takes the TDS rates from the vendor master and calculates TDS on it and post to the TDS payable GL accounts.
    so for example if the original entry is
    Expense a/c dr...100
    to vendor a/c .......90
    to tds pbl /ac.........10
    and I upload only with the net vendor amount of 90 the system will again post
    GL upload a/c dr.......90
    to vendor a/c ...........81
    to TDS pbl /ac..........9.
    So this will be double calculation of TDS.
    So could you kindly let me know what is the proper procedure to upload and with what t.code and posting keys?
    Regards
    Nikit

  • SAP WM Cutover

    It is intended to implement SAP WM module at my company.
    For the cut-over activities, is it possible to create a warehouse on the existing storage location with material stock?
    i intend to adopt the following procedure
    - issue the existing stock of all materials to a cost center
    - send the transport for WM onto the PRD server
    - extend WM views on the target materials
    - create the storage bins for material placement in the system
    - reverse the material issue document to bring the stock back
    - place it in the relevant storage bin
    Experts, I would like to inquire if the above mentioned procedure is ok?

    It is one of the possible solutions for cutover.
    You will need to create settings in WM/IM interface for movement type - reversal of post to cost center in order to tell WM what to do with the materials being received in warehouse by that movement type.
    Also, your storage location must be put under warehouse number (assign SLoc to WhNum) after cost center issue and before the cost center issue reversal.
    So the answer is yes, but you will only need to change one thing in your approach, you need to deploy WM settings on production server (release requests with all the WM settings) AFTER you post the mat.doc. for cost center.
    Although it is possible to do what you want, it is a practice to use a new storage location for WM. But your solution is perfectly valid if you want to keep your SLoc.
    Also, most of the time we can use movement types 561 and 562 for the inital stock upload, or move the stock to a new fictional SLoc and then after deploying WM settings on PROD we just post Sloc to Sloc - movement type 311. So basically any approach that suits you best is OK to go with.
    Hope this helps.

  • Cutover Strategy

    Hello all,
    Can any body explain me about cutover strategy,
    the scenario is my client is paying full advance payment against PO  and but recived half material so PO is open . How we can expalin to client to prepare cutover plan startegy to prepare cutover data.
    Suggest.

    Hi ,
    Cutover strategy in SAP implementation or any other implementation is client specific . It depends on organisation data load strategies .
    as example , in simple words for MDM it means that after cutover - all data will be used of MDM and not legacy systems . for central master data scnerio ; Data before cutover date will be maintained in all systems and after cutover date , it will be maintained in MDM only .
    Hope this clarfies your Query .
    -Annika .

  • How to Upload WIP Production orders in production during Cutover.

    How to Upload the Open Production orders in production system during cutover activities.
    my client is having 1000 open production order(WIP), during cutover activies how to upload this in production.
    Please guide me
    Regards
    Sunil Patil.

    Hi,
    I somewhat agree with what Raj has to say. Something which is already in process how can that be uploaded, how can one compensate for the time which has been consumed in the production activity.
    I hope Rupesh Brahamakar sir would throw light on this issue, as most of us are under the dillema at the time of Cut-Over activity.
    Sir, hoping your valueable inputs.
    Regards,
    Harris

  • Difference Between Phased Migration and Parallel-cutover and which is better considering Roll-back if something unexpected occurs

    Difference Between Phased Migration and Parallel-cutover and whcih is better considering Roll-back if something unexpected occurs
    Regards
    Sumit

    For what application and going from which version to which?
    Chris

  • Details on Data cutover activities during merger of 2 company codes

    Hi all,
    Basically we have 2 companies which will be merged to one. what would be
    the data cutover activities (MM perspective) during merger?
    May I know more details (particularly transaction details) on
    Inventory upload,
    physical inventories and value adjustments,
    other open items/ balances in financial accounting,
    Open PO and PR
    Thanks in advance
    Regards
    JJ

    Hi
    There are lot of issues that you need to take care of:
    1. is there any relation bwteeen the two company codes before merger. have they done any transactions between them? If yes, what wewould be the accounting treatment for the same. Would it be transferred at cost or Cost+Price (Transfer Price)
    2. If you are in India, there would be effects of taxation like excise and vat calculations
    3. One of the most important issue, is that of the new fiscal year. What strategy would you follow for the merged entity? In Sap, changing a fiscal year is a critical issue. Request you to refer SAP Help for the same. There are notes available for the same
    4. What would be the strategy for Asset valuations? Are there different asset valuation procedures followed in the two company codes?
    Thanks & regards
    Sanil K Bhandari

  • Cycle Count Cutover

    The company I'm working with has been doing annual "wall-to-wall" Physical Inventory counts. They now want to cutover to Cycle Counting and have 20,000 materials that they manage in inventory. The last count was performed in October of 2006. So the concern is that if they turn on cycle counting, it will create count docs for all materials. They want a way of staggering the docs automatically so that the warehouse is not hit all at once. I mentioned that the problem would be lessened if they rolled out cycle counting right after the next wall-to-wall, but their setup is as follows:
    A is counted monthly
    B is counted bi-monthly
    C is counted semi-annually
    So, they would also end up with all of their Cs on the same day (6 months after the last wall-to-wall). They will have to figure out a way to stagger the counts so that they get a manageable daily volume of count documents.  Does anyone have suggestions as to how to cutover in a reasonable way?
    Thanks,
    Richard

    Hello Richard,
    They can use Flot time functionality which will allow them to create the inventory document within flot time period. for ex. if you are defining flot time as 5 days then still you have chance to do inventory count for due material in 5 days, if dont count in this 5 day then that material/bin will pushed in the next cycle count period.
    Now in initial period they need to create inventory document manually as per their capability.
    Once they will be on regular basis then they can set batch job for it.
    Hope this helps.
    Regards
    Arif Mansuri

  • Travel Management - Cutover mileage

    We converting one of our Companies to SAP.  We will be using travel management for expenses, and employees are entitled to increased rates when they hit a certain mileage.
    As we will be going live 10 months into the tax year, we need to cut over the mileage values for each employee.
    How do we tell the system what employees b/fwd mileage is so they will get the currect amount based on their cumulative mileage for the year?
    Thanks
    Graham

    Hi Graham,
    I understand this is an old ticket but i am facing the same problem
    can you please mention how you managed to enter the cutover mileages for the current fiscal year?
    Best Regards,
    Chrissy

Maybe you are looking for