Differnt material in order and idoc

Hi,
I have a standard order that is created through inbound idoc.
The data segment in the idoc shows a differnt material while that present in the created order line item is different.
What could be the possible reason and where can I check the same.

Hi
Use T code WE60 to search for the segment documentation of IDoc type
IDoc needs three different kinds of segment types:
E1EDK01 is the main segment of an ORDERS01 IDoc.Used for calling program to pass the SAP IDoc syntax check.
E1EDP01 is the segment for a single order position. The field MENGE contains the quantity. Of course, this segment can occur more the once.
E1EDP19 represents an object definition. In this case the object is a material number. The field QUALF is therefore set to 002 and the material number is written into the IDTNR field. E1EDP19 segments are always children of E1EDP01
Rohit

Similar Messages

Study material on ALE and IDOCS

Hi
If anyone has some study material on ALE and IDOCS ,if you can please send it across to me , it would be very helpful to me .
My mail id is : [email protected]
Thanks in advance
Ankit

1. What is ALE?
Application Link Enabling (ALE) is a set of business processes and tools that allow applications on different computer systems to be linked. This can be done between different SAP systems as well as between SAP and non-SAP systems.
In a single SAP system different applications are integrated via a single database (e.g. finance, sales, production, human resources). However, many companies do not have just one integrated system but a distributed environment with different applications running on different systems. To run the whole business in such an environment the distributed applications have to be linked. This can be done through Application Link Enabling (ALE).
ALE provides distributed business processes that can be used to link the applications on different platforms. There are some ALE business processes delivered in the standard SAP system. Furthermore, there are tools that can be used to change the existing ALE business processes or to implement new distributed business processes.
Besides the business processes there are special ALE services that are required to set up and control a distributed environment. These services include a distribution model, business object synchronization and tools for monitoring or error handling.
ALE is a major part of SAP's Business Framework Architecture. Besides the basis middleware, that provides the communication between components, and the interfaces (BAPIs), ALE business processes and ALE services enable the cooperation of the single components within the framework. That makes ALE the glue of the Business Framework.
2. What are the benefits of ALE?
With ALE companies get the opportunity to improve business performance and to solve organizational or technical issues.
Through distribution you can decentralize your business, enabling local units to operate independently from each other. This flexibility enables the local units to return better business results than in a centralized environment. They have the necessary flexibility to optimize business processes in different organizational units and can ensure that information systems can handle the speed of change in rapidly expanding markets. Distribution allows a high level of freedom, provided that this level of freedom has been clearly defined.
On the other hand, some companies, that already have a distributed organization with different computer systems in the local units, have the opportunity to link their units through ALE business processes. This enables them for example to provide a 'one face to the customer' approach. Another area that can benefit through ALE are virtual organizations (partnerships between independent companies, joint ventures and mergers and acquisitions).
Of course, in many cases an integrated solution based on a single system is not possible at all. Some applications used by a company can not run on the same computer system. This includes legacy systems or complementary software. It may also be possible that a company uses different SAP industry solutions or specific country solutions, which do not run on the same SAP System. If these applications run on different systems they can not be linked by a central database but have to use a special integration mechanism like ALE. In this way ALE also links SAP Core Systems to other SAP components like CRM, Business Information Warehouse or APO.
Besides the benefits of having an improved flexibility in setting up the whole business processes, ALE may also reduce costs, in particular costs of upgrading. If the whole business is run on one integrated system you have to upgrade the whole system, even if only one part of your company (e.g. human resources) requires an update. So the entire company is affected by the upgrade project and all users have to be trained for the new release. Within a distributed environment with release independent interfaces, like those provided by ALE, you can focus the upgrade project on that part of the company that has to be upgraded. The other parts of the company are not involved and need no training. This can save a lot of money. Furthermore, existing investments are protected.
Another cost factor for distribution might be communication costs. For an overseas connection it can be more expensive to provide online access to one central system (T1) than to connect distributed systems to each other (64K line).
There might also be some technical reasons for distributed systems. If some parts of the business have special requirements for security of data access (e.g. human resources), this can be set up much safer on a standalone system, which is, however, linked to other parts of the company through distributed business processes. A similar example is high availability. High availability is usually required by the operations part of the company (production, logistics) but not by other areas (e.g. financials, human resources). In a distributed environment high availability can be set up for specific parts of the environment instead of for the whole business. This can also reduce costs.
In a distributed environment you can not decrease the overall workload of the systems but you can separate the user workloads on different systems. Through this scalability you can improve performance. Another benefit of distributed systems is that if a technical failure occurs on one system, all other systems continue to operate. Only a small part of the business is disrupted by the error. On one central system such an error would disrupt the entire business.
3. When should ALE be used?
Besides the benefits of ALE there are also reasons not to distribute:
The functional scope in a distributed environment is restricted. Not all functionality that is available in an integrated SAP system can be used with distributed systems in the standard yet. Although ALE provides tools to create new ALE business processes or to enhance existing business processes, this does involve additional expenditure.
Each company needs some organizational standards and data harmonization. In a distributed environment less standards are required than on a single integrated system. However, in a distributed environment the maintenance of the standards and the data harmonization is more difficult than on a single system.
The administration of decentralized systems is more expensive. Support and service costs for hardware and software in decentralized systems are higher than these costs in a single centralized system.
ALE should be used in a company if the benefits of ALE for this company outweigh the reasons against distribution. For this you always need to carry out a company specific investigation, in which you also should consider the culture of the company. ALE is good for some companies but not for all.
4. What is the relationship between ALE and Middleware?
Electronic Data Interchange (EDI) is a term for the transfer of business messages between two systems. There are many such messages, the most common of these include a customer sending a purchase order message to a vendor, or a vendor sending an invoice message to a customer. Classic EDI is mainly restricted on the exchange of transactional data, no master data or configuration data. In most cases, EDI replaces the transfer of paper copies of these documents. Via the messages ALE business processes can be implemented between business partners. The EDI messages also use the ALE services.
For the communication between different types of systems special EDI messages are defined as standards for inter company communication. There are many standards for these messages - in the United States, the ANSI X.12 standard is the most prevalent, in Europe, the UN/EDIFACT standard is used. For sending EDI messages the information has to be converted into an EDI standard. With SAP systems this is done by EDI subsystems. This conversion is the only difference between EDI messages and other messages used in ALE business processes. The processing of these messages on the SAP System is the same as the processing of other ALE messages.
5. Which ALE business processes are available?
IDoc Types - Message Types
ALE business processes are integrated business processes that run across distributed systems. This can be two different SAP systems, links between SAP and non-SAP systems, SAP and Web-servers (Internet Application Components) or SAP and desktop applications. The links between the systems may be loosely (asynchronous) or tightly (synchronous) coupled. These business processes are release independent and can run between different release levels of the systems.
Many SAP applications offer ALE distribution processes. The following list gives some examples:
Master data replication (IDoc Types - Message Types - Master Data)
- Material
- Customer
- Vendor
- General Ledger accounts
- Bill of materials
Accounting (IDoc Types - Message Types -Accounting Business Processes)
- Links to logistic systems
- Distributed financial accounting
- Distributed cost center accounting
- Distributed special ledger
- Profitability analysis
- Distributed profit center accounting
- Consolidation
- Treasury
Logistics(IDoc Types - Message Types - Logistics Business Processes)
- Reallocation of materials
- Distribution of sales and shipping
- Product data management
- Purchasing contracts
- Sales and operations planning
- Warehouse management
- Links to warehouse control systems
- Links to production optimization systems
- Links to transport planning systems
Information systems (IDoc Types - Message Types - Logistics Business Processes)
- SAP Business Information Warehouse (BW)
- Exchange of data between information systems
- Web reporting
Human resources (IDoc Types - Message Types - HR Business Processes)
- Human resources as a single component
- Payroll results
- Travel expense accounting
- Links to time collecting systems
However, these standard solutions may not fit 100% for a company. There may be differentiation in the business process or a required distributed business process is not supported in the standard. If this happens, ALE provides tools that can be used to adapt a standard ALE business process or to create a new distributed business process.
6. Which ALE services are available and what do they do?
To integrate distributed systems you need more than a communication infrastructure and interfaces. Some additional services are required that are provided by ALE:
Business process harmonization:
Within system overlapping business processes multiple functions running on multiple systems are involved and connected through multiple interfaces. The processes are combinations of functions (sub-processes) running on the single systems.
(Example: A business process for customer order management involves functions in sales, manufacturing, warehouse management, finance, and so on. It is possible that the sales functions are carried out on another system than the manufacturing, the warehouse management or the accounting. Furthermore, some information exchange with the customer, a supplier or a bank may be involved in the process.)
ALE helps to coordinate the whole business process by defining it within a global model. In this model the business rules for the distribution are defined. Via the model the sub-processes get to know which part of the overall process they have to do themselves and when they have to pass the process over to another system. Through this the whole business process gets harmonized.
Receiver determination:
For distributed business processes a sub-process on one application (client) has to start another sub-process on another application (server). It is important that the new sub-process is started on the right server. Which server is the right one can not be defined by technical values, it depends on the business content of the process.
(Example: A sales system forwards customer orders to two different production systems. To which system a special sales order is forwarded depends on the entries in the sales order (this may depend, for instance, on the ordered material or on the customer). One sales order may also be split into two or more different orders that may be forwarded to different production systems.)
To notify the client which system is the receiver of the communication (server), ALE uses a distribution model. From this model the applications get the information about the right server. There are special ALE BAPIs and function modules available for this. The receiver determination makes sure that the information is sent to the right places.
Business object synchronization (semantic synchronization):
If business processes run across distributed systems, they have to share some data to be harmonized. This is data like business information data, master data or customizing data. If this data is changed in any of the distributed systems, other systems have to be informed about the change. There has to be some kind of subscription of the data.
ALE provides a special service for this data synchronization. This service can detect data changes and distribute the information to those systems that need to know about the change. This service also defines which data is shared. You can determine which fields of a data object shall be common and which fields may vary locally.
Consistency checks:
For a business process running across two distributed applications there has to be some harmonization of the sub-processes in the single applications. For making sure that the sub processes are harmonized there are special ALE consistency check tools. These tools help to find and repair inconsistencies. By this it can be ensured that the whole ALE business process works in the right way.
Monitoring:
For the monitoring of distributed processes it is not enough to monitor all activities on the single systems. The overall business process has to be monitored. The ALE monitoring services provide detailed information about the communication process, the sub-process on the other systems and its results. Database links are created between the business objects in question on the client and the server. This is especially important for loosely coupled applications with asynchronous links. In this case the server can not give return values back to the client directly so that the ALE monitoring is the only channel for feedback.
Error handling:
Another problem with asynchronous communication is error handling. If an error occurs on the server the calling process on the client may have finished already. So the server can not return the error message to the client. A special error handling process required. This process is one of the ALE services. It uses workflow functionality to identify the error and to start the required error handling.
7. Synchronous vs. asynchronous links?
When distributed applications are linked by ALE business processes, the question often arises as to how tight the link should be. Synchronous and asynchronous links have both advantages and disadvantages.
Synchronous links have the advantage that the sub-process on the server can return values to the sub-process on the client that has started the link. Problems with synchronous links occur if the communication line or the server is temporarily not available. If this happens, the sub-process on the client can not be finished (otherwise there would be data inconsistencies).
(Example: There is a logistics system and a financial system. Every stock movement in logistics has to be posted in the general ledger of the financial system. If the link between logistics and finance is synchronous, no stock movement can be recorded in the logistics system if the communication line to the financial system is down.)
Because of this, synchronous links are usually used if the client only wants to get some data from the server and the sub-processes on the server do not have to write any data to the database.
With asynchronous links the sub-process on the client can be finished even if the communication line or the server is not available. In this case the message is stored in the database and the communication can be done later. The disadvantage of asynchronous links is that the sub-process on the server can not return information to the calling sub-process on the client. A special way for sending information back to the client is required. In addition, a special error handling mechanism is required to handle errors on the receiving side.
Asynchronous links are used if a synchronous link is not applicable. For the problems with sending return information to the client and with error handling there is some support from the ALE services.
8. Which kind of interfaces do ALE business processes use?
ALE business processes are integrated processes across distributed systems, requiring interfaces between the systems. These interfaces have to be stable to enable the communication between different releases and to reduce the impact of release changes within the distributed environment.
In SAP R/3 release 3.0 and 3.1 ALE uses IDocs as interfaces. An IDocs is a data container for transferring messages asynchronously. They are release independent. Since SAP Release 3.1G BAPIs are a new type of object oriented, stable interfaces that can be called synchronously or asynchronously. Asynchronous BAPIs use IDocs as data containers. ALE business processes can use BAPIs as well. In the future new ALE business processes will use BAPIs as interfaces. But the existing IDocs will still be supported. In time, BAPIs will be created with similar functionality to existing IDoc interfaces.
9. Why does SAP uses ALE instead of database replication or distributed databases?
Database replication is another possibility for doing business object synchronization. However, there are some major disadvantages with database replication. At the moment database replication is database dependent and release dependent within one database. This makes database replication impossible for the use with non-SAP systems and even for the replication between SAP Systems you have to make sure that all systems are running on the same SAP release and the same database release of a single database vendor. Furthermore, with database replication you cannot do things like field conversions or version changes. ALE does not have these shortcomings because it offers application driven data replication independent of the underlying database.
Another technology, distributed databases, is no alternative for ALE at the moment, either. There are some good results of distributed databases available, but the performance is far from sufficient for using it with larger applications like SAP.
10. What is the relationship between ALE and middleware?
For distributed business processes many different services are required. Most of these services are offered by SAP. For some of these services you can also use products that are provided by SAP's complementary software partners or by other companies:
The communication service for doing the pure communication is usually done via Remote Function Call (RFC). RFC is provided by SAP for most platforms both for synchronous and asynchronous communication. There are other messaging systems for the communication service available as well, like IBM's MQSeries. However, the communication between SAP and the messaging system is still done via RFC.
For the serialization of asynchronous communication the RFC provides little functionality at the moment. The serialization has to be checked by the application. ALE offers some support to do these checks. The serialization of the RFC communication will be improved in the future. Serialization services are provided by some of the existing messaging systems, but even they can not guaranty a 100% serialization of the communication, since they use RFC for the connection to SAP.
The monitoring and error handling of the communication is done via services provided by the RFC and ALE. If messaging systems are used for the communication they also offer some monitoring and error handling functionality.
If a non-SAP system is involved in the ALE business scenario and this system does not understand SAP's BAPI or IDoc interfaces, the data has to be mapped to any interface structure that this system offers. For this mapping SAP does not provide a service but it certifies mapping tools from software partners. These tools are called ALE translator. The most known product in this area is probably Mercator from TSI International Software. The same kind of mapping can also be done by 'EDI converters'.
Another type of middleware products offer process ware. This is mainly a combination of the communication service, the mapping service and a set of rules for the mapping. Some ALE translator can be used for this as well.
Receiver determination is one of the ALE services (see above). Parts of this service can also be provided by some of the messaging systems, but you cannot use these systems without using ALE receiver determination.
For the other ALE services like application monitoring, application error handling, semantic synchronization and business process harmonization, there are no middleware products available as a replacement of ALE.
ALE is open for the use of middleware products for the distribution, but in most cases the additional middleware is not necessary. In a communication between different SAP systems usually the use of additional middleware makes no sense at all. For the communication between SAP and non-SAP systems there might be some benefits, especially if the middleware is used at the company already. The only middleware tool that is really required if the non-SAP system does not understand BAPIs or IDocs is an ALE translator.
Check different sites for more information.
Regards

Material in order and invoice, but i don't want it appears in delivery

Hi Gurus,
I have a problem. I have a dummy material (insurance) which is a service. I want that material appears in order and invoice (va02, vf02) like a normal item, but i don't want this material in the delivery (vl02).
I change item category for this dummy material to LEIS (service without delivery, before was DIEN, with delivery), but it still appears in delivery.
I have to do it through materials. We have ruled out a solution based in price conditions.
Can you help me? Have you some ideas what i have to do?
thanks,
Abel

First of all, thank you to everyone has answered to my post.
I've tried with some of your solutions and it works for take the material out of the delivery, but our problem still being there, because we have to do the billing from the delivery. When we do billing, this dummy material doesn't appear in the invoice.
Maybe what I asked before is impossible, so i think there's another option. The problem we have is about delivery note which includes this service. But, can I print the delivery note without this material? I wouldn't like modify the printing program, there's another option for taking the items which i don't want to see out of the output?
thanks to everyone,
abel

Purchase order and IDOC

Hi gurus,
can anyone send all the configuration steps involved when i save an Purchase Order then an idoc has to be generated
and send to PRD .
Pls help me.
Thanks and regards,
Rajeshwar.

thanks

Can any one prvide documentaion for BAPI Material, Sales order and Pricing?

Hi,
Can any one provide documentaion for BAPI Material create and change, Sales order create and change and Pricing?
thanks & Regards,
Gop.

Hi!
TABLES: t184.
IF NOT VBAP-PSTYV IS INITIAL.
SELECT SINGLE * FROM t184 WHERE pstyv = vbap-pstyv.
IF sy-subrc = 0.
IF t184-vwpos IS INITIAL.
IF t184-psty2 <> vbap-psty2.
MESSAGE e987(ZSD). "create the 987 message with SE91 transaction - ZSD mess.class
ENDIF.
ENDIF.
ENDIF.
ENDIF.
Somehow like this.
Regards
Tamá

About ALE transaction set 860 (purchase orders) and Idoc type ORDERS05.

Hi all,
What is the mapping between the two? How can I find more about the two..
Thanks,
Charles.
+++++++++++++++++++++

Hi,
Guess it looks like the output is getting proposed but its not getting processed. Check the output type configuration. Check the TIme Settings in the output type configuration.
It is possible to set the Time when the output must be processed. Is it on SAVE or is it set to other settings. If its set to via background job then the background job must be run to process the output types.
Check and let me know if all is fine at the output type configuration.
Cheers
VJ

Want some good links on BAPI and IDOC's.......

Hi,
Can I get some good links and some good material in BAPI and IDOC's.
Thanks in advance.
Message was edited by: Deepak333 k

hi
http://cma.zdnet.com/book/abap/ch03/ch03.htm
http://help.sap.com/saphelp_40b/helpdata/en/4f/991f82446d11d189700000e8322d00/applet.htm SAP Online Help For Dictionary.
http://sappoint.com/abap/
for SAPscripts
For follg., refer http://www.henrikfrank.dk/abapuk.html
Please note that I do not offer any support for the examples !
ABAP objects and control technology
IDOC
SapScript
Performance tuning
BAPI Programming
Visual Basic Integration - Using the DCOM Connector and BAPI OCX (Only available in Danish)
JAVA and the SAP java connector
http://www.sts.tu-harburg.de/teaching/sap_r3/ABAP4/abapindx.htm
for keywords
very useful link for all
http://www.sapgenie.com/abap/index.htm
http://www.sap-img.com/abap.htm
http://www.sapdevelopment.co.uk/tips/tipshome.htm
http://help.sap.com/printdocu/core/Print46c/en/Data/Index_en.htm
http://sap.ittoolbox.com/nav/t.asp?t=322&p=322&h1=322
http://sap.ittoolbox.com/nav/t.asp?t=448&p=448&h1=448
http://www.thespot4sap.com/
http://www.kabai.com/abaps/q.htm
http://www.geocities.com/mpioud/Abap_programs.html
http://www.sapgenie.com/abap/tips_and_tricks.htm
http://www.sapassist.com/code/d.asp?whichpage=1&pagesize=10&i=10&a=c&o=&t=&q=&qt=
For FAQ
http://www.sap-img.com/abap/more-than-100-abap-interview-faqs.htm
http://www.sapgenie.com/faq/abap.htm
BAPI-step by step
http://www.sapgenie.com/abap/bapi/example.htm
Weblog for receive email and processing it through ABAP
/people/thomas.jung3/blog/2004/09/09/receiving-e-mail-and-processing-it-with-abap--version-610-and-higher
For Logical database
http://help.sap.com/saphelp_46c/helpdata/en/9f/db9bed35c111d1829f0000e829fbfe/frameset.htm
very useful
http://help.sap.com/saphelp_46c/helpdata/EN/35/2cd77bd7705394e10000009b387c12/frameset.htm
Useful link to websites
http://www.hernangn.com.ar/sap.htm
Useful for background
http://www.sappoint.com/basis/bckprsng.pdf
http://help.sap.com/saphelp_nw04/helpdata/en/6f/08703713bf277ee10000009b38f8cf/frameset.htm
http://publib.boulder.ibm.com/infocenter/wbihelp/index.jsp?topic=/com.ibm.wbix_adapters.doc/doc/mysap4/sap4x41.htm
Table control in BDC
http://www.sap-img.com/abap/bdc-example-using-table-control-in-bdc.htm
For posting weblog,
/people/sap.user72/blog/2005/06/28/sdn-weblogs-making-it-easier
Dynamic Internal table -weblog in sdn
/people/subramanian.venkateswaran2/blog/2004/11/19/dynamic-internal-table
Smartforms
http://www.sap-basis-abap.com/sapsf001.htm
http://www.sap-press.com/downloads/h955_preview.pdf
http://www.ossincorp.com/Black_Box/Black_Box_2.htm
http://www.sap-img.com/smartforms/sap-smart-forms.htm
http://www.sap-img.com/smartforms/smartform-tutorial.htm
http://www.sapgenie.com/abap/smartforms.htm
How to trace smartform
http://help.sap.com/saphelp_47x200/helpdata/en/49/c3d8a4a05b11d5b6ef006094192fe3/frameset.htm
Workflow
http://www.sap-img.com/workflow/sap-workflow.htm
http://help.sap.com/saphelp_47x200/helpdata/en/a5/172437130e0d09e10000009b38f839/frameset.htm
For examples on WorkFlow...check the below link..
http://help.sap.com/saphelp_47x200/helpdata/en/3d/6a9b3c874da309e10000000a114027/frameset.htm
http://help.sap.com/printdocu/core/Print46c/en/data/pdf/PSWFL/PSWFL.pdf
http://help.sap.com/saphelp_47x200/helpdata/en/4a/dac507002f11d295340000e82dec10/frameset.htm
http://www.workflowing.com/id18.htm
http://www.e-workflow.org/
http://web.mit.edu/sapr3/dev/newdevstand.html
ALV
http://www.geocities.com/mpioud/Abap_programs.html
Mail
http://www.geocities.com/mpioud/Z_EMAIL_ABAP_REPORT.html
http://www.thespot4sap.com/Articles/SAP_Mail_SO_Object_Send.asp
http://www.sapdevelopment.co.uk/reporting/email/attach_xls.htm
Sending mail in background or spool mail
http://www.sap-basis-abap.com/sapac018.htm
BOM Explosion
/people/prakash.singh4/blog/2005/05/15/explode-boms-in-enterprise-portal-using-htmlb-tree--part-1-abap
BOM
http://help.sap.com/saphelp_erp2005/helpdata/en/ea/e9b7234c7211d189520000e829fbbd/frameset.htm
http://help.sap.com/saphelp_erp2005/helpdata/en/d1/2e4114a61711d2b423006094b9d648/frameset.htm
http://www.sap-img.com/sap-sd/sales-bom-implementation.htm
http://www.sap-basis-abap.com/sappp007.htm
OLE
http://www.sapgenie.com/abap/ole.htm
http://help.sap.com/saphelp_46c/helpdata/en/59/ae3f2e488f11d189490000e829fbbd/frameset.htm
ALVGRID with refresh
http://www.geocities.com/mpioud/Z_DEMO_ALV_REFRESH_BUTTON.html
For language setting and decimal separator
/people/horst.keller/blog/2004/11/16/abap-geek-7-150-babylonian-confusion
Oracle queries
http://sqlzoo.net/
To format SQL
http://www.sqlinform.com/
SCOT settings
http://www.sap-img.com/basis/basis-faq.htm
Status Icon [ALV,Table Control,Tab Strip]
http://www.sapdesignguild.org/resources/MiniSG-old/from_develop/norm_status_icons.htm#positioning_4
ALV Group Heading
http://www.sap-img.com/fu037.htm
For multiMedia
/people/thomas.jung3/blog/2005/05/11/using-classic-activex-controls-in-the-abap-control-framework
Uploading LOGO in SAP
http://www.sap-img.com/ts001.htm
LSMW
http://www.sap-img.com/sap-data-migration.htm
http://www.sapgenie.com/saptech/lsmw.htm
http://sapabap.iespana.es/sapabap/manuales/pdf/lsmw.pdf
http://www.sap.info/public/INT/int/glossary/int/glossaryletter/Word-17643ed1d6d658821_glossary/L#Word-17643ed1d6d658821_glossary
OOPS ALV
OOPS - Events.
Editable ALV
Tree
TabStrip
Multigrid
Check this for basic concepts of OOPS
https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/com.sap.km.cm.docs/library/webas/abap/abap code samples/abap objects/abap code sample to learn basic concept of object-oriented programming.doc
https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/com.sap.km.cm.docs/library/webas/abap/abap code samples/alv grid/abap code sample to display data in alv grid using object oriented programming.doc
Tabstrip
https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/com.sap.km.cm.docs/library/webas/abap/abap code samples/alv grid/abap code sample for tab strip in alv.pdf
Editable ALV
https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/com.sap.km.cm.docs/library/webas/abap/abap code samples/alv grid/abap code sample to edit alv grid.doc
Tree
http://www.sapdevelopment.co.uk/reporting/alv/alvtree/alvtree_usrint.htm
General Tutorial for OOPS
https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/com.sap.km.cm.docs/library/webas/abap/an easy reference for alv grid control.pdf
Function Module
http://www.geocities.com/victorav15/sapr3/abapfun.html
Smartforms
https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/com.sap.km.cm.docs/library/uuid/ccab6730-0501-0010-ee84-de050a6cc287
https://sdn.sap.com/irj/servlet/prt/portal/prtroot/com.sap.km.cm.docs/library/uuid/8fd773b3-0301-0010-eabe-82149bcc292e
https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/com.sap.km.cm.docs/library/uuid/3c5d9ae3-0501-0010-0090-bdfb2d458985
Table Control
https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/com.sap.km.cm.docs/documents/a1-8-4/table control in abap.pdf
regards
Arun

How to attempt production orders and get feedback by using IDocs

Hi,
I'm new new to SAP and R3 respectively mySAP. I need to know how to use IDocs (over file system) to attempt production orders to an extern application and how to get the feedback of the whole orders and single operations.
I found the IDoc-base-type "PPCC2RECORDER01" to send production orders. Is that the right base type for production orders?
(In consideration of compatibility and support me was recommend to avoid the old types OPERA2 and CONF21.)
What IDoc-types do I need to get feedback about a production order and its operations?
I hope someone is understanding my questions is able to help me. Please apologize my broken English.
Thanks!
Hannes

PROGRAM....... ZRCCLORDPROC
TITLE......... Production Odrer Idocs
AUTHOR........ Aveek Ghose
DATE WRITTEN.. 15/09/2006
R/3 RELEASE... 4.6C
=====================================================================*
COPIED FROM... N/A
DESCRIPTION...
*& Creation of production order IDOCs to a given selection
*& This program selects to an input given via the selection screen the *
*& corresponding production orders from the database. Then the function
*& module for creation of planned order idocs is called. *
*& In general this report is called from the report RCCLTRAN, but it *
*& can also be used for its own. *
=====================================================================*
PROGRAM TYPE.. Outbound Interface
DEV. CLASS.... ZPD1
LOGICAL DB.... N/A
=====================================================================*
SCREENS....... N/A
GUI TITLE..... N/A
GUI STATUS.... N/A
TRANSACTIONS.. N/A
USER EXITS.... N/A
=====================================================================*
CHANGE HISTORY *
Date By Correction Number & Brief Description Release
Tables / Structures
REPORT zrcclordproc
 NO STANDARD PAGE HEADING
 MESSAGE-ID ZCUST
 LINE-COUNT 65(0)
 LINE-SIZE 255.
INCLUDE RCORDO01. " PBO-Modules *
INCLUDE RCORDI01. " PAI-Modules *
INCLUDE RCORDF01. " FORM-Routines *
--> Global data
TYPE-POOLS: cloi.
include zprodata. "Types / constants for Orderselection
include zrcordtop. "Tables / Data for this report
include zrcordtop1.
include yrccl_constants.
TABLES : jcds,
 tvarv,
 zzzz_xref_data.
TYPES: BEGIN OF ty_date,
 aufnr TYPE aufnr,
 aedat TYPE aufaedat,
 aezeit TYPE co_chg_time,
 erdat TYPE auferfdat,
 erfzeit TYPE co_ins_time,
 loekz TYPE aufloekz,
 indicator(1) TYPE c,
 END OF ty_date.
DATA: is_enhancement type isu_ord_segments_determine.
DATA: itab_date TYPE STANDARD TABLE OF ty_date
 INITIAL SIZE 0 WITH HEADER LINE.
DATA: f_objnr TYPE j_objnr.
DATA: g_report_sub_head(72) TYPE c, "Sub-Header hold area
 g_report_head(72) TYPE c, "Header hold area
 g_run_date(72) TYPE c, "Holds message for Run date
 g_run_time(72) TYPE c. "Holds message for Run time
DATA:
f_old_date TYPE datum,
f_old_time TYPE uzeit,
f_continue(1) TYPE c.
END OF INSERTION DS001
--> Überschrift für sonstige Einstellungen
SELECTION-SCREEN SKIP 2.
SELECTION-SCREEN BEGIN OF BLOCK miscellaneous WITH FRAME.
SELECTION-SCREEN SKIP 1.
SELECTION-SCREEN COMMENT 1(30) text-001. "#EC
SELECTION-SCREEN SKIP 1.
*>> Logical system comes from Report RCCLTRANS
SELECTION-SCREEN BEGIN OF LINE.
SELECTION-SCREEN COMMENT 3(30) text-002.
SELECTION-SCREEN POSITION 35.
PARAMETERS opt_sys LIKE tbdlst-logsys.
SELECTION-SCREEN END OF LINE.
*>> Messagetype comes from Report RCCLTRANS
SELECTION-SCREEN BEGIN OF LINE.
SELECTION-SCREEN COMMENT 3(30) text-003.
SELECTION-SCREEN POSITION 35.
PARAMETERS mestyp LIKE tbdme-mestyp.
SELECTION-SCREEN END OF LINE.
*>> Messagetype comes from Report RCCLTRANS
SELECTION-SCREEN BEGIN OF LINE.
SELECTION-SCREEN COMMENT 3(30) text-004.
SELECTION-SCREEN POSITION 35.
PARAMETERS: p_date TYPE sydatum. "last run date
SELECTION-SCREEN END OF LINE.
*>> Messagetype comes from Report RCCLTRANS
SELECTION-SCREEN BEGIN OF LINE.
SELECTION-SCREEN COMMENT 3(30) text-005.
SELECTION-SCREEN POSITION 35.
PARAMETERS: p_time TYPE syuzeit. "last run time
SELECTION-SCREEN END OF LINE.
SELECTION-SCREEN END OF BLOCK MISCELLANEOUS.
*MOD-006
*>> Messagetype comes from Report RCCLTRANS
SELECTION-SCREEN BEGIN OF LINE.
SELECTION-SCREEN COMMENT 3(30) text-006.
SELECTION-SCREEN POSITION 35.
PARAMETERS: p_update AS CHECKBOX DEFAULT space.
SELECTION-SCREEN END OF LINE.
*MOD-006
*MOD-006
*>> Messagetype comes from Report RCCLTRANS
SELECTION-SCREEN BEGIN OF LINE.
SELECTION-SCREEN COMMENT 3(30) text-007.
SELECTION-SCREEN POSITION 32.
SELECT-OPTIONS: s_rundt FOR sy-datum NO-EXTENSION.
SELECTION-SCREEN END OF LINE.
*MOD-006
*MOD-006
*>> Messagetype comes from Report RCCLTRANS
SELECTION-SCREEN BEGIN OF LINE.
SELECTION-SCREEN COMMENT 3(30) text-008.
SELECTION-SCREEN POSITION 32.
SELECT-OPTIONS: s_runtm FOR sy-uzeit NO-EXTENSION.
SELECTION-SCREEN END OF LINE.
*MOD-006
**MOD-006
*SELECTION-SCREEN BEGIN OF LINE.
*SELECTION-SCREEN COMMENT 3(30) text-009.
*SELECTION-SCREEN POSITION 32.
*SELECT-OPTIONS: s_emat FOR zzzz_xref_data-z_in_value.
*SELECTION-SCREEN END OF LINE.
SELECTION-SCREEN END OF BLOCK miscellaneous.
**MOD-006
Write selected AUFPL numbers via ranges table to memory ?
PARAMETERS:
ordtomem TYPE cloi_x DEFAULT '' NO-DISPLAY. "X: yes
do not select from MARC, but use ranges tables directly. MK 4.0C
matnr_gl and werks_gl must have the same length.
PARAMETERS: no_sel TYPE c DEFAULT ' ' NO-DISPLAY.
--> Normal selection parameters for ORD comes from the logical db
*& Event START-OF-SELECTION
START-OF-SELECTION.
--> Select the ORD according to the selected
 MRP controller, Material, work center and plant
*MOD-006
Validate the last run date & Time
PERFORM validate_last_run_date_time.
*MOD-006
BEGIN OF INSERTION DS001
get the entry of the last program run
select single * for update from ycloidownlprot
 where logsys = OPT_SYS and
 downloadtype eq C_DOWNL_PROCESS_ORDERS.
if YCLOIDOWNLPROT-IN_PROGRESS eq CLOI_TRUE.
program is already running, do not allow to start again
 write : / text-004, YCLOIDOWNLPROT-USERNAME.
 exit.
endif.
YCLOIDOWNLPROT-MANDT = SY-MANDT.
YCLOIDOWNLPROT-LOGSYS = OPT_SYS.
YCLOIDOWNLPROT-START_DATE = SY-DATUM.
YCLOIDOWNLPROT-START_TIME = SY-UZEIT.
YCLOIDOWNLPROT-USERNAME = SY-UNAME.
YCLOIDOWNLPROT-DOWNLOADTYPE = C_DOWNL_PROCESS_ORDERS.
YCLOIDOWNLPROT-IN_PROGRESS = CLOI_TRUE.
insert or update entry (dependant if entry already exists)
MODIFY YCLOIDOWNLPROT.
COMMIT WORK.
CLEAR CREATED_MASTERIDOCS_PRO.
EXPORT CREATED_MASTERIDOCS_PRO TO MEMORY ID 'YLOI001'.
END OF INSERTION DS001
BEGIN OF INSERTION DS001
if not sscrfields-ucomm = 'ONLI'. mk zu 4.0
exit.
endif.
if s_dispo is initial and
 s_matnr is initial and
 s_arbpl is initial and
 s_werks is initial.
 exit.
endif.
Send only orders with type 40 - process orders
p_autyp = '40'.
END OF INSERTION DS001
*>> Put the ranges tabs back into matwrk list if no selection (NO_SEL)
IF no_sel = cloi_true.
 CLEAR t_matwrk_key. REFRESH t_matwrk_key.
 LOOP AT s_matnr.
 t_matwrk_key-matnr = s_matnr-low.
 READ TABLE s_werks INDEX sy-tabix.
 t_matwrk_key-werks = s_werks-low.
 APPEND t_matwrk_key.
 ENDLOOP.
 SORT t_matwrk_key BY matnr werks.
 DELETE ADJACENT DUPLICATES FROM t_matwrk_key.
delete duplicate duplicates from ranges table. Therfore sort by LOW
(HIGH is not used in this case).
 SORT s_matnr BY low.
 DELETE ADJACENT DUPLICATES FROM s_matnr.
 SORT s_werks BY low.
 DELETE ADJACENT DUPLICATES FROM s_werks.
ENDIF.
--> Determine which segments are selected in the message type
PERFORM ord_segments_determine
 USING mestyp
 CHANGING afpo_x
 jstk_x
 afab_x
 affl_x
 afvo_x
 kbed_x
 jstv_x
 resb_x
 kbeu_x
 afuv_x
 is_enhancement
 jstu_x.
Export the flags to the memory, because the following subroutine
must not have any parameters !!!
EXPORT affl_x
 afvo_x
 kbed_x
 resb_x
 kbeu_x
 afuv_x
 TO MEMORY ID 'LOI03'.
MK 19980326 enhanced selections on header/operation level
get selection profile for log system from customizing if available
SELECT SINGLE * FROM tcloi9 WHERE logsys = opt_sys.
if entry exists for the logical system
IF sy-subrc = 0.
if an selection profile for the order is entered, use it for selection
 IF NOT tcloi9-ord_selid IS INITIAL.
 p_selid = tcloi9-ord_selid.
 ENDIF.
 IF NOT tcloi9-ord_opr_selid IS INITIAL AND
 NOT afvo_x IS INITIAL AND NOT affl_x IS INITIAL.
 ord_opr_selid = tcloi9-ord_opr_selid.
 ENDIF.
ENDIF.
initialize control key table for selections
CALL FUNCTION 'CLOI_STEUS_GET'
 EXPORTING
 logsys_to_init = opt_sys
 IMPORTING
 no_entry_for_logsys = no_entry_for_logsys
 TABLES
 t_steus = t_steus
 EXCEPTIONS
 logsys_not_initialized = 1
 OTHERS = 2.
Write structure information into the memory
perform fill_memory_selobj.
-> import table with already sent orders
IMPORT gt_aufnrdone FROM MEMORY ID 'LOIAUFNRTAB'. "N599845
SORT gt_aufnrdone BY low. "N599845
--> Read header information
GET ioheader.
Check if material/plant combination is selected MK 4.0C
CLEAR check_flg.
IF no_sel = cloi_true.
 READ TABLE t_matwrk_key
 WITH KEY matnr = ioheader-matnr
 werks = ioheader-werks BINARY SEARCH.
 IF sy-subrc <> 0.
 check_flg = cloi_true.
 ENDIF.
ENDIF.
-> check if order was already sent
IF NOT gt_aufnrdone[] IS INITIAL. "N599845
 READ TABLE gt_aufnrdone WITH KEY "N599845
 low = ioheader-aufnr "N599845
 TRANSPORTING NO FIELDS "N599845
 BINARY SEARCH. "N599845
 IF sy-subrc = 0. "N599845
 -> order already sent
 check_flg = cloi_true. "N599845
 ENDIF. "N599845
ENDIF. "N599845
leave GET routine if check_flg is set.
CHECK check_flg IS INITIAL.
CLEAR t_afpo. REFRESH t_afpo.
CLEAR t_affl. REFRESH t_affl.
MOVE-CORRESPONDING ioheader TO t_afko.
GET ioheader LATE.
BEGIN OF INSERTION DS001
Check whether the process order has been changed since the last
run of the program
clear f_continue.
if the CHANGED date is greater than the last run or initial
IF IOHEADER-AEDAT GT F_OLD_DATE OR
 ( ioheader-aedat is initial and
 ioheader-aezeit is initial ).
if the CHANGED date is initial check the creation date
 if ioheader-aedat is initial.
if the creation date is greater than or equal to the date of the last
run, if it is equal the creation time must be later or equal to the
start time of the last run
 IF IOHEADER-ERDAT GT F_OLD_DATE OR
 ( IOHEADER-ERDAT EQ F_OLD_DATE AND
 IOHEADER-ERFZEIT GE F_OLD_TIME ).
 f_continue = 'X'.
 endif.
 else.
 f_continue = 'X'.
 endif.
if the CHANGED dat is not initial check it against the last run
ELSEIF IOHEADER-AEDAT EQ F_OLD_DATE AND
 IOHEADER-AEZEIT GE F_OLD_TIME.
 f_continue ='X'.
endif.
Aenderung 295/99 Selektions-Aenderung vom 26. August 99
Wenn Auftrag bereits techn. abgeschlossen ist, so darf kein IDOC
erzeugt werden, wenn Auftrag zum löschen vorgemerkt wird.
CONCATENATE 'OR' IOHEADER-AUFNR INTO F_OBJNR.
SELECT SINGLE * FROM JEST
 WHERE OBJNR = F_OBJNR
 AND STAT = 'I0045'.
IF JEST-INACT EQ SPACE AND SY-SUBRC EQ 0.
 SELECT * FROM JCDS WHERE OBJNR EQ F_OBJNR AND
 STAT EQ 'I0045' AND
 INACT EQ SPACE.
letzte Aenderung des Status TABG wird geprueft Beg. WA 354/99
 ENDSELECT.
IF ( F_OLD_DATE GT JCDS-UDATE OR " Beg JB_02
 ( F_OLD_DATE EQ JCDS-UDATE AND
 F_OLD_TIME GT JCDS-UTIME ) ) AND " End JB_02
 SY-SUBRC EQ 0.
 CLEAR F_CONTINUE.
 ENDIF.
ENDIF.
Ende 295/99
check f_continue eq 'X'.
END OF INSERTION DS001
t_afko-t_afpo = t_afpo[].
t_afko-t_jstk = t_jstk[].
t_afko-t_affl = t_affl[].
t_afko-t_afab = t_afab[].
APPEND t_afko.
IF jstk_x = cloi_x.
 t_objnr-objnr = ioheader-objnr.
 APPEND t_objnr.
ENDIF.
*---> Remember the orders that are already selected for the global
 selection parameters
IF ordtomem = cloi_x. "write order numbers to memory
 t_aufnr_range_done-sign = 'I'.
 t_aufnr_range_done-option = 'NE'.
 t_aufnr_range_done-low = ioheader-aufpl.
 APPEND t_aufnr_range_done.
ENDIF.
*---> Remember the orders internal/external keys for AFAB (relationship)
IF afab_x = cloi_x.
 MOVE-CORRESPONDING ioheader TO t_aufpl_aufnr.
 APPEND t_aufpl_aufnr.
ENDIF.
check afpo_x = cloi_x.
GET ioitem.
BEGIN OF INSERTION DS001
Check whether the process order has been changed since the last
run of the program
CLEAR F_CONTINUE.
if the CHANGED date is greater than the last run or initial
IF IOHEADER-AEDAT GT F_OLD_DATE OR
 ( ioheader-aedat is initial and
 ioheader-aezeit is initial ).
if the CHANGED date is initial check the creation date
 if ioheader-aedat is initial.
if the creation date is greater than or equal to the date of the last
run, if it is equal the creation time must be later or equal to the
start time of the last run
 IF IOHEADER-ERDAT GT F_OLD_DATE OR
 ( IOHEADER-ERDAT EQ F_OLD_DATE AND
 IOHEADER-ERFZEIT GE F_OLD_TIME ).
 f_continue = 'X'.
 endif.
 else.
 f_continue = 'X'.
 endif.
if the CHANGED date is not initial check it against the last run
ELSEIF IOHEADER-AEDAT EQ F_OLD_DATE AND
 IOHEADER-AEZEIT GE F_OLD_TIME.
 f_continue ='X'.
endif.
Aenderung 295/99 Selektions-Aenderung vom 26. August 99
Wenn Auftrag bereits techn. abgeschlossen ist, so darf kein IDOC
erzeugt werden, wenn Auftrag zum löschen vorgemerkt wird.
CONCATENATE 'OR' IOHEADER-AUFNR INTO F_OBJNR.
SELECT SINGLE * FROM JEST
 WHERE OBJNR = F_OBJNR
 AND STAT = 'I0045'.
IF JEST-INACT EQ SPACE AND SY-SUBRC EQ 0.
 SELECT * FROM JCDS WHERE OBJNR EQ F_OBJNR AND
 STAT EQ 'I0045' AND
 INACT EQ SPACE.
letzte Aenderung des Status TABG wird geprueft
 ENDSELECT.
IF ( F_OLD_DATE GT JCDS-UDATE OR " Beg JB_02
 ( F_OLD_DATE EQ JCDS-UDATE AND
 F_OLD_TIME GT JCDS-UTIME ) ) AND " End JB_02
 SY-SUBRC EQ 0.
 CLEAR F_CONTINUE.
 ENDIF.
ENDIF.
Ende 295/99
check f_continue eq 'X'.
END OF INSERTION DS001
IF afpo_x = cloi_x.
 MOVE-CORRESPONDING ioitem TO t_afpo.
 APPEND t_afpo.
ENDIF.
Put matnr and ltrmi in a help structure, which later goes to t_afpo
IF ioitem-posnr = '0001'.
 MOVE-CORRESPONDING ioitem TO help_afpo.
 APPEND help_afpo.
put PSP element (internal key) into order header. Unique for positions
 IF t_afko-pspel IS INITIAL.
 t_afko-pspel = ioitem-projn.
 ENDIF.
ENDIF.
CHECK affl_x = cloi_x.
GET iosequen.
CLEAR t_afvo. REFRESH t_afvo.
MOVE-CORRESPONDING iosequen TO t_affl.
GET iosequen LATE.
t_affl-t_afvo = t_afvo[].
APPEND t_affl.
CHECK afvo_x = cloi_x.
GET iooper.
CLEAR t_kbed. REFRESH t_kbed.
CLEAR t_afuv. REFRESH t_afuv.
CLEAR t_resb. REFRESH t_resb.
MOVE-CORRESPONDING iooper TO t_afvo.
"Temporary storing of operation information if for a phase
"the corresponding operation has is needed
MOVE-CORRESPONDING iooper TO t_aufpl_aplzl_vornr.
APPEND t_aufpl_aplzl_vornr.
check, if selection profile (if exists) for the operation is ok
IF NOT ord_opr_selid IS INITIAL.
 CALL FUNCTION 'STATUS_CHECK_BY_SELSCHEM'
 EXPORTING
 objnr = iooper-objnr
 selid = ord_opr_selid
 IMPORTING
 fullfill = status_ok
 EXCEPTIONS
 no_stat_tab = 1
 no_stat_scheme = 2
 OTHERS = 3.
 IF sy-subrc <> 0.
 status_ok = cloi_x.
 ENDIF.
ELSE.
 status_ok = cloi_x.
ENDIF.
check if control key (STEUS) should not be selected.
control_key_ok = cloi_x.
IF no_entry_for_logsys IS INITIAL.
 READ TABLE t_steus WITH KEY
 steus = iooper-steus BINARY SEARCH.
 IF sy-subrc <> 0.
 CLEAR control_key_ok.
 ENDIF.
ENDIF.
CHECK NOT status_ok IS INITIAL.
CHECK NOT control_key_ok IS INITIAL.
GET iooper LATE.
t_afvo-t_kbed = t_kbed[].
t_afvo-t_afuv = t_afuv[].
t_afvo-t_resb = t_resb[].
APPEND t_afvo.
IF jstv_x = cloi_x.
 t_objnr-objnr = iooper-objnr.
 APPEND t_objnr.
ENDIF.
CHECK kbed_x = cloi_x.
GET ioopcap.
MOVE-CORRESPONDING ioopcap TO t_kbed.
APPEND t_kbed.
CHECK resb_x = cloi_x.
GET ioopcomp.
do not transfer RESB entries with deletion flag
CHECK ioopcomp-xloek IS INITIAL.
MOVE-CORRESPONDING ioopcomp TO t_resb.
APPEND t_resb.
CHECK afuv_x = cloi_x.
GET iosoper.
CLEAR t_kbeu. REFRESH t_kbeu.
MOVE-CORRESPONDING iosoper TO t_afuv.
check if control key (STEUS) should not be selected.
control_key_ok = cloi_x.
IF no_entry_for_logsys IS INITIAL.
 READ TABLE t_steus WITH KEY
 steus = iooper-steus BINARY SEARCH.
 IF sy-subrc <> 0.
 CLEAR control_key_ok.
 ENDIF.
ENDIF.
CHECK NOT control_key_ok IS INITIAL.
GET iosoper LATE.
t_afuv-t_kbeu = t_kbeu[].
APPEND t_afuv.
IF jstv_x = cloi_x.
 t_objnr-objnr = iosoper-objnr.
 APPEND t_objnr.
ENDIF.
CHECK kbeu_x = cloi_x.
GET iosocap.
MOVE-CORRESPONDING iosocap TO t_kbeu.
APPEND t_kbeu.
*& Event END-OF-SELECTION
END-OF-SELECTION.
*MOD-006
DATA: itab_matnr TYPE zzzz_xref_data OCCURS 0.
DATA: l_wa_matnr TYPE zzzz_xref_data.
DATA: l_wa_matnr_value TYPE zzzz_xref_data-z_in_value.
DATA: l_wa_afko TYPE cloi_afko_struct.
SELECT *
FROM zzzz_xref_data
APPENDING TABLE itab_matnr
WHERE trans_id = 'ZELCUSMATLOOKUP' AND
 ( z_in_value IN s_matnr OR
 z_out_value IN s_matnr ).
IF sy-subrc = 0.
 LOOP AT ITAB_MATNR INTO L_WA_MATNR.
 L_WA_MATNR_VALUE = L_WA_MATNR-z_OUT_VALUE.
 S_MATNR-LOW = L_WA_MATNR_VALUE.
 S_MATNR-SIGN = 'I'.
 S_MATNR-OPTION = 'EQ'.
 APPEND S_MATNR.
 ENDLOOP.
 DELETE itab_matnr WHERE NOT in_value IN s_emat.
 SORT itab_matnr BY out_value.
ENDIF.
CLEAR: l_wa_matnr.
**MOD-010
Data which is not in the material lookup table but in the T_AFKO.
LOOP AT t_afko INTO l_wa_afko.
 READ TABLE S_MATNR WITH KEY LOW = L_WA_AFKO-MATNR BINARY SEARCH.
 READ TABLE itab_matnr INTO l_wa_matnr
 WITH KEY z_out_value = l_wa_afko-matnr BINARY SEARCH.
 IF sy-subrc NE 0.
 l_wa_afko-rgekz = 'X'.
 MODIFY t_afko FROM l_wa_afko TRANSPORTING rgekz.
 ENDIF.
 IF NOT P_DATE IS INITIAL.
 IF T_AFKO-GSTRP < p_date OR
 ( T_AFKO-GSTRP = p_date AND
 T_AFKO-GSUZP > p_time ).
 L_WA_AFKO-RGEKZ = 'X'.
 MODIFY T_AFKO FROM L_WA_AFKO TRANSPORTING RGEKZ.
 ENDIF.
 ENDIF.
ENDLOOP.
Delete Data which is not in the material lookup
table but in the T_AFKO.
DELETE t_afko WHERE rgekz = 'X'.
*MOD-010
*MOD-006
BEGIN OF INSERTION DS001
DATA: l_wa_itab_date TYPE ty_date.
Check whether the process order has been changed since the last
run of the program
CLEAR f_continue.
IF NOT t_afko IS INITIAL.
 SELECT aufnr aedat aezeit erdat erfzeit loekz
 INTO TABLE itab_date
 FROM aufk
 FOR ALL ENTRIES IN t_afko
 WHERE aufnr = t_afko-aufnr.
 IF sy-subrc = 0.
 IF NOT p_date IS INITIAL.
 CLEAR: itab_date.
Check whether the process order has been changed since the last
run of the program
 LOOP AT itab_date INTO l_wa_itab_date.
if the CHANGED date is greater than the last run or initial
 IF l_wa_itab_date-aedat GT p_date OR
 ( l_wa_itab_date-aedat IS INITIAL AND
 l_wa_itab_date-aezeit IS INITIAL ).
if the CHANGED date is initial check the creation date
 IF l_wa_itab_date-aedat IS INITIAL.
if the creation date is greater than or equal to the date of the last
run, if it is equal the creation time must be later or equal to the
start time of the last run
 IF l_wa_itab_date-erdat GT p_date OR
 ( l_wa_itab_date-erdat EQ p_date AND
 l_wa_itab_date-erfzeit GE p_time ).
 f_continue = 'X'.
 ELSE.
 l_wa_itab_date-indicator = 'X'.
 MODIFY itab_date FROM l_wa_itab_date TRANSPORTING indicator.
 ENDIF.
 ELSE.
 f_continue = 'X'.
 ENDIF.
if the CHANGED dat is not initial check it against the last run
 ELSEIF l_wa_itab_date-aedat EQ p_date AND
 l_wa_itab_date-aezeit GE p_time.
 f_continue ='X'.
 ELSE.
 l_wa_itab_date-indicator = 'X'.
 MODIFY itab_date FROM l_wa_itab_date TRANSPORTING indicator.
 ENDIF.
 ENDLOOP.
*MOD-006
ELSE.
 CLEAR: ITAB_DATE.
 LOOP AT ITAB_DATE INTO L_WA_ITAB_DATE.
if the CHANGED date is greater than the last run or initial
 IF L_WA_ITAB_DATE-AEDAT GT P_RUNDT OR
 ( L_WA_ITAB_DATE-aedat is initial and
 L_WA_ITAB_DATE-aezeit is initial ).
if the CHANGED date is initial check the creation date
 if l_wa_itab_date-aedat is initial.
if the creation date is greater than or equal to the date of the last
run, if it is equal the creation time must be later or equal to the
start time of the last run
 IF L_WA_ITAB_DATE-ERDAT GT P_RUNDT OR
 ( L_WA_ITAB_DATE-ERDAT EQ P_RUNDT AND
 L_WA_ITAB_DATE-ERFZEIT GE S_RUNTM-LOW OR
 L_WA_ITAB_DATE-ERFZEIT LE S_RUNTM-HIGH ).
 f_continue = 'X'.
 else.
 l_wa_itab_date-indicator = 'X'.
 MODIFY ITAB_DATE FROM L_WA_ITAB_DATE
 TRANSPORTING INDICATOR.
 endif.
 else.
 f_continue = 'X'.
 endif.
if the CHANGED dat is not initial check it against the last run
 ELSEIF L_WA_ITAB_DATE-AEDAT EQ P_RUNDT AND
 L_WA_ITAB_DATE-AEZEIT GE S_RUNTM-LOW.
 f_continue ='X'.
 ELSE.
 l_wa_itab_date-indicator = 'X'.
 MODIFY ITAB_DATE FROM L_WA_ITAB_DATE
 TRANSPORTING INDICATOR.
 endif.
 ENDLOOP.
*MOD-006
 ENDIF.
 ENDIF.
ENDIF.
DELETE ITAB_DATE WHERE INDICATOR = 'X'.
*MOD-006
CLEAR: itab_date.
IF s_rundt-high IS INITIAL AND NOT s_rundt IS INITIAL.
 s_rundt-high = sy-datum.
ENDIF.
LOOP AT itab_date INTO l_wa_itab_date.
 IF NOT s_rundt IS INITIAL.
if the CHANGED date is greater than the last run or initial
 IF ( l_wa_itab_date-aedat IS INITIAL AND
 l_wa_itab_date-aezeit IS INITIAL ).
if the CHANGED date is initial check the creation date
 IF l_wa_itab_date-aedat IS INITIAL.
if the creation date is greater than or equal to the date of the last
run, if it is equal the creation time must be later or equal to the
start time of the last run
 IF ( l_wa_itab_date-erdat GT s_rundt-low AND
 l_wa_itab_date-erfzeit GT s_runtm-low ) AND
 ( l_wa_itab_date-erdat LT s_rundt-high AND
 l_wa_itab_date-erfzeit LT s_runtm-high ).
 f_continue = 'X'.
 ELSE.
 l_wa_itab_date-indicator = 'X'.
 MODIFY itab_date FROM l_wa_itab_date
 TRANSPORTING indicator.
 ENDIF.
 ELSE.
 f_continue = 'X'.
 ENDIF.
if the CHANGED dat is not initial check it against the last run
 ELSEIF ( l_wa_itab_date-aedat GE s_rundt-low AND
 l_wa_itab_date-aezeit GE s_runtm-low ) AND
 ( l_wa_itab_date-aedat LE s_rundt-high AND
 l_wa_itab_date-aezeit LE s_runtm-high ).
 f_continue ='X'.
 ELSE.
 l_wa_itab_date-indicator = 'X'.
 MODIFY itab_date FROM l_wa_itab_date
 TRANSPORTING indicator.
 ENDIF.
 ENDIF.
ENDLOOP.
DELETE itab_date WHERE indicator = 'X'.
*MOD-006
**MOD-006
LOOP AT t_afko INTO l_wa_afko.
 READ TABLE itab_date INTO l_wa_itab_date
 WITH KEY aufnr = l_wa_afko-aufnr BINARY SEARCH.
 IF sy-subrc NE 0.
 l_wa_afko-rgekz = 'X'.
 MODIFY t_afko FROM l_wa_afko TRANSPORTING rgekz.
 ENDIF.
ENDLOOP.
DELETE t_afko WHERE rgekz = 'X'.
**MOD-006
-> initialize logical data base to reduce memory consumption
PERFORM ldb_process_init(sapdbioc)
 CHANGING
 lv_subrc.
--> add information to the order structure that is not
 selected via logical database:
 - if AFVO-entry is a phase (phflg) --> fill field for
 corresponding operation number (PVZNR)
 The internal node number (aplzl) of the corresponding operation
 is in field PVZKN of the phase
 - relationship information: E1AFABL
 especially: select external numbers for the used
 internal numbers in the table AFAB
 - status information of the order header: E1JSTKL
 - status information of the operation: E1JSTVL
--> Put matnr and ltrmi in the table t_afko
SORT t_afko BY aufnr.
LOOP AT help_afpo.
 READ TABLE t_afko WITH KEY aufnr = help_afpo-aufnr
 ASSIGNING -gltri = help_afpo-ltrmi.
 ENDIF.
ENDLOOP.
--> Select entries for order and operation status
IF NOT t_objnr[] IS INITIAL.
 SELECT objnr stat FROM jest INTO TABLE t_jest2
 FOR ALL ENTRIES IN t_objnr
 WHERE objnr = t_objnr-objnr
 AND inact <> 'X'.
ENDIF.
--> Select entries for relationships from afab for all orders
 into table t_afab_tmp
SORT t_aufpl_aplzl_vornr BY aufpl aplzl.
IF afab_x = cloi_x AND NOT t_aufpl_aufnr[] IS INITIAL.
-> select afab data
 SELECT * FROM afab INTO TABLE t_afab_tmp
 FOR ALL ENTRIES IN t_aufpl_aufnr
 WHERE aufpl_vor = t_aufpl_aufnr-aufpl.
 SELECT * FROM afab APPENDING TABLE t_afab_tmp
 FOR ALL ENTRIES IN t_aufpl_aufnr
 WHERE aufpl_nch = t_aufpl_aufnr-aufpl.
 SORT t_afab_tmp
 BY aufpl_vor aplzl_vor aufpl_nch aplzl_nch aobar mimax.
 DELETE ADJACENT DUPLICATES FROM t_afab_tmp
 COMPARING aufpl_vor aplzl_vor aufpl_nch aplzl_nch aobar mimax.
-> read external order numbers out of data base
 CLEAR t_aufpl. REFRESH t_aufpl.
 LOOP AT t_afab_tmp ASSIGNING -aufpl_nch.
 COLLECT t_aufpl.
 ENDLOOP.
 CLEAR t_aufpl_aufnr. REFRESH t_aufpl_aufnr.
 IF NOT t_aufpl[] IS INITIAL.
 SELECT aufpl aufnr FROM afko INTO TABLE t_aufpl_aufnr
 FOR ALL ENTRIES IN t_aufpl
 WHERE aufpl = t_aufpl-aufpl.
 SORT t_aufpl_aufnr BY aufpl.
 ENDIF.
-> add order numbers to afab data
 LOOP AT t_afab_tmp ASSIGNING -aufnr_nch = t_aufpl_aufnr-aufnr.
 ENDIF.
 ENDLOOP.
-> read operation numbers out of data base
 CLEAR t_aufpl_aplzl. REFRESH t_aufpl_aplzl.
 LOOP AT t_afab_tmp ASSIGNING -aplzl_nch.
 COLLECT t_aufpl_aplzl.
 ENDLOOP.
 IF NOT t_aufpl_aplzl[] IS INITIAL.
 SELECT aufpl aplzl vornr FROM afvc
 APPENDING TABLE t_aufpl_aplzl_vornr
 FOR ALL ENTRIES IN t_aufpl_aplzl
 WHERE aufpl = t_aufpl_aplzl-aufpl
 AND aplzl = t_aufpl_aplzl-aplzl.
 SORT t_aufpl_aplzl_vornr BY aufpl aplzl.
 ENDIF.
-> add operation numbers to afab data
 LOOP AT t_afab_tmp ASSIGNING -vornr_nch = t_aufpl_aplzl_vornr-vornr.
 ENDIF.
 ENDLOOP.
ENDIF. "afab_x
--> fill AFAB (relationship information) and status information
SORT t_aufpl_aufnr BY aufnr.
LOOP AT t_afko ASSIGNING .
-> fill order head status information
 IF jstk_x = cloi_x.
 CLEAR t_jstk. REFRESH t_jstk.
 LOOP AT t_jest2 INTO wa_tjest2 WHERE objnr = -t_jstk = t_jstk[].
 ENDIF.
-> fill afab information
 IF afab_x = cloi_x.
 CLEAR t_aufpl_aufnr.
 READ TABLE t_aufpl_aufnr WITH KEY
 aufnr = -t_afab = t_afab[].
 ENDIF.
-> fill operation and suboperation status information
 IF jstv_x = cloi_x OR afvo_x = cloi_x.
 LOOP AT .
 -> read status information of suboperation
 IF jstu_x = cloi_x.
 LOOP AT -t_jstu = t_jstu[].
 ENDLOOP.
 ENDIF.
 -> read status information of operation
 IF jstv_x = cloi_x.
 CLEAR t_jstv. REFRESH t_jstv.
 LOOP AT t_jest2 INTO wa_tjest2 WHERE objnr = -t_jstv = t_jstv[].
 ENDIF.
 -> Read operation for a phase
 IF NOT -pvznr = t_aufpl_aplzl_vornr-vornr.
 ENDIF.
 ENDIF.
 ENDLOOP.
 ENDLOOP.
 ENDIF.
-> collect order numbers
 CLEAR wa_aufnrdone.
 wa_aufnrdone-low = -aufnr.
 APPEND wa_aufnrdone TO lt_aufnrdone.
ENDLOOP.
-> append collected order numbers to global table
APPEND LINES OF lt_aufnrdone TO gt_aufnrdone.
EXPORT gt_aufnrdone TO MEMORY ID 'LOIAUFNRTAB'.
-> free large tables
CLEAR t_jest2. REFRESH t_jest2.
CLEAR t_afab_tmp. REFRESH t_afab_tmp.
CLEAR t_aufpl. REFRESH t_aufpl.
CLEAR t_aufpl_aufnr. REFRESH t_aufpl_aufnr.
CLEAR t_aufpl_aplzl. REFRESH t_aufpl_aplzl.
CLEAR t_aufpl_aplzl_vornr. REFRESH t_aufpl_aplzl_vornr.
-> create idocs
CALL FUNCTION 'CLOI_MASTERIDOC_CREATE_LOIPRO'
 EXPORTING
 opt_sys = opt_sys
 message_type = mestyp
 TABLES
 order_data = t_afko
 EXCEPTIONS
 OTHERS = 1.
-> export already selected order numbers via ranges tab to memory
EXPORT t_aufnr_range_done TO MEMORY ID 'LOI002'.
**MOD-006
IMPORT created_masteridocs_pro FROM MEMORY ID 'YLOI001'.
ycloidownlprot-end_date = sy-datum.
ycloidownlprot-end_time = sy-uzeit.
ycloidownlprot-idocs_selected = created_masteridocs_pro.
ycloidownlprot-in_progress = cloi_false.
insert or update entry (dependant if entry already exists)
MODIFY ycloidownlprot.
COMMIT WORK.
MESSAGE i967(z001) WITH created_masteridocs_pro.
**MOD-006
Update last run date and time
IF p_update = 'X'.
 PERFORM update_last_run.
ELSE.
MESSAGE s000 WITH text-022.
 "Last Run Date and Last Run Time not updated
 LEAVE LIST-PROCESSING.
ENDIF.
INCLUDE rcordf01.
*& Form validate_last_run_date_time
 text
--> p1 text
<-- p2 text
*FORM validate_last_run_date_time.
IF p_date IS INITIAL OR
 p_time IS INITIAL.
 IF sy-batch IS INITIAL.
 MESSAGE s000 WITH text-017.
 "Last Run date & Last Run Time can not be blank
 LEAVE LIST-PROCESSING.
 ELSE.
 MESSAGE e000 WITH text-017.
 "Last Run date & Last Run Time can not be blank
 ENDIF.
ENDIF.
*ENDFORM. " validate_last_run_date_time
*& Form update_last_run
 text
--> p1 text
<-- p2 text
FORM update_last_run.
CONSTANTS:
 l_c_name TYPE rvari_vnam VALUE 'Z_PROC_DATE',
 l_c_name1 TYPE rvari_vnam VALUE 'Z_PROC_TIME',
 l_c_type TYPE rsscr_kind VALUE 'P',
 l_c_numb TYPE tvarv_numb VALUE '0000'.
Update last run date
UPDATE tvarv SET low = sy-datum
 WHERE name = l_c_name AND
 type = l_c_type AND
 numb = l_c_numb.
IF sy-subrc = 0.
 COMMIT WORK.
ELSE.
 ROLLBACK WORK.
 g_run_date = text-015. "#EC
 "Updation of TVARV table failed for ZLAST_RUN_DATE. Update manually
ENDIF.
Update last run time
UPDATE tvarv SET low = sy-uzeit
 WHERE name = l_c_name1 AND
 type = l_c_type AND
 numb = l_c_numb.
IF sy-subrc = 0.
 COMMIT WORK.
ELSE.
 ROLLBACK WORK.
 g_run_time = text-016. "#EC
 "Updation of TVARV table failed for ZLAST_RUN_TIME. Update manually
ENDIF.
ENDFORM. " update_last_run

Message type and IDoc type to update a sales order

I can create sales order at WE19 by the message type SALESORDER_CREATEFROMDAT2 and IDoc type SALESORDER_CREATEFROMDAT202 . Can I use the same message type and IDoc type to update a sales document (sales order) and also how can I do (I mean, which structures should I use; at E1BPSDHD1X - UPDATEFLAG what should I enter? Put an X to update a document or etsc?)? I enter the "E1BPSDHD1X - UPDATEFLAG" as X, "E1BP_SENDER - LOG_SYSTEM", "E1BPSDITM - ITM_NUMBER", " E1BPSDITM - MATERIAL", "E1BPPARNR - PARTN_ROLE", "E1BPPARNR - PARTN_NUMB" and "E1BPSCHDL - REQ_QTY". The sales order quantity is at "E1BPSCHDL - REQ_QTY" and it is the field that I want to update. When I look at the transaction code BD87, I see the status text as "Enter a document number between 0005000000 and 0005999999". I cannot update the order. How can I update it? Canybody explain me in a detailed manner?
Thanks in advance....
Edited by: Hikmet Akcali on Oct 21, 2009 4:00 PM

At the IDoc type pop-up selection, there are 3 types. These are: ORD_ID01, ORDERS05 and /NFM/ORDERS05. SAP system component version is SAP ECC 6.0 . I choose ORD_ID01. There are structures EDI_Z1, EDI_Z3, EDI_Z5, EDI_Z9 and EDI_Z53. Where should I enter the number of the sales document to be updated? Also, which function module should I choose?
Edited by: Hikmet Akcali on Oct 21, 2009 5:34 PM

Quantity Mismatched in Sales Order and it's corresponding Order's IDOC

Hi SAP experts,
In an ORDERS IDOC, conversion is done from EACH'S to CASES. ( INBOUND PROCESS, Message type - ORDERS, Basic type - ORDERS04 )
For e.g.: In a Sales Order, If 432 EACH'S are placed, it will be converted into 36 CASES in the IDOC (Here 1 Case = 12 Each's)
But in Sales Order it shows as 36 EACH'S (which is wrong) and In the IDOC it shows as 36 CASES (which is correct)
The Conversion has been done correctly from Each's to Cases. But don't know how this problem occurred for this document alone.
It should be 432 Each's in the Sales Order, Instead of 36 Each's...!!!
This problem is for only one Document number dated on ' 28th March 2011 '. It's working correctly again till date without any problem.
any idea to solve this single error guys?
<removed by moderator>
Regards,
Mano.
Edited by: Thomas Zloch on Apr 26, 2011 8:21 PM - urgency normalized

Hi Mano,
How to control the modifications? I suggest you to create a report to control this modifications. For instance use the report RVSCD100 as a template and create your own z* with a range of documents and filtering the fields that you want to control. Other possibility is use the standard report RSSCD100. One suggestion, is to have isolated this kind of SO in an specific range of numbers.
Nevertheless, if the problem is always with the same customer and material, check them and compare with other pair that works right.
For the value for STAMNO. If you are working in WE19 and create a new IDOC using other as a template, the system replies with a warning message. If you create the IDOC the system store in EDIDS the message (type, number, etc..). You can see it in tcode SE91 (ie: message i157(ea) with...).
I hope this helps you
Regards
Eduardo
Edited by: E_Hinojosa on Apr 29, 2011 9:45 AM

Creation of Sales Order and Service Contract from Inbound IDOC

Hi Experts,
My requirement is to create a Sales Order as well as a Service Contract from one Inbound IDOC. I am getting the Inbound IDOC from a third Party. The message type is ORDERS and Basic Type is ORDERS02. How ever i am using an extension type IDOC which carries all the required data for Sales Order and Service Contract. My requirement is like, to create a Sales Order first.
I have created a Z FM which is attached to the Process Code and subsequently to the message type. Inside the FM i an calling FM 'IDOC_INPUT_ORDERS' for creation of Sales Order. After that i am changing the IDOC data for the Document Type. I am changing the document type which is responsible for Contract Creation.
Then I am again calling the FM 'IDOC_INPUT_ORDERS' for creation of Contract with the help of IDOC data. But here the Contract is not getting created. It's getting failed during the Batch input session.
I need to solve this problem as soon as possible. Please help me. If there are any other options also please share.
Thanks in Advance.
Regards,
Priyabrata

Actually there is problem with BDCDATA. Inside the FM it's calling transaction with help of BDCDATA. If i am creating a Sales order or contract alone its creating successfully. But when i am trying to create both, it's retuning sy-subrc '1001' after calling the transaction on the second attempt. Is there any problem with BDCDATA like we can't handle with less time gap? Please help and give your inputs.
Regards,
Priyabrata

IDOC for Creation of Production order and also adding components

Hi ,
I have a requirement like I get the data from a 3rd party system and using that i have to create production orders and also should be able to add more materials in COMPONENTS part of that Production order. I was looking for a BAPI which can handle this process.
And also can any one help me by letting me know is there any Message type available for handling this process of Production order creation and Adding extyra components to it.
I have a message type LOIPRO (for Production Order) and associated function modle CLOI_MASTERIDOC_CREATE_LOIPRO for creation of master IDoc, but not sure can i handle the Components part in this.
Please do send replies ASAP, its very urgent.
Or else atleast suggest me the other ways of doing this .
Also send me any BDC program if anyone has already developed for this.
Thanks
Kumar
Edited by: Phani Kumar Peddagopu on Mar 19, 2008 6:56 PM

Resolved .

Want to see combination of Purchase Order and A/P report at material level

Hello,
Anyone familiar with an InfoProvider that will show a combination of Purchase Order and A/P data combined?
I'm specifically looking for a source that includes the PO information at the Vendor / Material level with order value and quantity at the time the PO was created AND accounts payable data at the Vendor / Material level with the invoiced amount and quantity (which may vary for the PO amounts).
Thank you,
Jim

Hi
Have you seen all of the follwoing datasources......
http://help.sap.com/saphelp_nw04/helpdata/en/df/fbb0d62f3a794d98d23609d17e1610/frameset.htm
Hope this helps
Regards
N Ganesh

Production Order for a material without BOM and Routing

Is it possible to create a production order for a given material without routing and BOM, I know we can
create a production order for a material without a BOM (with a default routing) just wanted to check with
the above criteria
Thanks in Advance!!

Members:
Thank you for your valuable replies and time
Santosh:
Tried what you have mentioned, but system still picks up a default routing
Kaushik:
Maintained Default values in OPJG for the given order type, but system still picks up
default routing
Mangalraj:
have no issue in creating a production order without a BOM, but I am trying to see
is there a way where I can create a production order without a BOM and routing (not
even default operation )
Any suggestions on how to create a production order for a material without a BOM
and routing (not even default one )

Make to order and stock both in one material with consignment

Hi Seniors
FERT Material = XYZ which is being used for Make to Order and Make to stock both.
In case of make to stock scenario from GR u2013 101 and PGI made @ std price. At the time of Consignment 631 mvt. No accounting document is generated. As per my knowledge its fine. No issue.
In case of Make to order scenario for above material.
Q.1   At the time of goods receipt (101 Mvt) from production order, accounting document is generated at the rate of Per unit target cost of production order and no variance shown on production order. Why not accounting document is created at Std price of Material?
Q.2 At the the time of consignment an accounting document generated with following entry.
    Finished Goods Inventory      Dr
    Price difference                   Dr
                    Finish Goods Inventory Cr
Why accounting document is generated at the time of consignment in case of make to order scenario? Pls confirm is this a sap standard behavour or anything wrong with me. As I told earlier that in case of make to stock when we make 631 mvt there is no accounting document generated.
Note: My standard price is on the base of mix costing using two production versions. Every time we create production order in each version.
Regards
Imdad

Hi Imdad
Q1: Why not accounting document is created at Std price of Material?
Check your req class... There is a Field called "Valuation"... your valuation depends on whether you select M or A there... You can decide to valuate based on CK11N std cost estimate or based on Sales order cost estimate / Prod order cost estimate
So, in a nut shell, you can configure the system to generate acc doc at CK11N Std cost also
Q2. Why accounting document is generated at the time of consignment in case of make to order scenario?
In my opinion, your MTO stock is maintained in Table EBEW.. Pls check that... WHen you do GR from Prod order, it resides in EBEW table..
However, when you send it as a cons stock, the link to sales order is lost and your stock is no longer a MTO stock.. Hence, it is valuated at CK11N Std Cost.... If there is a diff between CK11N cost and GR Price, then PRD is generated... Thats why you are seeing PRD in your case
BR, Ajay M

Differnt material in order and idoc

Similar Messages

Maybe you are looking for