Configuration Questions Flashcards
What is your vendor evaluation experience?
You set up vendor evaluation to help gauge vendor performance on criteria customized in the system. So as to pick the best vendors for the business and to use their evaluation results in negotiations. In IMG, these are the steps to set up Vendor evaluation: 1- Setup weighting keys ((1)equal weighting or (2)unequal weighting) vendor evaluation-> weighting keys. 2- Set up Criteria upon which the vendors will be evaluated, their weighting factors and for each Purch Org, whether they will be automatically, manually or semi automatically scored. MM->V.E.-> Criteria. 3. Define the V.E. settings for each P. Org, things like what span of data is to be used in the evaluation, what is the max score achievable for each criterion etc. MM->V.E.-> Maintain P. Org data. 4- Define the list corresponding to the criteria that will be used in the evaluation. MM-> V.E.-> Define Scope of list.
What do you know about release strategy?
We set up release strategy to replace the manual use of signature to authorize purchasing document while maintaining dual control. The configuration in the system goes as follow: 1. Create characteristics 2-Create Class and Assign characteristics to class 3- Create Release group and assign it to class. 4- Create release codes and assign them to release group. 5- Create release indicators. 6- Create the release strategy (defining which codes and in which order will be needed to release the documents). Only PR can be release without classification (at header level and individual line items) POs and other are with classification (at header level only). tr:OMGQ
Tell me about your support experience
As a support resource with my most current employer, I helped users through WebEx, Over the phone and in person. I averaged about 20 tickets a day, and we had 3 days to solve each tickets submitted by users. I would generally get access to outstanding tickets through the queue on Heat. The number of of tickets, or service request handled generally varies depending or the company and its size. We handled service request at my lead’s discretion, generally following the service level agreement or expediting it if it were urgent.Service request were generally handle on the same day every week ( on Mondays and Wednesdays). Many of the tickets we handled were from users not understanding the system so I had to walk them through the transactions they were unable to perform, or users trying to perform a process not yet configured in the system, Or a configuration simply had not been made in the system. I kept track of my tickets through Heat, previously have used OSS notes and also my personal log.
Tell me about pricing determination
Well you set pricing determination in the system to arrive at a net price you pay after having applied different conditions such as discount freight and surcharges to the gross price provided by the vendor. You customize your system for those various conditions. First, in the system you have to check the dependencies under which conditions are arrived at, then bring those dependencies in line with the criteria for price determination in SAP. After you’ve done that, in customizing (1) you define condition tables (In a condition table, you specify the combination of fields for which you can create condition records), (2) then define the access sequence (The search strategy by which the system searches for valid condition records of a certain condition type), (3) then define the condition types (such as discounts, freight that are stored in condition records), (4) then define the calculation schema (used here to calculate the condition types discounts, taxes etc), (5) then you define the schema group (grouping together P. Org that use the same calculation schema), (6) define schema determination (you assign certain transactions and processes to a calculation schema, specifying the cases in which a certain schema is used).
Tell me about you testing experience:
At multiple stops,I have used HPQC to perform my testing tasks. Whether I was performing Unit testing (testing individual transactions)in the development client to establish a baseline SAP functionality. And then string testing, where you link elements of related SAP functionality together and ensure that the pieces work well together. Then in the quality assurance client, Integration testing (checking that transactions properly work across modules), and the User acceptance testing (after transport from development client to QA client to ensure it meets Super users requirements???
What is your experience with EDI?
Well, the basic of EDI in SAp is that the system sends EDI messages (of business docs such as a PO) in IDoc format to an EDI subsystem which converts it to a universal format such as ANSI/X12 to facilitate communication with non-SAP systems. ??
How did you gather requirements?
We organized requirement workshops to gather all the data from the client’s staff assigned to the project.
Tell me about functional specs you’ve created:
Well, functional specs are documents that describe in details what the desired functionality for a set transaction in SAP will be (for example, what exactly will happen in the system when you execute transaction XK01). It is crucial for a smooth execution of SAP implementation that in my role as a functional rep, I write functional specifications that ensures that the people that handle the development process understand exactly the product feature requirements, and that the information I provide in my functional specs are clear and unambiguous for the technical consultants. A functional spec must include items such as tables, field names, test data if available. For GAPs for example, the spec should clearly describe whether what is needed is a report, an interface, conversion, an enhancement or a form and provide precise details to be included in the object. At Medimmune for example, I wrote specs for POs, explaining in details to the ABAPer everything that should be present in the design of the object for it to meet clent’s expectations. I would generally run specs through the client for approval.
What exactly did you do during the Blueprint phase?
I conducted requirement workshops during which I had to carefully write notes and compiled documents pertaining to the AS-IS and I helped prepare the QADB (questions and answer data base) questionaire. And with the answers from the client, I mapped the AS-IS and TO-BE process in flow process mapping.
Tell me about your RICEF experience:
Well, the extent of my experience with RICEF, was to describe the way I wanted a GAP in the system to be filled, whether as a report, an interface (EDI or ALE for example), a conversion object (Data upload from legacy system in flat files format to SAP system is done via Conversion Objects.. using LSMW), Enhancement (USER EXIT and BADI), and Forms (Smartforms and SAP Scripts).
What’s your experience with User Exit and BADI?
The extent of my experience with these is in my writing functional specs requesting a GAP be filled through enhancements. ?? User exits were used to add functionality to SAP. For example, if the client has an existing software that performs a specialized task not available in SAP, You can use a user exit to connect SAP to the external software.
Tell me about some processes you’ve been a part of:
Well, I was a part of the Purchasing process, IM, and raw material preparation among others.
Tell me about designs you’ve performed
?? I’ve designed data requirements, data dependencies and data requirements.
What do you do when you identify a Gap:
?You have to determine whether the Gap can be closed by customizing the software, or by a workaround, or if the Gap simply cannot be closed. Generally, I have to determine whether a report of form, an interface, a conversion or an enhancement is what’s needed to close the Gap.
How did you keep track of your documentation?
I’ve mostly used Solution Manager but, I’ve also used BPML.
