Auto Creation of new requisitions based on a list of items

Auto Creation of new requisitions based on a list of items
We are starting discussions to determine how we could auto-create requisitions based on a list of servers in order to perform periodic health checks.
One approach we thought about was creating one service request that could spawn multiple requests, again based on a list and using a set schedule (weekly, monthly, quarterly, yearly, etc.)
Has anyone implemented this and can provide some guidance/tips?

You can check this article for more references on how to use sp_helptext object_name stored procedure:
http://blog.sqlauthority.com/2007/05/25/sql-server-stored-procedure-to-display-code-text-of-stored-procedure-trigger-view-or-object/
I also suggest trying commercial tools to sync and compare the stored procedures between two databases. We used
ApexSQL Diff, but I've also heard some good things about
Devart's tools.

Similar Messages

Auto Creation of Purchase Requisition at Contract Level

Hi All,
I am having business requirement for creation of purchase requisition at contract level for third party Products.
Brief Business requirement
My client is in trading business of telecom product. They are sourcing product from different-different vendors and some of the product is also supplied by him self. As a business practice the system will automatically create an Installed base as per structured by business owner once delivered the product to end customer and also assigned warranty norms.
Once warranty is over then customer will called for contract since at the time sailing the product warranty will be liability of the company which in terns had some mutual contract with supplier (back to back replacement).
But once the same will come under service agreement/contract on that time they want installed base selection of components should had a functionality to segregate component based on vendor because they want to calculate % margin based on net sale value of the product.(e.g 10% of net sale Value 10,0000) not only that they also wants based on that system should automatically create Purchase requisition so that logistic department will take care of third party agreement part.
If any body come across with such kind of business scenario. Please share the proposed solution.
Regards
Neeraj

Hello,
I noticed that this question had status answered. We have the same requirement.... how did you resolve this?
Best Regards
Kristof

Creation of new schema based on old schema

Hi,
I want to create a new schema with the different name based on the objects of the old schema.
For that I created a new user and schema and then imported the dump file into it. But problem is
I am not getting the external table structure, except that other objects are coming into new schema.
Ex: Old schema name "ABC", new schema name "XYZ"
ABC contains 15 normal tables, 3 external table, 2 procedure, 2 functions and 2 packages.
I want to have all these objects in this new schema.
Help me regarding this matter.
Thanks in advance,
Narayan

Hi,
Thanks Seenu,
So i have to clasify based on Maintenance activity types. If there are activities like repair, shutdown, testing etc. then i will have to create work center based on that?
So i can create some activities like, Modification, Repair, standby, waiting etc and assign work center for each?
Here we are following 4 maintenance planning preventive, predictive, breakdown & shutdown so is it possible to make 4 work center according to those.
please correct me if i m wrong. i really have no much idea in this. any help or suggestions will be appreciated.
Thanks in advance
Ramya

Auto Creation of Dispute Case based on dunning level

Dear All
We want to create the dispute case automatically using T.Code FDM_Auto_Create. We want to default the title as dunning level + External reference. We know the BADI for this but how to check which dispute cases are created automatically due to dunning level.
Thanks and Best Regards
Farhan Qaiser

Hi Farhan,
I presume you are creating your disputes against open items, and not incoming payments.
If this is correct, the dunning level field is part of the selection parameter.
Are you planning on disputing all open items, that have a specific Dunning level, if that is the case you can include this in your selection parameter.

Automatic PO creation - only for PRs based on catalog SRM/EBP items

Dear Experts,
i am facing the following question w.r.t. automatic PO creation:
Is it possible to have automatic PO creation in R/3 only for those purchase requisition items, that are based on shopping cart/EBP/SRM items that are from a third party punch out catalog?
The idea is, that the requisitioner on the SRM EBP side shops in a catalog. Once the the SC is approved and the purchase requisition is created in the R/3 system, automatically a PO should be created based on that PReq. This would save the time for the buyer, who do not need to pay attention to this document, because the purchase from the catalog guarantees the buyer, that the already pre-agreed conditions are getting applied.
But PReqs that are based on Free Text shopping cart EBP items must not be taken into account for the automatic PO creation.
Is there a way to distinguish between the catalog-based and the non-catalog based PReq positions?
Thank you.

Auto PO transaction ME59N comes with huge selection crieteria. If you can distinguish between catelog vs non catalog requisition then it very easy to set up variant to filter non catalog based requistion. you can also think about ehnacement of polulating text fields like Requisitioner or Requirement tracking number with unque idetifier in case of non catalog based PR then you can set variant to filter out those requistions..

Creation of new field in RFX screen and populating item details

Hi Experts,
I have to create a new button in "Create RFX " screen where it should procure the shopping cart details and it should populate in table in RFX screen.
Shopping cart number should be entered in this screen. Set up for this input field is already done.Now i added an button GO.This one should retrieve the shopping cart details of entered shopping cart number and populate in the table present in this screen.
Procedure
1.Procure shopping cart details by calling the function module "bbp_pd_sc_getdetail".
I am strucked after this.How to proceed further as i have tried different procedures.
Please help if any idea on this

thanks for reply
I have did same thing but in input parameter of bado i am getting the shoping cart GUID . form which how i can get the Bid detail.
and other part is I need to send data by extension this this how we can do ?
do we need to write code in backend also and need to create custom field in backend PO table.
Thaks for reply

Auto creation of Groups

Has anyone configured auto creation of dynamic groups based on lets say a new dept. created in HR's connected data source. Then have the criteria of that new Dept. be in the new group, all hands off??? Custom workflows in the FIM Portal is what I'm thinking,
is that possible???
Thanks

Hi,
the script is currently just a "planning" so there is none.
But it will be similar to my scripts I use to modify object in portal from this wiki article:
http://social.technet.microsoft.com/wiki/contents/articles/19615.fim-2010-r2-how-to-manage-group-membership-from-the-user-ui.aspx
In this script i modify group objects on changes on user attributes, you can modify this to your needs an create groups on create requests of groups.
Regards
Peter
Peter Stapf - ExpertCircle GmbH - My blog:
JustIDM.wordpress.com

How to approve creation of new identities

Hi,
I have created an approval process for the creation of new identities based on the how-to-guide for role approvals.
My idea is to determine all approvers in a script which gets the entry reference as parameter from ToIdentityStore pass.
However, for some reason, the entry reference is empty.
Any ideas what am I doing wrong?
Here is the script:
function nsn_getNSNApproversFromCompanyAddress(Par){
var entryReference = Par;
uErrMsg(1, "entry reference: " + entryReference);
var idStore = uGetIDStore();
var companyAddress = uIS_GetValue(entryReference, idStore, "MXREF_MX_COMPANY_ADDRESS");
uErrMsg(1, "company address: " + companyAddress);
var nsnApprovers = uIS_nGetValues(companyAddress, "MX_APPROVERS");
if (nsnApprovers.indexOf("!ERROR")>= 0)
     uErrMsg(1, "ERROR: " + nsnApprovers);
return nsnApprovers;
uErrMsg(1, "entry reference: " + entryReference) does not print out any value for entry reference
And here is the destination tab content of the ToIdentityStorePass:
MSKEYVALUE     %MSKEYVALUE%
MX_APPROVERS     $FUNCTION.nsn_getNSNApproversFromCompanyAddress(%MX_ENTRY_REFERENCE%)$$
Thanks in advance for your help,
Elmar

Hm, from what the error output message tells me it looks like MX_ENTRY_REFERENCE does not contain ANY value.
uErrMsg(1, "entry reference: " + entryReference); generates this output: 'entry reference: '
May this be due to the fact that this is a creation process and the identity to be created is not yet stored anywhere? If so, what would be the correct way to implement an approval process for identity creation?
In the destination tab, MX_PENDING_VALUE is defined, as in the how-to-guide manager approval example.
Thanks & Br,
Elmar

MRP - Auto creation of del schedule lines based on planned delivery time

Hi,
We have activated MRP (type PD) where Purchase requiesition is auto created by system for requirement quantity. We require to optimize delivery schedule in such a way that entire PR quantity is broken into various delivery schedule based on planned delivery time and requirement. Scenario can be further explained with following example.
Material Requirement for a month is say 1,25,000 units
Closing Stock say 25,000 units
PR Generated by system for 1,00,000 units. The entire quantity is schdulled with only one delivery schedule line as per planned delivery time.
The requirement is to generate multiple delivery schedule lines automatically in Purchase requisition based on planned delivery time so that Purchase orders can be placed with system generated delivery schedule lines.
How can it be achieved ?
Regards,
Nirav Kinkhabwala

Nirav,
This subject has been discussed repeatedly in this and other forums. I must assume that you overlooked the rules of engagement, which state that you should first search the forums and other public sites, before posting questions here.
Standard SAP MRP cannot be made to generate multiple items in a Purchase requisition. The functionality you seek is usually achieved when converting purchase reqs to Purchase orders, where many single purchase reqs can be adopted into a single Purchase order.
You also might want to investigate use of Vendor Scheduling agreements.
Best Regards,
DB49

Auto PO creation using purchase requisition

Hi,
I have tried the following steps for auto PO creation using purchase requisition.
i. Maintain Auto PO in Material master Purchasing view
ii. Select Automatic purchase order in Vendor master- Purchase data
iii. Maintain info-record
iv. Create PR through ME51
v. enable source determination during creation of PR
vi. Execute using ME59N
But Auto PO is creating with the same document type (e.g NB) which is used while creating purchase requisition (e.g NB). Following steps have done in SPRO.
1. SPRO - MM - Purchasing - purchase requisition - define document type
a. NB- PR document type LINK TO DI01- PO document type
2. SPRO - MM - Purchasing - Purchase order - Define document type
a. DI01- PO document type LINK TO NB- PR document type
3. There is no linking from NB - NB & DI01 - DI01 but still it is creating auto PO with document type NB iif requisition has been created with document type NB.
Please suggest on this . waiting for ur quick response.
Thanks...
ARATI.
Thanks!
Arati.
Edited by: Rakesh Gupta on Aug 20, 2009 11:00 AM

Hi
Please check the below thread
PR to PO via ME59 -Doc type issue
Thanks/karthik

BAdI for during new requisition creation in e-recruiting

Hi,
How to check what BAdI being called when new requisition created in e-recruiting?
Given BAdI HRRCF00_GET_ASSIGNED_SGR to add support group when new requisition is created.
But the BAdI was not triggered after i created new requisition in e-recruiting.
Greatly appreciate for any helps/comments.
Thanks.

E-Recruiting specific BADIs are not called in functions which are built in the ABA.
E-Recruiting BADIs are just used in E-Recruiting functions and classes.
The support team group BADI belongs to the new Manager process implemented in the new MSS scenario.
The easiest way to assign a support team to a requisition automatically, is by implementing a workflow, which is triggered by ERC_OBJECT ObjectCreated.
This will automatically assign anything you want. But in this case you will have the problem, that you can just assign a generic support group to a requisition, because no data was entered before.
Another possibility is enhancing a specific BSP-Application by using the enhancement framework. Post-Exists on class methods might help you. But you need to identify that specific BSP application, which is called during the specific save you need in order to have the right criteria provided.
Regards.

Auto selection of PO type based on PR type

Dear Gurus,
I am placing question for the first time, please guide.
While using ME21N PO type should be automatically selected based on PR type when PR number is refered while creating PO.
I have configured "Link purchase requisition - document type" through Define Document type .
Above conf. has triggerd an error msg. in ME21N (useful to some extent).
But we want system to automatically select PO type based on PR type ( when PR No. refered in PO ).
Thanks in advance
Rammohan

Dear sir,
Auto creation of PO will not workout, since manual creation only allowed. Only auto PO type selection is required.
Even PO type select in in SU3 & personal setting are made blank.
Thanks
Rammohan

CUP - Issue regarding creation of New SAP ID in CUP.

System : SAP GRC 5.3 SP 12..
We have requirement where in we need to design a workflow for creation of New SAP ID.
The Naming convention followed for SAP ID is FIRST LETTER of FIRST NAME and LAST NAME with maximum 8 characters.
For Eg
JOHN SMITH would have SAP ID as JSMITH
JERRY SMITH would have SAP ID as JSMITH01
The requirement here is when user fill the REQUEST FORM for NEW User ID there is field where in the requestor need to put the desired SAP ID,
Can a validation be set OR Logic be written so that user can put the SAP ID as per the naming convention..?
Also , any other solution as to how the situtation can be handled in CUP...
Regards.
Ajit

Hi Ajit,
Yes, you can maintain the user ID in the Active Directory. User id will be now auto populated in the request form, from Active Directory when we data Source is LDAP -Actice directory. So when user login to end user form to create a request, It's all information( user details + manager details ) will fetched from Active Directory.
It is not possible to change userid in later stage of approval in the request.
You can have security as final stage and guide them to create user manually as per naming convention.
Make auto provisioning OFF in CUP
Kind Regards,
Srinivasan

Auto creation of po from shopping cart

hai gurus
Iam in SRM 5.o,CLASSIC Scenario.
In configuration for "Auto creation of po from shopping cart"i have given "purchase order if item data complete,otherwise PR"in SPRO>SRM>srmserver>cross application basic settings>Define objects in Backend(PR,PO,requisition)
So shopping cart is been created with PUR org,PUR GROUP,Vendor tax code,account assignment etc,but purchase requisition is created and not purchase order.Is there any settings left over
Thanks in Advance
chandra

Hello Chandra,
You also could use the PR (in ECC) and try to convert it into a PO (ME57). If it asks you for some additional data (e.g. vendor, price, ..) this might indicate, that it is missing in the SC.
Also, you could try and debug transaction ME59 (auto PO creation) to see, what's missing/checked.
Good luck.
Franz

Creation of new Sales order

Hi,
       While creating a new Sales Order(tcode VA01) depending on the material, Item category will be generated and depending on the Item category purchase requisition screen(ME51n) will be automatically opened and PR will be created.
Now to automate this process, BAPI_SALESORDER_CREATEFROMDAT1 will be called to create the sales order. But the requirement is that we need to pass Requisitioner and Vendor to the BAPI for creation of PR.
But in this BAPI there is no option/field to pass Requisitioner and Vendor. So is there any other BAPI/Function Module where a new Sales order is created and also we can pass Requisitioner and Vendor required for creation of new PR.

REPORT ZSALESORDER.
Parameters
Sales document type
SELECTION-SCREEN BEGIN OF LINE.
SELECTION-SCREEN COMMENT 2(20) v_text FOR FIELD p_auart.
PARAMETERS: p_auart TYPE auart OBLIGATORY.
SELECTION-SCREEN END OF LINE.
Sales organization
SELECTION-SCREEN BEGIN OF LINE.
SELECTION-SCREEN COMMENT 2(20) v_text1 FOR FIELD p_vkorg.
PARAMETERS: p_vkorg TYPE vkorg OBLIGATORY.
SELECTION-SCREEN END OF LINE.
Distribution channel
SELECTION-SCREEN BEGIN OF LINE.
SELECTION-SCREEN COMMENT 2(20) v_text2 FOR FIELD p_vtweg.
PARAMETERS: p_vtweg TYPE vtweg OBLIGATORY.
SELECTION-SCREEN END OF LINE.
Division.
SELECTION-SCREEN BEGIN OF LINE.
SELECTION-SCREEN COMMENT 2(20) v_text3 FOR FIELD p_spart.
PARAMETERS: p_spart TYPE spart OBLIGATORY.
SELECTION-SCREEN END OF LINE.
SKIP 1.
Sold-to
SELECTION-SCREEN BEGIN OF LINE.
SELECTION-SCREEN COMMENT 2(20) v_text4 FOR FIELD p_sold.
PARAMETERS: p_sold TYPE kunnr OBLIGATORY.
SELECTION-SCREEN END OF LINE.
Ship-to
SELECTION-SCREEN BEGIN OF LINE.
SELECTION-SCREEN COMMENT 2(20) v_text5 FOR FIELD p_ship.
PARAMETERS: p_ship TYPE kunnr OBLIGATORY.
SELECTION-SCREEN END OF LINE.
SKIP 1.
Material
SELECTION-SCREEN BEGIN OF LINE.
SELECTION-SCREEN COMMENT 2(20) v_text6 FOR FIELD p_matnr.
PARAMETERS: p_matnr TYPE matnr   OBLIGATORY.
SELECTION-SCREEN END OF LINE.
Quantity.
SELECTION-SCREEN BEGIN OF LINE.
SELECTION-SCREEN COMMENT 2(20) v_text7 FOR FIELD p_menge.
PARAMETERS: p_menge TYPE kwmeng OBLIGATORY.
SELECTION-SCREEN END OF LINE.
Plant
SELECTION-SCREEN BEGIN OF LINE.
SELECTION-SCREEN COMMENT 2(20) v_text9 FOR FIELD p_plant.
PARAMETERS: p_plant TYPE werks_d .
SELECTION-SCREEN END OF LINE.
Complete Deliver
SELECTION-SCREEN BEGIN OF LINE.
SELECTION-SCREEN COMMENT 2(20) v_text10 FOR FIELD p_autlf.
PARAMETERS: p_autlf TYPE autlf DEFAULT 'X'.
SELECTION-SCREEN END OF LINE.
Data declarations.
DATA: v_vbeln            LIKE vbak-vbeln.
DATA: header             LIKE bapisdhead1.
DATA: headerx            LIKE bapisdhead1x.
DATA: item               LIKE bapisditem OCCURS 0 WITH HEADER LINE.
DATA: itemx              LIKE bapisditemx OCCURS 0 WITH HEADER LINE.
DATA: partner            LIKE bapipartnr OCCURS 0 WITH HEADER LINE.
DATA: return             LIKE bapiret2    OCCURS 0 WITH HEADER LINE.
DATA: lt_schedules_inx   TYPE STANDARD TABLE OF bapischdlx
                         WITH HEADER LINE.
DATA: lt_schedules_in    TYPE STANDARD TABLE OF bapischdl
                         WITH HEADER LINE.
DATA: lt_schedules_ink    TYPE STANDARD TABLE OF bapisdhead1
                         WITH HEADER LINE.
Initialization.
INITIALIZATION.
v_text   = 'Order type'.
v_text1 = 'Sales Org'.
v_text2 = 'Distribution channel'.
v_text3 = 'Division'.
v_text4 = 'Sold-to'.
v_text5 = 'Ship-to'.
v_text6 = 'Material'.
v_text7 = 'Quantity'.
v_text9 = 'Plant'.
v_text10 = 'Complete delivery'.
Start-of-selection.
START-OF-SELECTION.
Header data
Sales document type
header-doc_type = p_auart.
headerx-doc_type = 'X'.
Sales organization
header-sales_org = p_vkorg.
headerx-sales_org = 'X'.
Distribution channel
header-distr_chan = p_vtweg.
headerx-distr_chan = 'X'.
Division
header-division = p_spart.
headerx-division = 'X'.
headerx-updateflag = 'I'.
*Complete delivery
    header-COMPL_DLV = p_autlf.
    header-COMPL_DLV = 'X'.
Partner data
Sold to
partner-partn_role = 'AG'.
partner-partn_numb = p_sold.
APPEND partner.
Ship to
partner-partn_role = 'WE'.
partner-partn_numb = p_ship.
APPEND partner.
ITEM DATA
itemx-updateflag = 'I'.
Line item number.
item-itm_number = '000010'.
itemx-itm_number = 'X'.
Material
item-material = p_matnr.
itemx-material = 'X'.
Plant
item-plant    = p_plant.
itemx-plant   = 'X'.
Quantity
item-target_qty = p_menge.
itemx-target_qty = 'X'.
item category
itemx-ITEM_CATEG = 'X'.
APPEND item.
APPEND itemx.
ITEM DATA
itemx-updateflag = 'I'.
Line item number.
item-itm_number = '000020'.
itemx-itm_number = 'X'.
Material
item-material = p_matnr.
itemx-material = 'X'.
Plant
item-plant    = p_plant.
itemx-plant   = 'X'.
Quantity
item-target_qty = p_menge.
itemx-target_qty = 'X'.
APPEND item.
APPEND itemx.
Fill schedule lines
lt_schedules_in-itm_number = '000010'.
lt_schedules_in-sched_line = '0001'.
lt_schedules_in-req_qty    = p_menge.
APPEND lt_schedules_in.
Fill schedule line flags
lt_schedules_inx-itm_number = '000010'.
lt_schedules_inx-sched_line = '0001'.
lt_schedules_inx-updateflag = 'X'.
lt_schedules_inx-req_qty     = 'X'.
APPEND lt_schedules_inx.
Fill schedule lines
lt_schedules_in-itm_number = '000020'.
lt_schedules_in-sched_line = '0001'.
lt_schedules_in-req_qty    = p_menge.
APPEND lt_schedules_in.
Fill schedule line flags
lt_schedules_inx-itm_number = '000020'.
lt_schedules_inx-sched_line = '0001'.
lt_schedules_inx-updateflag = 'X'.
lt_schedules_inx-req_qty     = 'X'.
APPEND lt_schedules_inx.
Call the BAPI to create the sales order.
CALL FUNCTION 'BAPI_SALESDOCU_CREATEFROMDATA1'
       EXPORTING
            sales_header_in     = header
            sales_header_inx    = headerx
       IMPORTING
            salesdocument_ex    = v_vbeln
       TABLES
            return              = return
            sales_items_in      = item
            sales_items_inx     = itemx
            sales_schedules_in = lt_schedules_in
            sales_schedules_inx = lt_schedules_inx
            sales_partners      = partner.
Check the return table.
LOOP AT return WHERE type = 'E' OR type = 'A'.
    EXIT.
ENDLOOP.
IF sy-subrc = 0.
    WRITE: / 'Error in creating document'.
ELSE.
Commit the work.
    COMMIT WORK AND WAIT.
    WRITE: / 'Document ', v_vbeln, ' created'.
ENDIF.

Auto Creation of new requisitions based on a list of items

Similar Messages

Maybe you are looking for