Functional specification required for Me57 requirement

In SAP MM, Transaction ME57, I want to pull in the Common Inventory Quantity (Not Project or Sales Order Stock) of the Material which is maintained on the Purchase Requisition.
And also in the T code MB52 screen, the Inventory Quantity i want to bring it. It will be ALL Common Inventory in the Plant (minus Storage Loc a001 for Plant a000). Again, this should NOT pull in Project or Sales Order stock. Only Common Inventory.
I would like a rough functional specification draft ASAP. Pleas help.

Hi prasanna,
we can get SAP idoc types in tcode we31.For every requirment there will be different message type.
For example we want idoc type for account invoice receipt.
First find out message type for that purpose which can be found in we81-ACC_INVOICE_RECEIPT.
Get this message type and search in we82 where we can find message type and idoc type linkage.
try this way.
Reward if it is usful.
Thanks,
Srikanth.A

Similar Messages

Functional Specification Documents for SAP Sales and Distribution

Dear Gurus,
I am having the problems of Invoice Output..... the default out put generated by the SAP is completely different from the hard copy of the Invoice of the Client. ppl say that I have 2 take the help of ABAPers to define the smart forms for the invoices of different company codes.... i had conversation with the ABAPers.... butthey are asking the format, wht ever the change we are looking for..... I am not be able to get the exact format.... how 2 provide this to ABAPers in FS format.
can any one pls send me ( or provide me the link to download the same from the SDN website) these Functional Specification Documents for Sales and distribution.
Wishes,
Abhishek

Hi there,
1st try to understand what is a functional specification doc before asking for it.
Functional specs is a doc in which you include what is the business requirement. If it requires a change to change to existing configs / code, then you will give the progs & the location where you will need to change. If the requirement is a totally new one, then yuo will explain the requirement in detail & possibly give the progs / code if there are any.
In your case, your client has a specific invoice format which is different from which SAP gives, in such cases, you will need to define a new Invoice output for eg ZINV. Define it as a print output. You will need to define a new print prog for the new output in which you will call smart forms to define the layout & fields.
Ask your business user to send the invoice copy which he has. Scan it & include it in the functional specs which you prepare. Mention all the fields which you want in the layout. Ask the ABAPer to code the invoice format in the same way. ABAPer is free to define any convinent name as per the guidelines (which he will be aware). You will need to assign that in the form routines of the output.
As a functional consultant you will need to give the field mappings (from where you get the data) for all the fields which you wish to print in the output. All that should be included in the func specs.
So there is no standard func specs that you can follow. Each func specs varies on the requirement. So dont ask these kind of questions in SDN forum. If you dont know how to define func specs, ask how to define. Dont ask people to send the sample func specs. Thats against the rules of conduct.
Regards,
Sivanand

How to find out the idoc type required for our requirement

Hi,
How to find out the list of available idoc type in SAP. It will be good if i get to know the table name where all the idoc type definitions are gets stored.
Say i have some requirement and for that requirement how i can find the proper idoc type to be used. (assume functional consultant is not providing that information)
Points will be given for the useful answers
Thanks,
Prasanna

Hi prasanna,
we can get SAP idoc types in tcode we31.For every requirment there will be different message type.
For example we want idoc type for account invoice receipt.
First find out message type for that purpose which can be found in we81-ACC_INVOICE_RECEIPT.
Get this message type and search in we82 where we can find message type and idoc type linkage.
try this way.
Reward if it is usful.
Thanks,
Srikanth.A

Table details required for pegged requirements

Dear All,
I have the following scenario.
One child components is required for three different header materials. After MRP run, In MD04, three diffenerent planned orders will be there for child component for three reservations of three Header materials. I want to see the immediate header level of the child component through tables for report purpose. If you see through the function module MD_PEGGING or MD_PEGGING_NODIALOG, it is showing the top most header material. But it is not showing the immediate header material for the child component planned order. Please guide me to get the immediate header material through table or function module or any.
Thanks in advance.
Vijay.

Check these tables.
MDTB,PLAF.

Functional Specification doc for release strategy

Hi Gurus,
can anybody forward me the functional spec doc for release strategy. I know what to do by I am confused somewhere. My id [email protected]
Thanks for the help,
Armaan

Hi Sheeja
Look into table CABN.
regrds
Yogesh

Select statement or a procedure or a function required for this requirement

i have 2 tables t1 and t2.
t1 contains 1 column,named as c_id
t2 contains 2 columns, named as tc_id and preceeding_c_id.
select * from t1;
c_id
100
200
300
400
select * from t2;
tc_id preceeding_c_id
150 100
180 150
100
190 180
210 200
250 210
260 250
Now my requirement is:
I need to send a parameter as :c_id = 100
the ouput should be as follows
100
150
180
190
:c_id = 200
the output should be as follows:
200
210
250
260
Thanks & Regards

SQL> variable c_id number
SQL> exec :c_id := 100
PL/SQL procedure successfully completed.
SQL> with t as (
2             select 150 tc_id, 100 preceeding_c_id from dual union all
3             select 180, 150 from dual union all
4             select 100, null from dual union all
5             select 190, 180 from dual union all
6             select 210, 200 from dual union all
7             select 250, 210 from dual union all
8             select 260, 250 from dual
9            )
10   select tc_id
11     from t
12     start with preceeding_c_id = :c_id
13     connect by preceeding_c_id = prior tc_id
14 union all
15   select :c_id
16     from dual
17 order by 1
18 /
     TC_ID
       100
       150
       180
       190
SQL> exec :c_id := 200
PL/SQL procedure successfully completed.
SQL> /
     TC_ID
       200
       210
       250
       260
SQL> SY.

Java mapping or UDF required for a requirement!!!

I am doing idoc to file scenario and stuck with the mapping in the following case. I think an UDF or JAVA mapping will do the bill. can some one help me in this regard please.
IDoc message type, IDoc basic type, IDoc extension
PAYEXT.PEXR2002.ZEXR2002.
<u><b>conditions:</b></u>
IF E1IDB02 BA-FIIKWAER = CNY
      then MID(E1EDKA1 BE-NAME1,12,11)
IF E1IDB02 BA-FIIKWAER <> CNY and LEN(E1EDKA1 BE-NAME1)<=35
     then MID(E1EDKA1 BE-STRAS,1,35)
IF E1IDB02 BA-FIIKWAER <> CNY and LEN(E1EDKA1 BE-NAME1)>35
     then MID(E1EDKA1 BE-NAME1,36,35)
This will be mapped to "Info Line 1" field in file.
Thanks,
Kiran

Hi Mr.Kiran,
here is the code
pass the following fields to Context UDF
1.E1IDB02-FIIKWAER
2.E1EDKA1-NAME1
3.E1EDKA1-STRAS
for(int k = 0;k<FIIKWAER.length;k++)
     if(FIIKWEAR[k].equalsIgnoreCase("CNY"))
        result.addValue(NAME1[k].substring(11,12));
     else if(!(FIIKWEAR[k].equalsIgnoreCase("CNY"))&&(NAME1[k].length() <= 35))
       result.addValue(STRAS[k].substring(1,35));
     else if(!(FIIKWEAR[k].equalsIgnoreCase("CNY"))&&(NAME1[k].length() > 35))
      result.addValue(NAME1[k].substring(35,36));

Logic required for the requirement (urgent)

HI experts,
can anyone help me out regarding the following logic.
The logic will check for both complete and partial goods receipts and invoice receipts. Based on the PO line item history it will calculate the totals into following categories:
(1) Total PO Line Item value with both GR & IR
(2) Total PO Line Item value with GR but no IR
(3) Total PO Line Item value with IR but no GR
For a single PO line, it is possible to have the Total Line Item Value divided into one or more of the above three categories at the same time. For example, if for a PO line item with 100 unit at $10.00 per unit, there is a GR for 50 Units and IR for only 30 units, the three columns above will be populated as:
(1) Total PO Line Item value with both GR & IR 30 x 10 = 300
(2) Total PO Line Item value with GR but no IR 20 x 10 = 200
(3) Total PO Line Item value with IR but no GR 0 x 10 = 0
Similarly, if for a PO line item with 100 units and $10.00 per unit, there is a GR for 50 units and IR for 70 units, the three columns will be populated as:
(1) Total PO Line Item value with both GR & IR 50 x 10 = 500
(2) Total PO Line Item value with GR but no IR 0 x 10 = 0
(3) Total PO Line Item value with IR but no GR 20 x 10 = 200
Regards,
Nagaraj

Maybe this example will help....
report zrich_0002 .
data: iekbe type table of ekbe with header line.
data: xmbew type mbew.
data: xekpo type ekpo.
data: begin of ibuckets occurs 0,
      ebeln type ekpo-ebeln,
      ebelp type ekpo-ebelp,
      pgrir type p decimals 2, " Total GR & IR
      pgr   type p decimals 2, " Total GR
      pir   type p decimals 2, " Total IR
      pgrni type p decimals 2, "GR no IR
      pirng type p decimals 2, "IR no GR
      end of ibuckets.
parameters: p_ebeln type ekko-ebeln,
            p_ebelp type ekpo-ebelp.
start-of-selection.
clear iekbe. refresh iekbe.
select * into table iekbe from ekbe
              where ebeln = p_ebeln
                and ebelp = p_ebelp
                and vgabe in ('1','2').
loop at iekbe.
    clear ibuckets.
    ibuckets-ebeln = iekbe-ebeln.
    ibuckets-ebelp = iekbe-ebelp.
    select single * from ekpo into xekpo
                  where ebeln = iekbe-ebeln
                    and ebelp = iekbe-ebelp.
    select single * from mbew into xmbew
                   where matnr = xekpo-matnr.
    case iekbe-vgabe.
      when '1'.
        ibuckets-pgrir = iekbe-menge * xmbew-stprs.
        ibuckets-pgr   = iekbe-menge * xmbew-stprs.
      when '2'.
        ibuckets-pgrir = iekbe-menge * xmbew-stprs.
        ibuckets-pir   = iekbe-menge * xmbew-stprs.
    endcase.
    collect ibuckets.
endloop.
loop at ibuckets.
    ibuckets-pgrni = ibuckets-pgr - ibuckets-pir.
    ibuckets-pirng = ibuckets-pir - ibuckets-pgr.
    if ibuckets-pgrni < 0.
      clear ibuckets-pgrni.
    endif.
    if ibuckets-pirng < 0.
      clear ibuckets-pirng.
    endif.
    modify ibuckets.
endloop.
loop at ibuckets.
    write:/    ibuckets-ebeln,
               ibuckets-ebelp ,
               ibuckets-pgrir,
               ibuckets-pgr   ,
               ibuckets-pir ,
               ibuckets-pgrni ,
               ibuckets-pirng .
endloop.
Regards,
Rich Heilman

EXIT_SAPMM06E_016 for User exit how to prepare functional specification.

Hello Gentlemen,
Ex: - issue for the PO no: 4500006789
Made advance payment against PO 100%, later vendor has given discount on freight charges, so once advance payment is made then system should not allow to amending the PO.
Now client requirements are as follows likeu2026.
Condition no1: If there is an existing down payment against the PO then system should allow to amending the PO, but system should throw the warning message as there is already down payment against the PO.
Condition no2: If there is an existing down payment against the PO system should allow to amending the PO, but system should not allow to changing more than the total value of the PO.
So User exit which I have mentioned in above subject line it should be in a position to fullfill the condition no1 and condition no2.
So pleas let me know the functional specification and functional specification logic for above said in subject User exit.
Early action inthis matter will be highly appreciated.

as far as i know, when you make an advance payment you can link it to a po only thru a reference text field.
uncleared vendor items will be table BSIK
you may have to filter it out by transaction type A and spl gl indicator A, both refering to down payment.
this way you can find out what is the advance payment still with the vendor.

Technical Requirements for SD in ECC 6.0

Hi All,
I need to document the technical requirements in ECC 6.0 implementation for SD Module.Kindly revert back with helpful answers.
Thanks,
Faisal

As per my understanding you require information on what Technical document might be required to be prepared by SD Consultant. If my understanding is correct, in that case we require to prepare Functional Specs for the enhncement & development required in the project.
Functional Specs:
To speak at macro level that is at project manager or at senior levels. The Functional Spec (Specification) which is a comprehensive document is created after the (SRS) Software Requirements Document. It provides more details on selected items originally described in the Software Requirements Template. Elsewhere organizations combine these two documents into a single document.
The Functional Specification describes the features of the desired functionality. It describes the product's features as seen by the stake holders, and contains the technical information and the data needed for the design and development.
The Functional Specification defines what the functionality will be of a particular area that is to be precise a transaction in SAP terminology.
The Functional Specification document to create a detailed design document that explains in detail how the software will be designed and developed.
The functional specification translates the Software Requirements template into a technical description which
a) Ensures that the product feature requirements are correctly understood before moving into the next step that is technical development process.
b) Clearly and unambiguously provides all the information necessary for the technical consultants to develop the objects.
At the consultant level the functional specs are prepared by functional consultants on any functionality for the purpose of getting the same functionality designed by the technical people as most of the times the functionalities according to the requirements of the clients are not available on ready made basis.
Let me throw some light on documentation which is prepared before and in a project:
1) Templates
2) Heat Analysis -
3) Fit Gap or Gap Analysis
4) Business Process Design
5) Business Process Model
6) Business Change & Impact
7) Configuration Design, which is just 5 % of Total SAP- have different names -
8) Future Impact & Change Assessment
9) Functional Design (Module Wise)
10) Risk Assessment
11) Process Metrics and Many More-- Which has impact on Business and its work flow
Regards,
Rajesh Banka

Need a Pegging module for dependent requirements.

Hi
Need a Pegging functional module for dependent requirements.
There is MD_PEGGING_NODIALOG ,where we need to pass the planned order number.
Please advise how to get the pegged requirements for dependent requirements or other MRP elements other than planned order.
Thanks
Prasad

Hello,
Function module MD_PEGGING_NODIALOG works with data structures of MRP list or current requirements/stock list. For a given material, you first need to fetch the relevant structures by the help of following FMs; BAPI_MATERIAL_MRP_LIST and BAPI_MATERIAL_STOCK_REQ_LIST. You can loop at the structures exported by these FMs and run MD_PEGGING_NODIALOG with the corresponding parameters of the MRP element you require. You can run MD_PEGGING_NODIALOG with any MRP element you like as in MD04 and MD05 transactions.
Regards.

Functional specification documents..

HI guys,
I am new to SAP HCM..
i was wonderingg as to when is the need to write a Function spec document?
It would be great if you could give an example..
Also, what is the difference between Functioal Spec doc and functioal design document??
Thanks,

Functional-specification documents decribes business requirements and required changes that are to be applied in Project.
For Example If you company want to implement Second saturday as well fouth saturday as off days: For this you have to clearly mentioned the business requirement , what are the pre requisites required , is there ny development is required etc...
some time test cases also attached with this
Please refer these links , which will help you
http://www.premieresapconsultants.com/wisdom/2010/08/sap-functional-document/
http://www.sap-img.com/general/what-are-functional-specification-in-sap.htm

Workflow Functional Specification Document

Hi All
I am working on a implementation project which includes Workflows. Right now I am in the process of writing the functional specification document for the Workflows. I am a functional consultant and never worked on workflows.
Can some one provide me what should be included in the functional document , how should the flow be written.
Is there any sample Workflow template anyone can share.
There are 4 places that requires workflows according to my understanding as described below in my requirement:
1. Workflow for corporate users when a notification is created or closed
2. Workflow email, forward a complaint to
     Finance Manager
     Quality Manager
     Plant Managers
3. Workflow for forwarding to an approver, reassign task to someone else
4. Workflow to send remainder emails for open items longer than 30 days
Please provide your insights and neccesary documentation to start
Thanks,
Sai

HI Prakash,
Thanks for the detailed response, it helped me a lot.
for approval to sales director, operations director and quality director an email has to be triggred simultaneously.We have predefined list depending on plant who can take corrective action and who can approve the corresponding task. Further users should have the option to select who should get the email.
For Approver Determination:
Case 1: In your scenario approver is not fixed.The approvers get selected based on plant. Try to get link between plant and all the approvers. The easy approch will be to maintain the approvers SAP ID in Z-Table against all the plant and developer will use RULE to fetch approvers from this Z-Table. The structure of Z-Table will be:
                                  PLANT     LEVEL   OBJID     USERID
For one plant 3 entry will be maitained here. LEVEL will help to identify the 3 types of approvers i.e. sales director, operations director and quality director. OBJID value will be US (if SAP ID will maintained in USERID), O (if Org. ID will maintained in USERID), S (if Position will maintained in USERID) etc. Benifit of this approch will be when ever you want to change any approver you have to change corresponding entry in this Z-Table no need to do changes in Workflow (As suggested by Ronen).
I used the same logic, creating a Z-Table for agents who has to approve the corrective action for taks completed. I was curious if there is a standard way to get this functionality in SAP. I am not sure about the responsibility rule that Mike was mentioning. Can you tell me which approach is a better design.
Case 2: Now I am confused since you said user can choose next level of approver. So please explain in which scenario Approver will come based on plant and in which scenario user will choose it manually. If user have to choose manually then a screen design is require. From approval screen based on user selection you need to pass the Approver in workflow.
Sorry for not putting things clealy. There are no levels for approval. Each of them are independent i.e. Sales director , Operations Manager and Quality director should get emails for approval after the Plant Manager, QA, Manager, Sales Coordinator take corrective action and the notification is closed only when all 3 of them approve the corrective action.
The user have to choose manually when the correspondng approver of that plant left the company, long vacation, took a new role etc...
Mail Notification: Extended mail notification functionaity is there. The person who will get work item in his/her SAP inbox for approval they will get mail notification in their external mail ID. All the approvers email id should be maintained along with their SAP ID in T-Code SU01. You Just need to provide mail contents in your FS, workflow developer will put same text in in mail body.
I was thinking about the SO23 distribution list for sending the emails to approvers. Also, how do the emails go to the corresonding approvers of that specific plant unless we explicity specify the email id's associated with that plant. Please clarify.
Thanks,
Sandeep

Functional Specification Document needed

hi guys ...
i have been asked to write the functional specification document for the following issue... i have never wrote any functional Spec. till now... can n y one write it down for me...or tell me the exact format of how to write it down...
The issue is as follows....thx.
Invoice enhancements for tagging, serial number and email identification
1. Add the Customer Tagging Text to the invoice document.
2. Add Serial Number to the invoice.
3. Change the subject line for the emailed invoice from the generic "SPX Invoice $000000001" to the more meaningful format "SPX Invoice <invoice number>, SO <sales order number>, for <customer name>", the order acknowledgement already has a similar format
Please do reply.... thanks in advance.

Hi,
Broadly in SAP there will be two types of Consultants - Functional and Technical. Technical consultants are mainly working on developments / changes in programs using ABAP language.
On the other hand Functional Consultants understand the business process from Business users and map the functionality in SAP by doing required configurations and by designing reports.
Here comes the Functional Design Specification. The report / an extension is developed by Technical resource, but the design / explanation has to be given by Functional Consultant in such a way that Technical Consultant is able to understand it. In other words it should be a media for converting Business language into a language understood by Technical Consultant.
So, in a Functional design of a report Functional Consultant should furnish the following information:
   - Assumptions made
   - Pre requisites to be met for executing the report / transaction
   - Main Tables from which data to be selected
   - Selection Parameters for executing the report.
   - Logic for the Program
   - Layout of the report
Thanks
Murali.

What is the significance of Functional Specification.

Please do mail me at [email protected]

Dear FARHAN FAROOQ,
The Functional Specification describes the features of the desired functinality.
It describes the product's features as seen by the stake holders,and contains the technical information and the data needed for the design and developement.
The Functional Specification defines what the functionality will be of a particulat area that is to be precise a transaction in SAP terminology.
The Functional Specification document to create a detailed design document that explains in detail how the software will be designed and developed.
The functional specification translates the Software Requirements template into a technical description which
a) Ensures that the product feature requirements are correctly understood before moving into the next step, that is detchnical developement process.
b) Clearly and unambiguously provides all the information necessary for the technical consultants to develop the objects.
A functional specification (or sometimes functional specifications) is a formal document used to describe in detail for software developers a product's intended capabilities, appearance, and interactions with users. The functional specification is a kind of guideline and continuing reference point as the developers write the programming code. (At least one major product development group used a "Write the manual first" approach. Before the product existed, they wrote the user's guide for a word processing system, then declared that the user's guide was the functional specification. The developers were challenged to create a product that matched what the user's guide described.) Typically, the functional specification for an application program with a series of interactive windows and dialogs with a user would show the visual appearance of the user interface and describe each of the possible user input actions and the program response actions. A functional specification may also contain formal descriptions of user tasks, dependencies on other products, and usability criteria. Many companies have a guide for developers that describes what topics any product's functional specification should contain.
For a sense of where the functional specification fits into the development process, here are a typical series of steps in developing a software product:
Requirements. This is a formal statement of what the product planners informed by their knowledge of the marketplace and specific input from existing or potential customers believe is needed for a new product or a new version of an existing product. Requirements are usually expressed in terms of narrative statements and in a relatively general way.
Objectives. Objectives are written by product designers in response to the Requirements. They describe in a more specific way what the product will look like. Objectives may describe architectures, protocols, and standards to which the product will conform. Measurable objectives are those that set some criteria by which the end product can be judged. Measurability can be in terms of some index of customer satisfaction or in terms of capabilities and task times. Objectives must recognize time and resource constraints. The development schedule is often part or a corollary of the Objectives.
Functional specification. The functional specification (usually functional spec or just spec for short) is the formal response to the objectives. It describes all external user and programming interfaces that the product must support.
Design change requests. Throughout the development process, as the need for change to the functional specification is recognized, a formal change is described in a design change request.
Logic specification. The structure of the programming (for example, major groups of code modules that support a similar function), individual code modules and their relationships, and the data parameters that they pass to each other may be described in a formal document called a logic specification. The logic specification describes internal interfaces and is for use only by the developers, testers, and, later, to some extent, the programmers that service the product and provide code fixes to the field.
User documentation. In general, all of the preceding documents (except the logic specification) are used as source material for the technical manuals and online information (such as help pages) that are prepared for the product's users.
Test plan. Most development groups have a formal test plan that describes test cases that will exercise the programming that is written. Testing is done at the module (or unit) level, at the component level, and at the system level in context with other products. This can be thought of as alpha testing. The plan may also allow for beta test. Some companies provide an early version of the product to a selected group of customers for testing in a "real world" situation.
The final product. Ideally, the final product is a complete implementation of the functional specification and design change requests, some of which may result from formal testing and beta testing.
The cycle is then repeated for the next version of the product, beginning with a new Requirements statement, which ideally uses feedback from customers about the current product to determine what customers need or want next.
Hope this helps you.
Do award points if you found them useful.
Regards,
Rakesh
P.S. you can send me a mail at my mail id [email protected] for any specific details

Functional specification required for Me57 requirement

Similar Messages

Maybe you are looking for