Tickets related to business process

47.Question: Explain STO Inter process?

Answer: Inter STO is like transfer of goods between two plants with different company codes and at this time billing will happen and accounting documents gets posted.

Here the material should be maintained in both the plants with sales view and it will be worked by MM and SD consultant.

Backend settings:

 we need to maintain the customer code for the receiving plants and sales organization with receiving plants.

Maintain delivery type and checking rule- delivery type is NLCC

Now maintain document type with supplying plant and receiving plant.

After all these settings, shipping tab will popup and SD team will do OBD and wrt that PGI will be done and billing, lastly MIGO will be done for the PO.

48.Question: Explain Invoice, credit memo and subsequent adjustment.

Answer: Invoice: Invoice is a document where we will take reference for payment of goods that we received, and it contains the information of goods we are paying and tax with planned and unplanned delivery costs.

Planned costs: if the costs mentioned in invoice as well PO, then the costs are called as planned costs.

Unplanned costs: if the costs we are paying at invoice time and not mentioned in PO or GR, then those costs are maintained in MIRO as unplanned costs and paid to vendor.

Credit Memo: if any case the goods are failed in quality in quality testing then we use to return the goods with another PO and create MIGO and credit note wrt return PO to collect costs from vendor.

Subsequent adjustment: we have

Subsequent debit

Subsequent credit

Subsequent debit: if we are paying to vendor with extra invoice then we will use subsequent debit for the payment, suppose vendor forgets to collect the taxes for the previous PO, then vendor will send extra invoices for the purpose of subsequent debit.

Subsequent credit: if we already paid to vendor for the invoice and we see as per the contract we paid extra then we will be asking a subsequent credit.

49.Question: Explain Asset procurement?

Answer: Asset procurement is an MM-FI-PP Integration

As a MM consultant our part in Asset procurement is less and FI team use to generate the asset number and provide to PP team for the PR purpose and MM team use to create PO and MIGO.

50.Question: MRP with examples?

Answer: MRP provides their types of stocks planning by system automatically.

               1.Safety stock

               2.Planned independent stock

               3.Forecast based planning

51.Can we block a material master view?

Yes, we have customized blocking codes and for everything as per views and we can create in Logistics general-material master-material status

Project related Questions:

2. ASAP Methodology:

Asap methodology its an accelerated SAP methodology where we use to follow while implementation of project for the smooth functionality of project and time saving.

Its an SDLC method where we need to follow the process while we are implementing new SAP project.

We have 5 phases.

1.      Project preparation

2.      Business blueprint

3.      Realization

4.      Final preparation

5.      Preproduction / Go live support

1.      Project preparation: As an associate consultant I didn’t involved in the project preparation, where only project manager and my manager were involved and discussed about their module requirements and mainly server’s requirement and clients in servers and how many interfaces required estimation

2.      Business Blueprint: In this phase I have involved where not as a lead but as an associate I involved in understanding their current process in few concepts like purchase requisition and order, PIR, SL, Quota and old process of creation of contracts.

I have created the AS-IS document for above concepts and for major concepts AS-IS was created by senior consultants.

We also mapped to To-be process for all the concepts in word document, along with this integration requirements study and necessary plan for integration as per there requirements and if any requirements were not able achieve in SAP then we will mention in GAP analysis and works with technical consultant for the enhancement.

We will take sign from the client that AS-IS and TO-BE will be agreed to configuration.

3.      Realization: in this phase we will do all configurations that we defined in the business blueprint.

Material types/Field selection/Vendor account groups/Partner functions/purchase order document types with field selection/release procedure groups with classification

Inventory- STO related things, account determination/required valuation classes/new material stasis/IDOC’s, All integrations

All TR’s will be generated for the configurations and tested in unit/Integration testing.

UAT documents from super users

4.      Final preparation: in this phase all TR’s will be moved from quality client to production client and all number ranges and release strategy/LSMW/Mass maintenance/Posting periods

We will call all this as cut over activities

All material and vendor master data

UAT documents from end-users and training on the project.

5.      Golive/Support: we should support in terms on training and minor errors.

3.Question: LSMW/BDC/BAPI explanation?

Answer: LSMW: it’s a legacy system migration tool, where we use to migrate the data from legacy system to new SAP system and basically when there is an no customized fields in the data and no large data then we will go with LSMW process.

BDC-batch data communication- we will use BDC when there are customized fields are there in data upload and very large data then we will use BDC.

BAPI-Business application programming interface- when we have any open PR’s, PO’s and GR’s then we will use BAPI with help of developer.

Where in BDC and BAPI, we will prepare excel sheet with data and given to ABAP’er with all the explanation and they will be adding code and given back to us and we will perform the uploading.

6.Question: What are RICEFW with examples?

Answer: Reports, Interfaces, Conversions, Enhancements, Forms, Workflows.

Reports: As we are working in purchasing and inventory, reports plays a major role

We have

·        Standard reports

·        Custom reports

Every filed we are entering in SAP will be stored in tables and can be pulled in reports and few of the reports we cannot achieve because SAP has not provided the tables for all merge type.

So, we have custom reports, which are developed by ABAP, where we need to provide the requirements like filed names of all requirements

Example for standard report:

If we require any PO or PR reports for analysis purpose.

Example for Custom report:

If we require mode of transport in PO, then there are no standard reports to achieve at that time we created our custom reports with all the required fields.

In the PR item level, if we want requester field and release data of PR then also, we don’t have standard report it should be achieved by custom report.

Interfaces:

Interface will be data that can be shared with other system to SAP with the help of EDI.

Normally we can see in OCR, output condition once we send the PO through EDI the data transfer takes place through EDI and receiver system will have sales order automatically.

CMT- Contract request, where stakeholders use to create CMT request and as per the EDI it will flow respective user inbox with the help of workflow.

Approved vendor form- here we have custom T-code, in which vendor approval form will be prepared as per the data receive from QA team in plant- CG54

Conversions:

Here while we are using other tool and moved to SAP then data needs to be converted to respective format needs to be uploaded in SAP.

For that we need to use LSMW or BDC or BAPI

Uploading material master, I used LSMW and regarding scaling prices we requested buyer to process manually.

Enhancements:

If we want to do our own functionality within SAP, then we will do enhancement or if modifications for the existing functionality then also we do enhancement.

It will be done by SAP ABAPer and we need to support in functionality.

They may use BDC or BADI process.

For RFQ- While comparing we require lead time and price from for comparison.

Forms:

Forms are nothing but printouts where we have standard forms like PO print out like this, we have our own form for COA, where they use to update in their system and in this system COA will be printed with required fields.

ABAPer will prepare this and we need to mention the layout of fields name and table name.

Workflow:

We already know for release procedure we have workflow and to develop this workflow we need to work with ABAPer and tell what data needs to be

4.Challenging tickets for L1/L2/L3/L4?

We will receive tickets related to Master data updating/Changes/Configuration errors/New requirement/Enhancement/Modification/testing

L4- When business changes the process/Procedure and set of teams is working on those requests like it may take 30-45 days’ time for configuration and testing.

Example: New screen like we have new modifications for the existing process, where we need to perform like FRICEW.

Example 2: We worked on contract pricing in which we have taken the requirements of fields that’s impacting when they do normally for price change and worked on all aspects and developed pricing T-code and upload method for bulk price load.

L3-When we require any configuration changes to the SAP, after analyzing the requirement we will change the ticket level to L3. Time for this will be 15-20 days.

Example 1: we developed few forms for our client requirements, where it’s called COA for every vendor QA team will update the COA in the production system and through IDOC it will be placed in respective form in customized T-code. Based on the COA the buyers use to create Contracts and every they need few changes in forms like- QA team wants new fields in form.

At this time, we will work with power users and takes the fields requirements exactly and works with ABAP’er to get that field placed in forms.

Example 2: For RFQ, we have only price comparison which we will receive from vendor and, but we need to comparison of lead time also to be shown in RFQ documents.

We can achieve by enhancement to the normal screen.

Example 3: For plant they want source list to make mandatory for purchasing purpose, then we need to make configuration settings to make source list mandatory for purchasing.

L2-Normal tickets where resolution with MM or SD, where data needs to be updated or corrected by other teams. Time for the resolution is 18 hours

Example 1: Not able to perform MIGO for subcontracting cycle- where they use to procure the material from subcontracting vendor only.

These cases we cannot perform the goods receipt and we need to do goods receipt for child material that procuring and after for parent material.

Example 2: Customer code and sales organization issues in subcontracting cycle, where we need to check entire configuration for subcontracting.

L1-Normal basic queries but should be resolved within 10 hours and actioned within 3 hours.

Example:1 Pricing condition record not pulling in PO, even though they maintained all conditions.

While updating the vendor master, MDM team will forget to update the schema group in new vendor.

Example 2: MMPV Errors for Company codes, where we will do as month end activity. Because for few company codes it may miss updating closing period.

Example 3: When we have subcontracting cycle, all the postings has been completed and its under consumption and user raised a request after 1 month that still stocks showing in vendor consignment as they already done with MIGO.

To bring back the under consumption we need to perform 542 MB1B movement and it will not take automatically.

Example 4: User wants to upload the prices in PO, but the format of system is in, and he wants it in., so every system we have SU3 settings to change

Example 5: Currency rate and currency exchange will be raised to MM people, and we will assign to FI team, they will assign to MM department because PO and master data are related to MM.

Example 6: When they want price needs to be changed automatically as per the quantity in MIRO, then we can achieve by SU3.

5.Question: Use of BADI and User Exits

Answer: BADI and User Exits are used for the company related enhancements for the standard SAP screen.

For the standard SAP screen if we require any modifications with custom developments then we will use BAdi and user exit

7.Ticketing tool- Service now previously and now Manage Engine now.

8.Present project and responsibility:

Currently I’m working for project Consilio and I use to handle daily queries received from focal points and I use to analyze the query by interacting with team and resolving the issues.

Reviewing the configurations done PR’s and sending confirmations and maintain SLA by follow-ups with buyers and stakeholders regarding queries they raised.

Taking UAT documents from superusers which I did configured and maintain the Solman process and updating the status in ServiceNow.