EDI information
hi,
i have interview for edi position.
the requirement is edi for order to cash cycle.
I am abap developer with some knowledge in ale and IDOC.
but i am new for edi .
so if any one has sny material for this scenario then it will be help ful for me.
Thanks,
Jigar
Hi Jigar,
Please check this online documents for ALE and IDoc.
http://help.sap.com/printdocu/core/Print46c/en/data/pdf/BCMIDALEIO/BCMIDALEIO.pdf
http://help.sap.com/printdocu/core/Print46c/en/data/pdf/BCMIDALEPRO/BCMIDALEPRO.pdf
http://help.sap.com/printdocu/core/Print46c/en/data/pdf/CABFAALEQS/CABFAALEQS.pdf
http://help.sap.com/printdocu/core/Print46c/en/data/pdf/BCSRVEDISC/CAEDISCAP_STC.pdf
http://help.sap.com/printdocu/core/Print46c/en/data/pdf/BCSRVEDI/CAEDI.pdf
Also check this links for additional information.
http://help.sap.com/saphelp_erp2004/helpdata/en/dc/6b835943d711d1893e0000e8323c4f/content.htm
http://www.sapgenie.com/sapgenie/docs/ale_scenario_development_procedure.doc
http://edocs.bea.com/elink/adapter/r3/userhtm/ale.htm#1008419
http://www.netweaverguru.com/EDI/HTML/IDocBook.htm
http://www.sapgenie.com/sapedi/index.htm
Hope this will help to start with.
Regards,
Ferry Lianto
Similar Messages
-
RFFOJP_T - Zenginkyo format "EDI information"
Dear all,
Which field in FB60 are used as a value of "EDI Information" in Zenginkyo format payment file generated by RFFOJP_T?
I put some info in "Reference" field, but it was not picked up.
Best regards,
MKThanks Sinkar.
I have tried the java code you have given.It is giving true for file.isDirectory() and some object location for file.isDirectory().
file.canWrite() is also returing true.
But in my b2b.log it is giving that Directory /Y:/PM/Praveena/RI_99 does not exist. as given below.
Starter thread: B2B - (INFORMATION) Repository:getDeliveryEndPointList: Putting file://localhost/Y:\PM\Praveena\RI_99
2009.03.19 at 19:02:30:505: B2BStarter thread: B2B - (INFORMATION) oracle.tip.adapter.b2b.transport.TransportInterface:initialize: Props: file://localhost/Y:\PM\Praveena\RI_99 PROTOCOL_ENDPOINT = null
file.receiver.archive_dir = D:\Archiving
marker = false
archive_dir = D:\Archiving
transport_callout_waittime = 30
file.receiver.polling_interval = 30
polling_interval = 30
file.receiver.minimum_age = 0
file.receiver.marker = false
2009.03.19 at 19:02:30:535: B2BStarter thread: B2B - (WARNING) oracle.tip.adapter.b2b.transport.TransportInterface:initialize Directory /Y:/PM/Praveena/RI_99 does not exist
2009.03.19 at 19:02:30:655: B2BStarter thread: B2B - (DEBUG) initialize TransportReceiver: [IRIS_Transport_Server < file > < IRIS >]
2009.03.19 at 19:02:30:675: B2BStarter thread: B2B - (DEBUG) oracle.tip.adapter.b2b.transport.AppTransportInterface:initialize Initialize AppTransport Logger.
Edited by: Praveena Paruchuru on Mar 19, 2009 7:46 AM -
Hi Friends
Any body please help me to my questions.
1) How to configured to EDI (Send idoc to third party Aramex).
2) What is the process code for Betmas01 IDOC.
3) How to raise idoc automatically when we create a data on sitemaster. (Betmas01).
Thanks
KrishnaHi krishna,
welcome to SDN
Configuring EDI Integration
BEA WebLogic EDI Integration must be completely configured before it can be used. Because EDI Integration depends on BEA EDI Connect for WebLogic Integration to operate properly, make sure you configure Power.Enterprise! correctly so that you can communicate with your trading partners.
General Configuration
This section discusses the general configuration information that you should perform before attempting to configure a specific document exchange with a trading partner.
Configure Trading Partners
Before configuring individual transactions, you should configure all trading partners, including your own company, using Power.Manager!. For more information about configuring trading partners, see the following topics:
Configuring Trading Partners
Chapter 4, "Partners," in the Power.Manager! User Reference Manual
Configure VAN/Trading Partner Connectivity
You should also configure your trading partner connectivity before attempting to configure individual document exchanges. See the following topics:
Connections and VAN Connectivity
Chapter 3, "Connections," in the Power.Manager! User Reference Manual
Although you may not want to set up connectivity to your production trading partners at this time, you may want to configure them with file connectors for development and testing purposes.
Configuring EDI Integration to Receive an EDI Document
This section describes how to configure EDI Integration so that the BEA WebLogic Adapter for Power.Enterprise! 3.1 can receive an EDI document and send it to the WebLogic Integration process engine as an XML document.
Pre-Planning
Determine the EDI standard, version, and document type of the document you will receive. For example, you might select an X12 850 document v4010, which is an X12-standard, 850-type document, version 4010.
Define the XML format that you will use internally. This XML format should contain a complete data map of the fields in the EDI document that you will use.
Create a DTD and an XSD for the XML document. You must create both because Power.Enterprise! and WebLogic Integration do not use the same data file format for this step. WebLogic Integration requires an XSD (if you supply one at all), while Power.Enterprise! requires a DTD. You should note that Power.Enterprise! does not provide any export utility to export a DTD or XSD from a map definition once the DTD or XSD has been imported. You will be responsible for creating both the DTD and XSD files.
Within Power.Enterprise!
Create a map between the XML document and the EDI document. Import the DTD into Power.Map! to load the XML document standard. The appropriate EDI document should already exist in the Power.Server! repository. If the EDI document is not present, contact BEA Customer Support. For more information about how to do this, see the following topics:
Mapping XML and EDI Data
Chapter 3, "Maps" in the Power.Map! User Reference Manual
Define an inbound connection. This connection should use your trading partner's connection protocol, which you should have defined already. For more information, see Connections and VAN Connectivity.
Define an RMI target connection. This connection is used to communicate with the WebLogic Integration process engine.
Define an exchange profile, using the procedure discussed in Configuring Exchange Profiles. This exchange profile should connect the inbound connection from your trading partner to the RMI target connection.
Within BEA WebLogic Integration
Create an application view, using the procedure in Configuring the BEA WebLogic Adapter for Power.Enterprise!.
Create an event for the application view you just created, using the procedure in Configuring Events. Be sure to set the following parameters:
Event Name: A descriptive name for the event, such as ReceivePurchaseOrder
Event Description: Text that provides details about the event
RMI Service Name: Should match RMI service name defined in the Power.Enterprise! RMI target connection set up in the Within Power.Enterprise! section
XSD: The XML schema of the XML message to be received (optional)
XML Root Element: The XML root element of the XML schema (optional)
Deploy the application view you have created and defined.
Verify that the Power.Server! instance is running. At this point, the application view should be available to the WebLogic Integration process engine through the application integration plug-in. For more information about the application integration plug-in, see Understanding the Application Integration Plug-In for BPM in Introducing Application Integration.
Note: Always start the Power.Server! before you start WebLogic Integration or WebLogic Server. The WebLogic Integration connectors expect to see the Power.Server! running when they are initialized, and they throw exceptions if Power.Server! is not running when they are initialized.
Configuring EDI Integration to Send an EDI Document
This section describes how to configure EDI Integration to send an EDI document using an XML document in the WebLogic Integration process engine as the source.
Pre-Planning
Determine the EDI standard, version, and document type of the document you will receive. For example, you might select an X12 850 document v4010, which is an X12-standard, 850-type document, version 4010.
Define the XML format that you will use internally. This XML format should contain a complete data map of the fields in the EDI document that you will use.
Create a DTD and an XSD for the XML document. You must create both because Power.Enterprise! and WebLogic Integration do not use the same data file format for this step. WebLogic Integration requires an XSD (if you supply one at all), while Power.Enterprise! requires a DTD. You should note that Power.Enterprise! does not provide an export utility that can be used to export a DTD or XSD from a map definition once the DTD or XSD has been imported. You are responsible for creating both the DTD and XSD files.
Within Power.Enterprise!
Create a map between the XML document and the EDI document. Import the DTD into Power.Map! to load the XML document standard. The appropriate EDI document should already exist in the Power.Server! repository. If the EDI document is not present, contact BEA Customer Support. For more information about how to do this, see the following topics:
Mapping XML and EDI Data
Chapter 3, "Maps" in the Power.Map! User Reference Manual
Define an outbound connection. This connection should use your trading partner's connection protocol, which you should have defined already. For more information, see Connections and VAN Connectivity.
Define an RMI source connection. This connection is used to communicate with the WebLogic Integration process engine.
Define an exchange profile, using the procedure discussed in Configuring Exchange Profiles. The exchange profile should connect the RMI source connection to your trading partner's outbound connection.
Within BEA WebLogic Integration
Create an application view, using the procedure in Configuring the BEA WebLogic Adapter for Power.Enterprise! in this document.
Create a service for the application view you just created, using the procedure in Configuring Services in this document. Be sure to set up the following parameters:
Service Name: A descriptive name for the service, such as SendPurchaseOrder
Service Description: Text that provides details about the service
Connection Name: Should match the RMI service name defined in the Power.Enterprise! RMI target connection set up in the Within Power.Enterprise! section.
XSD: The XML schema of the XML message to be sent (optional)
XML Root Element: The XML root element of the XML schema (optional)
Deploy the application view you have created and defined.
Verify that the Power.Server! instance is running. At this point, the application view should be available to the WebLogic Integration process engine through the application integration plug-in. For more information about the application integration plug-in, see Understanding the Application Integration Plug-In for BPM in Introducing Application Integration.
see this link for complete edi information
http://msdn.microsoft.com/en-us/library/bb246069.aspx
for your second question......
sapsdforum.files.wordpress.com/2008/03/idoc_handy_doc.pdf
Assigning a Process Code (Direct Inbound Processing)
This section describes how to assign a new process code to the new function module. This enables the function module to be identified from the partner profiles defined in the IDoc Interface when an IDoc of the new message type is received.
Prerequisites
You must have completed the required steps in Defining and Using a Basic Type .
Procedure
Choose SAP Menu ® Tools ® IDoc Interface/ALE ® Development ® Inbound Processing ® Process Code (WE42), or navigate to Inbound Processing Process Code, then and New Entries.
Enter your process code and a description. Choose the Processing with ALE and Processing by function module options and save your entries.
The maintenance screen is displayed (either automatically or manually), in which you can assign the inbound function module to the process code.
Choose New entries and enter in the detail screen:
Your process code
Module (inbound) frame: Your function module and the maximum number of attempts permitted for posting the application data before exception handling is triggered.
IDoc frame: Your object type, the trigger event inputErrorOccurred and the completing event inputFinished.
Application object frame: Your object type
Leave the other fields blank. Save your entries and return to the process codes inbound initial screen.
Go back using to maintain the inbound process codes and choose the Logical message navigation.
In change mode choose New Entries.
Enter the message type (logical message) and the process code and save your entries. As a result, the possible entries (F4) in the partner profiles can display the possible process codes from the logical message, that is, the business view.
If you chose all types in the last step, the value help displays the process code for all message types. This is also valid for both other options for message type and function.
Result
This assignment has specified a new process code for the function module. You can now enter this process code in the partner profiles.
Make the following entries for the example:
Process code
TESTEIN
Basic type
TESTER01
Function module
IDOC_INPUT_TESTER
Maximum number of attempts
0
Message type (logical message)
TESTER
IDoc object type
IDOCTEST
Application object type
BUS2032 (sales order)
To generate Partner profiles automatically you may use BD82 or go to BD64
thanks'
karthik -
can any one explain me what is ALE and EDI and what is difference between two?
plese explain me with example..
thanks in advance.
with regards,
kps moorthy.The philosophical difference between EDI and ALE can be pinned as follows: If we send data to an external partner, we generally speak of EDI, while ALE is a mechanism to reliable replicate data between trusting systems to store a redundant copy of the IDoc data. The difference is made clear, when we think of a purchase order that is sent as an IDoc. If we send the purchase order to a supplier then the supplier will store the purchase order as a sales order. However, if we send the purchase order via ALE to another R/3 system, then the receiving system will store the purchase order also as a purchase order.
This is an article posted on the site below, You Can easily check it out.
http://expertanswercenter.techtarget.com/eac/knowledgebaseAnswer/0,295199,sid63_gci983331,00.html
1) ALE = Application Link Enable: Initially developed for SAP as an abstract layer to extract master and transactional data to be sent ellectronically to other SAP systems. These days is also being used to send data no non-SAP systems. ALE is not a protocol or anything like that, it's just abstract layer composed by a set of applications which are capable of extracting aplication data on a 1-time basis or periodically, by selection criteria or incrementally by deltas.
2) In contrast, EDI = Electronic data interface, this is a comunication protocol not designed by SAP but it´s an industry standard. Of course most SAP software supports EDI, but EDI it's no software but the specification of the protocol in itself.
ALE(Application Link Enabling) refers to the losely coupled systems whereas the EDI speaks about the Electronic Document Exchange. We need to enable ALE in order to use the EDI feature. ALE builds the bridge and EDI is the means by which the data moves in and out of the SAP system just like vehicles moving over the bridge. IDOC(Intermediate Documents) are the data containers which will be moving in and out of SAP carrying data.
Thus summarising we need to establish ALE between the systems in order to use EDI between them. In case we need to use EDI between SAP and some other target system then we need a EDI subsystem which understands these IDOCs and converts into the format understood by the target system.
While IDocs have to be understood as a data exchange protocol, EDI and ALE
are typical use cases for IDocs. R/3 uses IDocs for both EDI and ALE to
deliver data to the receiving system.
Check this link for more details.
http://sapabap.iespana.es/sapabap/sap/faq/ale_idocs_bapi.htm
ALE/Idoc information
http://help.sap.com/saphelp_erp2004/helpdata/en/dc/6b835943d711d1893e0000e8323c4f/content.htm
http://www.sapgenie.com/sapgenie/docs/ale_scenario_development_procedure.doc
http://edocs.bea.com/elink/adapter/r3/userhtm/ale.htm#1008419
http://www.netweaverguru.com/EDI/HTML/IDocBook.htm
http://www.sapgenie.com/sapedi/index.htm
http://www.sappoint.com/abap/ale.pdf
http://www.sappoint.com/abap/ale2.pdf
http://www.sapgenie.com/sapedi/idoc_abap.htm
http://help.sap.com/saphelp_erp2005/helpdata/en/0b/2a60bb507d11d18ee90000e8366fc2/frameset.htm
http://help.sap.com/saphelp_erp2005/helpdata/en/78/217da751ce11d189570000e829fbbd/frameset.htm
http://www.allsaplinks.com/idoc_sample.html
http://www.sappoint.com/abap.html
http://help.sap.com/saphelp_erp2004/helpdata/en/dc/6b835943d711d1893e0000e8323c4f/content.htm
http://www.sapgenie.com/sapgenie/docs/ale_scenario_development_procedure.doc
http://edocs.bea.com/elink/adapter/r3/userhtm/ale.htm#1008419
http://www.netweaverguru.com/EDI/HTML/IDocBook.htm
http://www.sapgenie.com/sapedi/index.htm
http://www.allsaplinks.com/idoc_sample.html
Check these step-by-step links
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
EDI information
http://www.erpgenie.com/sapedi/index.htm
Please refer to site http://edifactory.de which will give you good documentation about EDI.
Check these links for EDI
http://www.netweaverguru.com/EDI/HTML/IDocBook.htm
http://www.sapgenie.com/sapedi/idoc_abap.htm
www.sapgenie.com/sapedi/edi_sap_training.htm
www.sap-img.com/basis/ difference-between-edi-and-idoc.htm
help.sap.com/saphelp_nw04/helpdata/ en/35/26b592afab52b9e10000009b38f974/content.htm
help.sap.com/saphelp_nw04/helpdata/ en/35/26b594afab52b9e10000009b38f974/content.htm
http://www.onestopsap.com/interview-Question/edi/
http://www.intelligententerprise.com/channels/applications/feature/archive/kasturi2.jhtml
http://www.sapgenie.com/sapgenie/docs/i830v3020.xls
http://help.sap.com/saphelp_46c/helpdata/en/0b/2a655d507d11d18ee90000e8366fc2/frameset.htm
http://www.hud.gov/offices/hsg/comp/edi/0306sec1.cfm
http://www.sapgenie.com/sapedi/index.htm
http://help.sap.com/saphelp_erp2004/helpdata/en/dc/6b835943d711d1893e0000e8323c4f/content.htm
http://www.sapgenie.com/sapgenie/docs/ale_scenario_development_procedure.doc
http://edocs.bea.com/elink/adapter/r3/userhtm/ale.htm#1008419
http://www.sapgenie.com/sapedi/index.htm
http://www.allsaplinks.com/idoc_sample.html
http://www.sap-img.com/abap/ale-bapi.htm
http://www.sap-img.com/basis/difference-between-edi-and-idoc.htm
http://www.sappro.com/downloads/OneClientDistribution.pdf
http://www.sapgenie.com/sapgenie/docs/ale_scenario_development_procedure.doc
http://www.sapgenie.com/sapedi/idoc_abap.htm
http://help.sap.com/saphelp_erp2004/helpdata/en/0b/2a60bb507d11d18ee90000e8366fc2/frameset.htm
http://help.sap.com/saphelp_erp2004/helpdata/en/dc/6b828943d711d1893e0000e8323c4f/frameset.htm
http://www.sapgenie.com/ale/whitepaper.htm
http://help.sap.com/printdocu/core/Print46c/en/data/pdf/BCMIDALEIO/BCMIDALEIO.pdf
http://help.sap.com/printdocu/core/Print46c/en/data/pdf/BCMIDALEPRO/BCMIDALEPRO.pdf
http://help.sap.com/printdocu/core/Print46c/en/data/pdf/CABFAALEQS/CABFAALEQS.pdf
http://help.sap.com/printdocu/core/Print46c/en/data/pdf/BCSRVEDISC/CAEDISCAP_STC.pdf
http://help.sap.com/printdocu/core/Print46c/en/data/pdf/BCSRVEDI/CAEDI.pdf
regards,
srinivas
*reward for useful answers*</b> -
Attaching a document along with payment advice during F110
Hi All,
when i run F110 all payments with payment mode 'T'(telegraphic) are mailed to the respective vendors and all payments with mode 'K'(Credit) are displayed in the spool(SP01).
Now the requirement is that the contract of the vendor(contract document is attached in the vendor master-FK02) should also me mailed along with the payment advice.
I created a Z-program(copied from RFFOEDI1) which downloads this contract document from vendor master onto the desktop and then uploads this and sends it to the customer.
However when i do this the mail request for the contract document is being generated(as can be seen in the send requests list (t-code SOSG) and the mail also gets triggered when i process it in SCOT), but no mail request is being generated for the payment advice .
Also no spool for payment advices with payment mode 'K' is generated in SP01.
Any help is appreciated and will be rewared generously.
Thanks in advance.
Najam
I am attaching the part of code i have inserted -
REPORT RFFOEDI1.
INCLUDE ZDWNLD_ATTA.
F110ID-LAUFD = ZW_LAUFD.
F110ID-LAUFI = ZW_LAUFI.
F110ID-OBJKT = KON_PARAM.
PERFORM F_MAIL_CONTRACT.
INSERT T012D-EDIPN INTO HEADER.
AT SELECTION-SCREEN ON PAR_WFOR.
IF PAR_WFOR NE SPACE.
SET CURSOR FIELD 'PAR_WFOR'.
CALL FUNCTION 'FORM_CHECK'
EXPORTING
I_PZFOR = PAR_WFOR.
ENDIF.
FORM F_MAIL_CONTRACT .
F110ID-LAUFD = ZW_LAUFD.
F110ID-LAUFI = ZW_LAUFI.
F110ID-OBJKT = KON_PARAM.
IMPORT SLKTAB FROM DATABASE RFDT(FB) ID F110ID.
READ TABLE SLKTAB INDEX 1.
IF SY-SUBRC = 0.
W_LIFNR = SLKTAB-VONKT.
ENDIF.
CALL FUNCTION 'CONVERSION_EXIT_ALPHA_INPUT'
EXPORTING
INPUT = W_LIFNR
IMPORTING
OUTPUT = W_LIFNR .
*Get vendor Email Address
SELECT SINGLE * FROM LFA1 WHERE LIFNR = W_LIFNR.
IF SY-SUBRC = 0.
SELECT SINGLE * FROM ADR6 WHERE ADDRNUMBER = LFA1-ADRNR.
ENDIF.
W_RECIPIENT = ADR6-SMTP_ADDR.
PERFORM DOWNLOAD_ATT USING W_LIFNR.
PERFORM UPLOAD_ATT_SEND_MAIL USING W_RECIPIENT LTP_FILENAME .
ENDFORM. " F_MAIL_CONTRACT
FORM DOWNLOAD_ATT USING P_W_LIFNR.
SO_INSTI = P_W_LIFNR.
SELECT * FROM SRGBTBREL INTO TABLE TA_SRGBTBREL
WHERE INSTID_A = SO_INSTI
AND TYPEID_A = SO_TYPID
AND CATID_A = SO_CATID.
IF SY-SUBRC EQ 0.
SORT TA_SRGBTBREL BY INSTID_A TYPEID_A CATID_A.
DELETE ADJACENT DUPLICATES FROM TA_SRGBTBREL
COMPARING INSTID_A TYPEID_A CATID_A.
LOOP AT TA_SRGBTBREL INTO WA_SRGBTBREL.
PERFORM PROCESS_ATTACHMENTS
USING WA_SRGBTBREL-INSTID_A
WA_SRGBTBREL-TYPEID_A
WA_SRGBTBREL-CATID_A.
ENDLOOP.
ENDIF.
ENDFORM. " download_att
FORM UPLOAD_ATT_SEND_MAIL USING P_W_RECIPIENT
P_LTP_FILENAME.
RECEIVER = P_W_RECIPIENT.
PERFORM ML_CUSTOMIZE USING 'Tst' 'Contract'.
PERFORM ML_ADDRECP USING RECEIVER 'U'.
PERFORM UPL.
PERFORM DOCONV TABLES I_ITAB OBJBIN.
PERFORM ML_PREPARE USING 'X' EXTENSION NAME.
PERFORM ML_DOSEND.
FORM ML_CUSTOMIZE USING OBJNAME
OBJDESC.
CLEAR DOCDATA.
REFRESH OBJPACK.
CLEAR OBJPACK.
REFRESH OBJHEAD.
REFRESH OBJTXT.
CLEAR OBJTXT.
REFRESH OBJBIN.
CLEAR OBJBIN.
REFRESH OBJHEX.
CLEAR OBJHEX.
REFRESH RECLIST.
CLEAR RECLIST.
REFRESH LISTOBJECT.
CLEAR LISTOBJECT.
CLEAR TAB_LINES.
CLEAR DOC_SIZE.
CLEAR ATT_TYPE.
DOCDATA-OBJ_NAME = OBJNAME.
DOCDATA-OBJ_DESCR = OBJDESC.
ENDFORM. " ml_customize
FORM ML_ADDRECP USING PRECEIVER PREC_TYPE.
CLEAR RECLIST.
RECLIST-RECEIVER = PRECEIVER.
RECLIST-REC_TYPE = PREC_TYPE.
APPEND RECLIST.
ENDFORM. " ml_addrecp
FORM UPL .
FILE_NAME = LTP_FILENAME.
CALL FUNCTION 'GUI_UPLOAD'
EXPORTING
FILENAME = FILE_NAME
FILETYPE = 'BIN'
TABLES
DATA_TAB = I_ITAB
EXCEPTIONS
FILE_OPEN_ERROR = 1
FILE_READ_ERROR = 2
NO_BATCH = 3
GUI_REFUSE_FILETRANSFER = 4
INVALID_TYPE = 5
NO_AUTHORITY = 6
UNKNOWN_ERROR = 7
BAD_DATA_FORMAT = 8
HEADER_NOT_ALLOWED = 9
SEPARATOR_NOT_ALLOWED = 10
HEADER_TOO_LONG = 11
UNKNOWN_DP_ERROR = 12
ACCESS_DENIED = 13
DP_OUT_OF_MEMORY = 14
DISK_FULL = 15
DP_TIMEOUT = 16
OTHERS = 17.
PATH = FILE_NAME.
CALL FUNCTION 'PC_SPLIT_COMPLETE_FILENAME'
EXPORTING
COMPLETE_FILENAME = PATH
IMPORTING
EXTENSION = EXTENSION
NAME = NAME
EXCEPTIONS
INVALID_DRIVE = 1
INVALID_EXTENSION = 2
INVALID_NAME = 3
INVALID_PATH = 4
OTHERS = 5.
ENDFORM. " upl
FORM DOCONV TABLES MYPDF STRUCTURE TLINE
OUTBIN STRUCTURE SOLISTI1.
DATA : POS TYPE I.
DATA : LEN TYPE I.
LOOP AT MYPDF.
POS = 255 - LEN.
IF POS > 134. "length of pdf_table
POS = 134.
ENDIF.
OUTBIN+LEN = MYPDF(POS).
LEN = LEN + POS.
IF LEN = 255. "length of out (contents_bin)
APPEND OUTBIN.
CLEAR: OUTBIN, LEN.
IF POS < 134.
OUTBIN = MYPDF+POS.
LEN = 134 - POS.
ENDIF.
ENDIF.
ENDLOOP.
IF LEN > 0.
APPEND OUTBIN.
ENDIF.
ENDFORM. " doconv
*& Form ml_prepare
text
FORM ML_PREPARE USING BYPASSMEMORY WHATATT_TYPE WHATNAME.
IF BYPASSMEMORY = ''.
CALL FUNCTION 'LIST_FROM_MEMORY'
TABLES
LISTOBJECT = LISTOBJECT
EXCEPTIONS
OTHERS = 1.
IF SY-SUBRC EQ 0.
MESSAGE ID '61' TYPE 'E' NUMBER '731'
WITH 'LIST_FROM_MEMORY'.
ENDIF.
CALL FUNCTION 'TABLE_COMPRESS'
TABLES
IN = LISTOBJECT
OUT = OBJBIN
EXCEPTIONS
OTHERS = 1
IF SY-SUBRC EQ 0.
MESSAGE ID '61' TYPE 'E' NUMBER '731'
WITH 'TABLE_COMPRESS'.
ENDIF.
ENDIF.
*Packing Info For Text Data
DESCRIBE TABLE OBJTXT LINES TAB_LINES.
READ TABLE OBJTXT INDEX TAB_LINES.
DOCDATA-DOC_SIZE = ( TAB_LINES - 1 ) * 255 + STRLEN( OBJTXT ).
CLEAR OBJPACK-TRANSF_BIN.
OBJPACK-HEAD_START = 1.
OBJPACK-HEAD_NUM = 0.
OBJPACK-BODY_START = 1.
OBJPACK-BODY_NUM = TAB_LINES.
OBJPACK-DOC_TYPE = 'TXT'.
APPEND OBJPACK.
*Packing Info Attachment
ATT_TYPE = WHATATT_TYPE..
DESCRIBE TABLE OBJBIN LINES TAB_LINES.
READ TABLE OBJBIN INDEX TAB_LINES.
OBJPACK-DOC_SIZE = ( TAB_LINES - 1 ) * 255 + STRLEN( OBJBIN ).
OBJPACK-TRANSF_BIN = 'X'.
OBJPACK-HEAD_START = 1.
OBJPACK-HEAD_NUM = 0.
OBJPACK-BODY_START = 1.
OBJPACK-BODY_NUM = TAB_LINES.
OBJPACK-DOC_TYPE = ATT_TYPE.
OBJPACK-OBJ_NAME = 'ATTACHMENT'.
OBJPACK-OBJ_DESCR = WHATNAME.
APPEND OBJPACK.
ENDFORM. " ml_prepare
*& Form ml_dosend
text
--> p1 text
<-- p2 text
FORM ML_DOSEND .
CALL FUNCTION 'SO_NEW_DOCUMENT_ATT_SEND_API1'
EXPORTING
DOCUMENT_DATA = DOCDATA
PUT_IN_OUTBOX = 'X'
COMMIT_WORK = 'X' "used from rel. 6.10
TABLES
PACKING_LIST = OBJPACK
OBJECT_HEADER = OBJHEAD
CONTENTS_BIN = OBJBIN
CONTENTS_TXT = OBJTXT
RECEIVERS = RECLIST
EXCEPTIONS
TOO_MANY_RECEIVERS = 1
DOCUMENT_NOT_SENT = 2
DOCUMENT_TYPE_NOT_EXIST = 3
OPERATION_NO_AUTHORIZATION = 4
PARAMETER_ERROR = 5
X_ERROR = 6
ENQUEUE_ERROR = 7
OTHERS = 8
*IF SY-SUBRC EQ 0.
*MESSAGE ID 'SO' TYPE 'S' NUMBER '023'
*WITH DOCDATA-OBJ_NAME.
*ENDIF.
ENDFORM. " ml_dosendHi,
As far as I remember there are no direct ways in SAP do to that.
One suggestion. Create a custom program to send emails and save it with a variant in DME (the last Tab in F110). This is the same place where you maintain the details for sending out the EDI information.
Once you are done with F110, you can carry out the print functionality to execute the program to send out emails with the payment advice.
hope this helps.
Regards -
Product Allocation: Removing a Material from Product Allocation
Hey folks!
I am new to the forums, so hopefully some of you sharks will bite on this one. I work for a consumer products company and we're having issues with product allocations.
We have had a material on product allocation for the past 3 months. We used a allocation rule that is modeled off of the S140 rule on the basic data of the material view. However, our production has now ramped up sufficiently to produce this product and provide normally.
1) How do we remove the material from product allocation?
We deleted the rule from the basic data view, but is there anything else we need to do? There are many remaining open sales orders that get the error "No Feature Combination exists for this selection error". I have ran rescheduling (V_V2) and have also ran the SDRQCR21 to rebuild requirements, but it still remains with this error.
2) Is there something we have to do with the infostructures? Something we have to do in MC64 or MC94?
3) Do we need to go through each sales order and delete the line item and replace the line item to get the normal ATP to function (we would rather not do this as we have EDI information connected to each line item)
4) Is there another report out there I need to run that I just do not know about?
Any help would be great. We are on ECC5.0 Hotpack 15. I will reward points if I can figure out how to.Use MC94 to remove the quantities allocated.
Use MC62 to remove the planning hierarchy.
I believe that in your situation MC94 will work. -
Hi Sap gurus,
Please let me know all tables related to SAP Material master.
and how to get this.
Thanks,
Shayanhi,
Here are the list of MM tables:
Materials
MARA - Material Master: General data
MAKT - Material Master: Description
MARM - Material Master: Unit of Measure
MAPE - Material master: Export control file
MARC - Material master: Plant data
MARD - Material master: Storage location
MAST - Material link to BOM
MBEW - Material valuation
MLGN u2013 Material Master: WM Inventory
MLGT u2013 Material Master: WM Inventory type
MDIP - Material: MRP profiles (field contents)
MKOP - Consignment price segment (old versions of SAP)
EBEW - Valuation of sales order stock
QBEW - Valuation of project stock
MVER u2013 Material Master: Consumption <Plant>
DVER u2013 Material Master: Consumption <MRP Area>
MVKE u2013 Material Master: Sales <Sales Org, Distr Ch>
MLAN - Material Master: Tax indicator
MARC - Material Master: Plant data
MAPR u2013 Material Master: Forecast
MARD u2013 Material Master: Storage Location
MCH1 u2013 Material Master: X Plant Batches
MCHA u2013 Material Master: Batches
MCHB u2013 Material Master: Batch Stock
MDMA - MRP Area data
DBVM - MRP Planning File Entry: MRP Area
MOFF - Outstanding Material Master Records (Maintenance status)
MARCH - Material Master C Segment: History
MARDH - Material Master Storage Location Segment: History
MBEWH - Material Valuation: History
MCHBH - Batch Stocks: History
MKOLH - Special Stocks from Vendor: History
MSCAH - Sales Order Stock at Vendor: History
MSKAH - Sales Order Stock: History
MSKUH - Special Stocks at Customer: History
MSLBH - Special Stocks at Vendor: History
MSPRH - Project Stock: History
MSSAH - Total Sales Order Stocks: History
MSSQH - Total Project Stocks: History
Vendors
LFA1 - Vendor Master: General data
LFB1 - Vendor Master: Company data
LFM1 - Vendor Master: Purchasing Data (Purchasing organization)
LFM2 - Vendor Master: Purchasing Data (Plant, Vendor sub-range)
Purchasing
EBAN - Purchase requisition: items
EBKN - Purchase Requisition: account assignment
STXH - SAPScript Text Header
STXL - SAPScript Text Lines
EKKO - Purchasing document header
EKPO - Purchasing Document: Item
EKET - Purchasing Document: Delivery Schedules
MDBS - Material View of Order Item/Schedule Line (good to find open PO's)
EKKN - Account assignment in purchasing document
EORD - Purchasing Source List
EIPA - Order price history record
EKAB - Release documentation
EKBE - Purchasing document history
EKBZ - Purchasing document history: delivery costs
EKPB - "Material to be provided" item in purchasing document
ESKL - Account assignment specification for service line
ESKN - Account assignment in service package
ESLH - Service package header data
ESLL - Lines in service package
ESSR - Service entry sheet header data
ESUC - External services management: Unplanned limits for contract item
ESUH - External services management: unplanned service limits header data
ESUP - External services management: unplanned limits for service packages
ESUS - External services management: Unplanned limits for service types
EINA - Purchase Info Record: General
EINE - Purchasing info record: purchasing organization data
KONP - Condition Item
KONH - Condition Header
Inventory Management
ISEG - Physical inventory document items
MKPF - Material document: Header
MSEG - Material document: item
RKPF - Reservation: Header
RESB - Reservation: Item
Invoice Verification
BSIM - Secondary index: documents for material
MYMFT - FIFO results table
MYML - LIFO material layer
MYMLM - LIFO material layer (monthly)
MYMP - LIFO period stocks, single material
MYMP1 - Receipt data LIFO/FIFO valuation
MYPL - LIFO pool layer
MYPLM - LIFO pool layer (monthly)
RBCO - Document item, incoming invoice account assignment
RBDIFFKO - Invoice Verification: conditions
RBDIFFME - Invoice Verification: quantity differences
RBDRSEG - Invoice Verification batch: invoice document items
RBKP - Document header: incoming invoice
RBKPB - Invoice document header (batch invoice verification)
RBTX - Taxes:incoming invoice
RBVD - Invoice document: summarization data
RBVDMAT - Invoice Verification: summarization data, material
RBWT - Withholding tax:incoming invoice
RKWA - Consignment withdrawals
RSEG - Document item, incoming invoice
Customising and other master data
MDLV - MRP Areas
MDLG - MRP Areas - Storage Locations
MDLW - MRP Areas - Plants
MDLL - MRP Areas - Subcontractor
T023 - Material Groups
T024 - Purchasing groups
T030 - Standard Accounts Table (Automatic Account Determination)
T156 - Movement Type
T156T - Movement Type: Text
AUSP - Release Procedure: Strategy values (cl20n, cl24n)
AGR_USERS - Assignment of roles to users
CDHDR & CDPOS - Change history of master data and documents
EDID4 - EDI information
TSTC - SAP Transaction Codes, lock/unlock: sm01, created: se93
TSTCT - Transaction codes TEXT
NAST - Message status
regards
Manish Joshi -
hi sap gurus,
i am implementation on MTO scenario of pipe & euipment manuf.industieries so i want infirmation about pp reports and where i get , my client wants following reports so plz tell me how i got fron sap standard or to make from abapers.
daily production reports, monthely production reports, daily scrap reports, pending production order reportswork center capacity report, bom reprts,production order reports, operation sequence reports.
thanks in advance
pareshMB51 Material Doc. List
MB5L List of Stock Values: Balances
MBBS Display valuated special stock
MC$G : Material PurchVal Selection
MC$I : Material PurchQty Selection
MC.1 : Plant Anal. Selection: Stock
MC.2 : Plant Anal.Selection, Rec/Iss
MC.5 : SLoc Anal. Selection, Stock
MC.9 : Material Anal.Selection,Stock
MC.A : Mat.Anal.Selection, Rec/Iss
MC.L : Mat.Group Analysis Sel. Stock
MC48 : Anal. of Current Stock Values
MC50 : Analysis of Dead Stock
MCBA : Plant Analysis Selection
MCBC : Stor. Loc. Analysis Selection
MCBE : Material Analysis Selection
MCBK : MatGrp Analysis Selection
MCBR : Batch Analysis Selection
MCE1 : PurchGrp Analysis Selection
MCE3 : Vendor Analysis Selection
MCE5 : MatGrp Analysis Selection
MCE7 : Material Analysis Selection
MCW3 : Evaluate VBD Header
MCW4 : Evaluate VBD Item
ME2L : Purchase Orders by Vendor
ME2M :Purchase Orders by Material
ME2N : Purchase Orders by PO Number
MIR6 :Invoice Overview
MMBE :Stock Overview
All transaction is stored in table TSTC.
Transaction for MM module start with M.
IH09 - Display Material
MM01 - Create Material
MM02 - Change Material
MM03 - Display Material
MM50 - List Extendable Materials
MMBE - Stock Overview
MMI1 - Create Operating Supplies
MMN1 - Create Non-Stock Material
MMS1 - Create Service
MMU1 - Create Non-Valuated Material
Purchase Requisition:-
ME51N - Create Purchase Requisition
ME52N - Change Purchase Requisition
ME53N - Display Purchase Requisition
ME5A - Purchase Requisitions: List Display
ME5J - Purchase Requisitions for Project
ME5K - Requisitions by Account Assignment
MELB - Purch. Transactions by Tracking No.
ME56 - Assign Source to Purch. Requisition
ME57 - Assign and Process Requisitions
ME58 - Ordering: Assigned Requisitions
ME59 - Automatic Generation of POs
ME54 - Release Purchase Requisition
ME55 - Collective Release of Purchase Reqs.
ME5F - Release Reminder: Purch. Requisition
Reservation:-
MB21 - Create Reservation
MB22 - Change Reservation
MB23 - Display Reservation
MB24 - Reservations by Material
MB25 - Reservations by Account Assignment
MB1C - Other Goods Receipts
MB90 - Output Processing for Mat. Documents
MBRL - Return Delivery per Mat. Document
MB1C - Other Goods Receipts
MB90 - Output Processing for Mat. Documents
MB1B - Transfer Posting
MIBC - ABC Analysis for Cycle Counting
MI01 - Create Physical Inventory Document
MI02 - Change Physical Inventory Document
MI03 - Display Physical Inventory Document
MI31 - Batch Input: Create Phys. Inv. Doc.
MI32 - Batch Input: Block Material
MI33 - Batch Input: Freeze Book Inv.Balance
MICN - Btch Inpt:Ph.Inv.Docs.for Cycle Ctng
MIK1 - Batch Input: Ph.Inv.Doc.Vendor Cons.
MIQ1 - Batch Input: PhInvDoc. Project Stock
MI21 - Print physical inventory document
MI04 - Enter Inventory Count with Document
MI05 - Change Inventory Count
MI06 - Display Inventory Count
MI09 - Enter Inventory Count w/o Document
MI34 - Batch Input: Enter Count
MI35 - Batch Input: Post Zero Stock Balance
MI38 - Batch Input: Count and Differences
MI39 - Batch Input: Document and Count
MI40 - Batch Input: Doc., Count and Diff.
MI08 - Create List of Differences with Doc.
MI10 - Create List of Differences w/o Doc.
MI20 - Print List of Differences
MI11 - Physical Inventory Document Recount
MI07 - Process List of Differences
MI37 - Batch Input: Post Differences
CT01 - Create Characteristic
CT02 - Change Characteristic
CT03 - Display Characteristic
CL01 - Create Class
CL02 - Classes
CL03 - Display Class
CL04 - Delete Class
CL2B - Class Types
ME01 - Maintain Source List
ME03 - Display Source List
ME04 - Changes to Source List
ME05 - Generate Source List
ME06 - Analyze Source List
ME07 - Reorganize Source List
ME08 - Send Source List
ME0M - Source List for Material
ME11 - Create Purchasing Info Record
ME12 - Change Purchasing Info Record
ME13 - Display Purchasing Info Record
ME14 - Changes to Purchasing Info Record
ME15 - Flag Purch. Info Rec. for Deletion
ME16 - Purchasing Info Recs. for Deletion
ME17 - Archive Info Records
ME18 - Send Purchasing Info Record
ME1A Archived Purchasing Info Records
ME1B Redetermine Info Record Price
ME1E Quotation Price History
ME1L Info Records Per Vendor
ME1M Info Records per Material
ME1P Purchase Order Price History
ME1W Info Records Per Material Group
ME1X Buyer's Negotiation Sheet for Vendor
ME1Y Buyer's Negotiat. Sheet for Material
ME21 Create Purchase Order
ME21N Create Purchase rder
ME22 Change Purchase Order
ME22N Change Purchase Order
ME23 Display Purchase Order
ME23N Display Purchase Order
ME24 Maintain Purchase Order Supplement
ME25 Create PO with Source Determination
ME26 Display PO Supplement (IR)
ME27 Create Stock Transport Order
ME28 Release Purchase Order
ME29N Release purchase order
ME2A Monitor Confirmations
ME2B POs by Requirement Tracking Number
ME2C Purchase Orders by Material Group
ME2J Purchase Orders for Project
ME2K Purch. Orders by Account Assignment
ME2L Purchase Orders by Vendor
ME2M Purchase Orders by Material
ME2N Purchase Orders by PO Number
ME2O SC Stock Monitoring (Vendor)
ME2S Services per Purchase Order
ME2V Goods Receipt Forecast
ME2W Purchase Orders for Supplying Plant
ME308 Send Contracts with Conditions
ME31 Create Outline Agreement
ME31K Create Contract
ME31L Create Scheduling Agreement
ME32 Change Outline Agreement
ME32K Change Contract
ME32L Change Scheduling Agreement
ME33 Display Outline Agreement
ME33K Display Contract
ME33L Display Scheduling Agreement
ME34 Maintain Outl. Agreement Supplement
ME34K Maintain Contract Supplement
ME34L Maintain Sched. Agreement Supplement
ME35 Release Outline Agreement
ME35K Release Contract
ME35L Release Scheduling Agreement
ME36 Display Agreement Supplement (IR)
ME37 Create Transport Scheduling Agmt.
ME38 Maintain Sched. Agreement Schedule
ME39 Display Sched. Agmt. Schedule (TEST)
ME3A Transm. Release Documentation Record
ME3B Outl. Agreements per Requirement No.
ME3C Outline Agreements by Material Group
ME3J Outline Agreements per Project
ME3K Outl. Agreements by Acct. Assignment
ME3L Outline Agreements per Vendor
ME3M Outline Agreements by Material
ME3N Outline Agreements by Agreement No.
ME3P Recalculate Contract Price
ME3R Recalculate Sched. Agreement Price
ME3S Service List for Contract
ME41 Create Request For Quotation
ME42 Change Request For Quotation
ME43 Display Request For Quotation
ME44 Maintain RFQ Supplement
ME45 Release RFQ
ME47 Create Quotation
ME48 Display Quotation
ME49 Price Comparison List
ME4B RFQs by Requirement Tracking Number
ME4C RFQs by Material Group
ME4L RFQs by Vendor
ME4M RFQs by Material
ME4N RFQs by RFQ Number
ME4S RFQs by Collective Number
ME51 Create Purchase Requisition
ME51N Create Purchase Requisition
ME52 Change Purchase Requisition
ME52N Change Purchase Requisition
ME52NB Buyer Approval: Purchase Requisition
ME53 Display Purchase Requisition
ME53N Display Purchase Requisition
ME54 Release Purchase Requisition
ME54N Release Purchase Requisition
ME55 Collective Release of Purchase Reqs.
ME56 Assign Source to Purch. Requisition
ME57 Assign and Process Requisitions
ME58 Ordering: Assigned Requisitions
ME59 Automatic Generation of POs
ME59N Automatic generation of POs
ME5A Purchase Requisitions: List Display
ME5F Release Reminder: Purch. Requisition
ME5J Purchase Requisitions for Project
ME5K Requisitions by Account Assignment
ME5R Archived Purchase Requisitions
ME5W Resubmission of Purch. Requisitions
ME61 Maintain Vendor Evaluation
ME62 Display Vendor Evaluation
ME63 Evaluation of Automatic Subcriteria
ME64 Evaluation Comparison
ME65 Evaluation Lists
ME6A Changes to Vendor Evaluation
ME6B Display Vendor Evaln. for Material
ME6C Vendors Without Evaluation
ME6D Vendors Not Evaluated Since...
ME6E Evaluation Records Without Weighting
ME6F Print
ME6G Vendor Evaluation in the Background
ME6H Standard Analysis: Vendor Evaluation
ME6Z Transport Vendor Evaluation Tables
ME80 Purchasing Reporting
ME80A Purchasing Reporting: RFQs
ME80AN General Analyses (A)
ME80F Purchasing Reporting: POs
ME80FN General Analyses (F)
ME80R Purchasing Reporting: Outline Agmts.
ME80RN General Analyses (L,K)
ME81 Analysis of Order Values
ME81N Analysis of Order Values
ME82 Archived Purchasing Documents
ME84 Generation of Sched. Agmt. Releases
ME84A Individual Display of SA Release
ME85 Renumber Schedule Lines
ME86 Aggregate Schedule Lines
ME87 Aggregate PO History
ME88 Set Agr. ***. Qty./Reconcil. Date
ME91 Purchasing Docs.: Urging/Reminding
ME91A Urge Submission of Quotations
ME91E Sch. Agmt. Schedules: Urging/Remind.
ME91F Purchase Orders: Urging/Reminders
ME92 Monitor Order Acknowledgment
ME92F Monitor Order Acknowledgment
ME92K Monitor Order Acknowledgment
ME92L Monitor Order Acknowledgment
ME97 Archive Purchase Requisitions
ME98 Archive Purchasing Documents
ME99 Messages from Purchase Orders
ME9A Message Output: RFQs
ME9E Message Output: Sch. Agmt. Schedules
ME9F Message Output: Purchase Orders
ME9K Message Output: Contracts
ME9L Message Output: Sched. Agreements
MEAN Delivery Addresses
MEB0 Reversal of Settlement Runs
MEB1 Create Reb. Arrangs. (Subseq. Sett.)
MEB2 Change Reb. Arrangs. (Subseq. Sett.)
MEB3 Displ. Reb. Arrangs. (Subseq. Sett.)
MEB4 Settlement re Vendor Rebate Arrs.
MEB5 List of Vendor Rebate Arrangements
MEB6 Busn. Vol. Data, Vendor Rebate Arrs.
MEB7 Extend Vendor Rebate Arrangements
MEB8 Det. Statement, Vendor Rebate Arrs.
MEB9 Stat. Statement, Vendor Rebate Arrs.
MEBA Comp. Suppl. BV, Vendor Rebate Arr.
MEBB Check Open Docs., Vendor Reb. Arrs.
MEBC Check Customizing: Subsequent Sett.
MEBE Workflow Sett. re Vendor Reb. Arrs.
MEBF Updating of External Busn. Volumes
MEBG Chg. Curr. (Euro), Vend. Reb. Arrs.
MEBH Generate Work Items (Man. Extension)
MEBI Message, Subs.Settlem. - Settlem.Run
MEBJ Recompile Income, Vendor Reb. Arrs.
MEBK Message., Subs. Settlem.- Arrangment
MEBM List of settlement runs for arrngmts
MEBR Archive Rebate Arrangements
MEBS Stmnt. Sett. Docs., Vend. Reb. Arrs.
MEBT Test Data: External Business Volumes
MEBV Extend Rebate Arrangements (Dialog)
MECCP_ME2K For Requisition Account Assignment
MEDL Price Change: Contract
MEI1 Automatic Purchasing Document Change
MEI2 Automatic Document Change
MEI3 Recompilation of Document Index
MEI4 Compile Worklist for Document Index
MEI5 Delete Worklist for Document Index
MEI6 Delete purchasing document index
MEI7 Change sales prices in purch. orders
MEI8 Recomp. doc. index settlement req.
MEI9 Recomp. doc. index vendor bill. doc.
MEIA New Structure Doc.Ind. Cust. Sett.
MEIS Data Selection: Arrivals
MEK1 Create Conditions (Purchasing)
MEK2 Change Conditions (Purchasing)
MEK3 Display Conditions (Purchasing)
MEK31 Condition Maintenance: Change
MEK32 Condition Maintenance: Change
MEK33 Condition Maintenance: Change
MEK4 Create Conditions (Purchasing)
MEKA Conditions: General Overview
MEKB Conditions by Contract
MEKC Conditions by Info Record
MEKD Conditions for Material Group
MEKE Conditions for Vendor
MEKF Conditions for Material Type
MEKG Conditions for Condition Group
MEKH Market Price
MEKI Conditions for Incoterms
MEKJ Conditions for Invoicing Party
MEKK Conditions for Vendor Sub-Range
MEKL Price Change: Scheduling Agreements
MEKLE Currency Change: Sched. Agreements
MEKP Price Change: Info Records
MEKPE Currency Change: Info Records
MEKR Price Change: Contracts
MEKRE Currency Change: Contracts
MEKX Transport Condition Types Purchasing
MEKY Trnsp. Calc. Schema: Mkt. Pr. (Pur.)
MEKZ Trnsp. Calculation Schemas (Purch.)
MELB Purch. Transactions by Tracking No.
MEMASSIN Mass-Changing of Purch. Info Records
MEMASSPO Mass Change of Purchase Orders
MEMASSRQ Mass-Changing of Purch. Requisitions
MENU_MIGRATION Menu Migration into New Hierarchy
MEPA Order Price Simulation/Price Info
MEPB Price Info/Vendor Negotiations
MEPO Purchase Order
MEQ1 Maintain Quota Arrangement
MEQ3 Display Quota Arrangement
MEQ4 Changes to Quota Arrangement
MEQ6 Analyze Quota Arrangement
MEQ7 Reorganize Quota Arrangement
MEQ8 Monitor Quota Arrangements
MEQB Revise Quota Arrangement
MEQM Quota Arrangement for Material
MER4 Settlement re Customer Rebate Arrs.
MER5 List of Customer Rebate Arrangements
MER6 Busn. Vols., Cust. Reb. Arrangements
MER7 Extension of Cust. Reb. Arrangements
MER8 Det. Statement: Cust. Rebate Arrs.
MER9 Statement: Customer Reb. Arr. Stats.
MERA Comp. Suppl. BV, Cust. Rebate Arrs.
MERB Check re Open Docs. Cust. Reb. Arr.
MERE Workflow: Sett. Cust. Rebate Arrs.
MEREP_EX_REPLIC SAP Mobile: Execute Replicator
MEREP_GROUP SAP Mobile: Mobile Group
MEREP_LOG SAP Mobile: Activity Log
MEREP_MIG SAP Mobile: Migration
MEREP_MON SAP Mobile: Mobile Monitor
MEREP_PD SAP Mobile: Profile Dialog
MEREP_PURGE SAP Mobile: Purge Tool
MEREP_SBUILDER SAP Mobile: SyncBO Builder
MEREP_SCENGEN SAP Mobile: SyncBO Generator
MERF Updating of External Busn. Volumes
MERG Change Curr. (Euro) Cust. Reb. Arrs.
MERH Generate Work Items (Man. Extension)
MERJ Recomp. of Income, Cust. Reb. Arrs.
MERS Stmnt. Sett. Docs. Cust. Reb. Arrs.
MEU0 Assign User to User Group
MEU2 Perform Busn. Volume Comp.: Rebate
MEU3 Display Busn. Volume Comp.: Rebate
MEU4 Display Busn. Volume Comp.: Rebate
MEU5 Display Busn. Volume Comp.: Rebate
MEW0 Procurement Transaction
MEW1 Create Requirement Request
MEW10 Service Entry in Web
MEW2 Status Display: Requirement Requests
MEW3 Collective Release of Purchase Reqs.
MEW5 Collective Release of Purchase Order
MEW6 Assign Purchase Orders WEB
MEW7 Release of Service Entry Sheets
MEW8 Release of Service Entry Sheet
MEW9 mew9
MEWP Web based PO
MEWS Service Entry (Component)
ME_SWP_ALERT Display MRP Alerts (Web)
ME_SWP_CO Display Purchasing Pricing (Web)
ME_SWP_IV Display Settlement Status (Web)
ME_SWP_PDI Display Purchase Document Info (Web)
ME_SWP_PH Display Purchasing History (Web)
ME_SWP_SRI Display Schedule Releases (Web)
ME_WIZARD ME: Registration and Generation
PURCHASING TABLES
A501 Plant/Material
EBAN Purchase Requisition
EBKN Purchase Requisition Account Assignment
EKAB Release Documentation
EKBE History per Purchasing Document
EKET Scheduling Agreement Schedule Lines
EKKN Account Assignment in Purchasing Document
EKKO Purchasing Document Header
EKPO Purchasing Document Item
IKPF Header- Physical Inventory Document
ISEG Physical Inventory Document Items
LFA1 Vendor Master (General section)
LFB1 Vendor Master (Company Code)
NRIV Number range intervals
RESB Reservation/dependent requirements
T161T Texts for Purchasing Document Types
MARA - Material Master: General data
MAKT - Material Master: Description
MARM - Material Master: Unit of Measure
MAPE - Material master: Export control file
MARC - Material master: Plant data
MARD - Material master: Storage location
MAST - Material link to BOM
MBEW - Material valuation
MLGN Material Master: WM Inventory
MLGT Material Master: WM Inventory type
MDIP - Material: MRP profiles (field contents)
MKOP - Consignment price segment (old versions of SAP)
EBEW - Valuation of sales order stock
QBEW - Valuation of project stock
MVER Material Master: Consumption <Plant>
DVER Material Master: Consumption <MRP Area>
MVKE Material Master: Sales <Sales Org, Distr Ch>
MLAN - Material Master: Tax indicator
MARC - Material Master: Plant data
MAPR Material Master: Forecast
MARD Material Master: Storage Location
MCH1 Material Master: X Plant Batches
MCHA Material Master: Batches
MCHB Material Master: Batch Stock
MDMA - MRP Area data
DBVM - MRP Planning File Entry: MRP Area
MOFF - Outstanding Material Master Records (Maintenance status)
MARCH - Material Master C Segment: History
MARDH - Material Master Storage Location Segment: History
MBEWH - Material Valuation: History
MCHBH - Batch Stocks: History
MKOLH - Special Stocks from Vendor: History
MSCAH - Sales Order Stock at Vendor: History
MSKAH - Sales Order Stock: History
MSKUH - Special Stocks at Customer: History
MSLBH - Special Stocks at Vendor: History
MSPRH - Project Stock: History
MSSAH - Total Sales Order Stocks: History
MSSQH - Total Project Stocks: History
Vendors
LFA1 - Vendor Master: General data
LFB1 - Vendor Master: Company data
LFM1 - Vendor Master: Purchasing Data (Purchasing organization)
LFM2 - Vendor Master: Purchasing Data (Plant, Vendor sub-range)
Purchasing
EBAN - Purchase requisition: items
EBKN - Purchase Requisition: account assignment
STXH - SAPScript Text Header
STXL - SAPScript Text Lines
EKKO - Purchasing document header
EKPO - Purchasing Document: Item
EKET - Purchasing Document: Delivery Schedules
MDBS - Material View of Order Item/Schedule Line (good to find open PO's)
EKKN - Account assignment in purchasing document
EORD - Purchasing Source List
EIPA - Order price history record
EKAB - Release documentation
EKBE - Purchasing document history
EKBZ - Purchasing document history: delivery costs
EKPB - "Material to be provided" item in purchasing document
ESKL - Account assignment specification for service line
ESKN - Account assignment in service package
ESLH - Service package header data
ESLL - Lines in service package
ESSR - Service entry sheet header data
ESUC - External services management: Unplanned limits for contract item
ESUH - External services management: unplanned service limits header data
ESUP - External services management: unplanned limits for service packages
ESUS - External services management: Unplanned limits for service types
EINA - Purchase Info Record: General
EINE - Purchasing info record: purchasing organization data
KONP - Condition Item
KONH - Condition Header
Inventory Management
ISEG - Physical inventory document items
MKPF - Material document: Header
MSEG - Material document: item
RKPF - Reservation: Header
RESB - Reservation: Item
Invoice Verification
BSIM - Secondary index: documents for material
MYMFT - FIFO results table
MYML - LIFO material layer
MYMLM - LIFO material layer (monthly)
MYMP - LIFO period stocks, single material
MYMP1 - Receipt data LIFO/FIFO valuation
MYPL - LIFO pool layer
MYPLM - LIFO pool layer (monthly)
RBCO - Document item, incoming invoice account assignment
RBDIFFKO - Invoice Verification: conditions
RBDIFFME - Invoice Verification: quantity differences
RBDRSEG - Invoice Verification batch: invoice document items
RBKP - Document header: incoming invoice
RBKPB - Invoice document header (batch invoice verification)
RBTX - Taxes:incoming invoice
RBVD - Invoice document: summarization data
RBVDMAT - Invoice Verification: summarization data, material
RBWT - Withholding tax:incoming invoice
RKWA - Consignment withdrawals
RSEG - Document item, incoming invoice
Customising and other master data
MDLV - MRP Areas
MDLG - MRP Areas - Storage Locations
MDLW - MRP Areas - Plants
MDLL - MRP Areas - Subcontractor
T023 - Material Groups
T024 - Purchasing groups
T030 - Standard Accounts Table (Automatic Account Determination)
T156 - Movement Type
T156T - Movement Type: Text
AUSP - Release Procedure: Strategy values (cl20n, cl24n)
AGR_USERS - Assignment of roles to users
CDHDR & CDPOS - Change history of master data and documents
EDID4 - EDI information
TSTC - SAP Transaction Codes, lock/unlock: sm01, created: se93
TSTCT - Transaction codes TEXT
MM01 - Create Material
MM02 - Change Material
MM03 - Display Material
MM50 - List Extendable Materials
MMBE - Stock Overview
MMI1 - Create Operating Supplies
MMN1 - Create Non-Stock Material
MMS1 - Create Service
MMU1 - Create Non-Valuated Material
ME51N - Create Purchase Requisition
ME52N - Change Purchase Requisition
ME53N - Display Purchase Requisition
ME5A - Purchase Requisitions: List Display
ME5J - Purchase Requisitions for Project
ME5K - Requisitions by Account Assignment
MELB - Purch. Transactions by Tracking No.
ME56 - Assign Source to Purch. Requisition
ME57 - Assign and Process Requisitions
ME58 - Ordering: Assigned Requisitions
ME59 - Automatic Generation of POs
ME54 - Release Purchase Requisition
ME55 - Collective Release of Purchase Reqs.
ME5F - Release Reminder: Purch. Requisition
MB21 - Create Reservation
MB22 - Change Reservation
MB23 - Display Reservation
MB24 - Reservations by Material
MB25 - Reservations by Account Assignment
MB1C - Other Goods Receipts
MB90 - Output Processing for Mat. Documents
MB21 - Create Reservation
MB22 - Change Reservation
MB23 - Display Reservation
MB24 - Reservations by Material
MB25 - Reservations by Account Assignment
MBRL - Return Delivery per Mat. Document
MB1C - Other Goods Receipts
MB90 - Output Processing for Mat. Documents
MB1B - Transfer Posting
MIBC - ABC Analysis for Cycle Counting
MI01 - Create Physical Inventory Document
MI02 - Change Physical Inventory Document
MI03 - Display Physical Inventory Document
MI31 - Batch Input: Create Phys. Inv. Doc.
MI32 - Batch Input: Block Material
MI33 - Batch Input: Freeze Book Inv.Balance
MICN - Btch Inpt:Ph.Inv.Docs.for Cycle Ctng
MIK1 - Batch Input: Ph.Inv.Doc.Vendor Cons.
MIQ1 - Batch Input: PhInvDoc. Project Stock
MI01 - Create Physical Inventory Document
MI02 - Change Physical Inventory Document
MI03 - Display Physical Inventory Document
MI31 - Batch Input: Create Phys. Inv. Doc.
MI32 - Batch Input: Block Material
MI33 - Batch Input: Freeze Book Inv.Balance
MICN - Btch Inpt:Ph.Inv.Docs.for Cycle Ctng
MIK1 - Batch Input: Ph.Inv.Doc.Vendor Cons.
MIQ1 - Batch Input: PhInvDoc. Project Stock
MI01 - Create Physical Inventory Document
MI02 - Change Physical Inventory Document
MI03 - Display Physical Inventory Document
MI31 - Batch Input: Create Phys. Inv. Doc.
MI32 - Batch Input: Block Material
MI33 - Batch Input: Freeze Book Inv.Balance
MICN - Btch Inpt:Ph.Inv.Docs.for Cycle Ctng
MIK1 - Batch Input: Ph.Inv.Doc.Vendor Cons.
MIQ1 - Batch Input: PhInvDoc. Project Stock
MI21 - Print physical inventory document
MI04 - Enter Inventory Count with Document
MI05 - Change Inventory Count
MI06 - Display Inventory Count
MI09 - Enter Inventory Count w/o Document
MI34 - Batch Input: Enter Count
MI35 - Batch Input: Post Zero Stock Balance
MI38 - Batch Input: Count and Differences
MI39 - Batch Input: Document and Count
MI40 - Batch Input: Doc., Count and Diff.
MI08 - Create List of Differences with Doc.
MI10 - Create List of Differences w/o Doc.
MI20 - Print List of Differences
MI11 - Physical Inventory Document Recount
MI07 - Process List of Differences
MI37 - Batch Input: Post Differences
IH09 - Display Material
MM01 - Create Material
MM02 - Change Material
MM03 - Display Material
MM50 - List Extendable Materials
MMBE - Stock Overview
MMI1 - Create Operating Supplies
MMN1 - Create Non-Stock Material
MMS1 - Create Service
MMU1 - Create Non-Valuated Material
ME51N - Create Purchase Requisition
ME52N - Change Purchase Requisition
ME53N - Display Purchase Requisition
ME5A - Purchase Requisitions: List Display
ME5J - Purchase Requisitions for Project
ME5K - Requisitions by Account Assignment
MELB - Purch. Transactions by Tracking No.
ME56 - Assign Source to Purch. Requisition
ME57 - Assign and Process Requisitions
ME58 - Ordering: Assigned Requisitions
ME59 - Automatic Generation of POs
ME54 - Release Purchase Requisition
ME55 - Collective Release of Purchase Reqs.
ME5F - Release Reminder: Purch. Requisition
MB21 - Create Reservation
MB22 - Change Reservation
MB23 - Display Reservation
MB24 - Reservations by Material
MB25 - Reservations by Account Assignment
MB1C - Other Goods Receipts
MB90 - Output Processing for Mat. Documents
MB21 - Create Reservation
MB22 - Change Reservation
MB23 - Display Reservation
MB24 - Reservations by Material
MB25 - Reservations by Account Assignment
MBRL - Return Delivery per Mat. Document
MB1C - Other Goods Receipts
MB90 - Output Processing for Mat. Documents
MB1B - Transfer Posting
MIBC - ABC Analysis for Cycle Counting
MI01 - Create Physical Inventory Document
MI02 - Change Physical Inventory Document
MI03 - Display Physical Inventory Document
MI31 - Batch Input: Create Phys. Inv. Doc.
MI32 - Batch Input: Block Material
MI33 - Batch Input: Freeze Book Inv.Balance
MICN - Btch Inpt:Ph.Inv.Docs.for Cycle Ctng
MIK1 - Batch Input: Ph.Inv.Doc.Vendor Cons.
MIQ1 - Batch Input: PhInvDoc. Project Stock
MI01 - Create Physical Inventory Document
MI02 - Change Physical Inventory Document
MI03 - Display Physical Inventory Document
MI31 - Batch Input: Create Phys. Inv. Doc.
MI32 - Batch Input: Block Material
MI33 - Batch Input: Freeze Book Inv.Balance
MICN - Btch Inpt:Ph.Inv.Docs.for Cycle Ctng
MIK1 - Batch Input: Ph.Inv.Doc.Vendor Cons.
MIQ1 - Batch Input: PhInvDoc. Project Stock
MI01 - Create Physical Inventory Document
MI02 - Change Physical Inventory Document
MI03 - Display Physical Inventory Document
MI31 - Batch Input: Create Phys. Inv. Doc.
MI32 - Batch Input: Block Material
MI33 - Batch Input: Freeze Book Inv.Balance
MICN - Btch Inpt:Ph.Inv.Docs.for Cycle Ctng
MIK1 - Batch Input: Ph.Inv.Doc.Vendor Cons.
MIQ1 - Batch Input: PhInvDoc. Project Stock
MI21 - Print physical inventory document
MI04 - Enter Inventory Count with Document
MI05 - Change Inventory Count
MI06 - Display Inventory Count
MI09 - Enter Inventory Count w/o Document
MI34 - Batch Input: Enter Count
MI35 - Batch Input: Post Zero Stock Balance
MI38 - Batch Input: Count and Differences
MI39 - Batch Input: Document and Count
MI40 - Batch Input: Doc., Count and Diff.
MI08 - Create List of Differences with Doc.
MI10 - Create List of Differences w/o Doc.
MI20 - Print List of Differences
MI11 - Physical Inventory Document Recount
MI07 - Process List of Differences
MI37 - Batch Input: Post Differences
CT01 - Create Characteristic
CT02 - Change Characteristic
CT03 - Display Characteristic
- Create Class
CL02 - Classes
CL03 - Display Class
CL04 - Delete Class
CL2B - Class Types -
Change default resolutions provided by ML
Hi folks,
I'm having an issue at the office that kind of upset me. Basically, PC users laungh at Mac user not being able to display correctly on plasma's meeting room.
They have a native resolution of 1280x768 and this is basically what I want to use.
The problem is that this resolution is not proposed by the system in Monitors. Why is that ? My thought is that the TV is connected through VGA then YUV components cable, and that wouldn't surprised me the EDI informations does not make the way to the mac to announce supported resolutions, so the mac sees a "VGA Display" and proposes a set of default resolutions, this is what I'd like to adjust.
I was able to do this with SwitchResX but I can't ask every mac owner to buy a software to use an external display... those guys are gonna laugh harder !
The TV is a Pioneer pdp-505-cmx
Changing the connection to the screen is not an option, the cable passes from behind the wall to the floor and the meeting room table to a VGA connector.
Please answer if you really know what you're talking about and avoid "Open System Preferences and choose a resolution" !Thanks... I don't know how that helps me tho !
I don't know hos windows is able to determine a correct resolution, but it can, and it works like a charm !
I still need to send the right resolution to the plasma, and rectangle shaped pixels in plasma monitor is not uncommon at all !
I should add that I tried every resolution provided by Mac OS X and none of them looks right (either pixelized, shaggy, wrong aspect ratio and so on...)
The only thing that worked is sending 1280x768 using SwitchResX. Even the aspect ratio looks good to me.
Here are the spec of the monitor : -
T-codes for Material Stockss....
Hi experts,
Any one know the T-codessss for the alll types of STOCKsssss......
like MMBE,MB52 like that.. all kind of materials all kind of stock...
Thanksin Advance,
Anthyodaya.Hi,
These are the main T codes in MM..
MARA - Material Master: General data
MAKT - Material Master: Description
MARM - Material Master: Unit of Measure
MAPE - Material master: Export control file
MARC - Material master: Plant data
MARD - Material master: Storage location
MAST - Material link to BOM
MBEW - Material valuation
MLGN u2013 Material Master: WM Inventory
MLGT u2013 Material Master: WM Inventory type
MDIP - Material: MRP profiles (field contents)
MKOP - Consignment price segment (old versions of SAP)
EBEW - Valuation of sales order stock
QBEW - Valuation of project stock
MVER u2013 Material Master: Consumption
DVER u2013 Material Master: Consumption
MVKE u2013 Material Master: Sales
MLAN - Material Master: Tax indicator
MARC - Material Master: Plant data
MAPR u2013 Material Master: Forecast
MARD u2013 Material Master: Storage Location
MCH1 u2013 Material Master: X Plant Batches
MCHA u2013 Material Master: Batches
MCHB u2013 Material Master: Batch Stock
MDMA - MRP Area data
DBVM - MRP Planning File Entry: MRP Area
MOFF - Outstanding Material Master Records (Maintenance status)
MARCH - Material Master C Segment: History
MARDH - Material Master Storage Location Segment: History
MBEWH - Material Valuation: History
MCHBH - Batch Stocks: History
MKOLH - Special Stocks from Vendor: History
MSCAH - Sales Order Stock at Vendor: History
MSKAH - Sales Order Stock: History
MSKUH - Special Stocks at Customer: History
MSLBH - Special Stocks at Vendor: History
MSPRH - Project Stock: History
MSSAH - Total Sales Order Stocks: History
MSSQH - Total Project Stocks: History
Related to Vendors:
LFA1 - Vendor Master: General data
LFB1 - Vendor Master: Company data
LFM1 - Vendor Master: Purchasing Data (Purchasing organization)
LFM2 - Vendor Master: Purchasing Data (Plant, Vendor sub-range)
Purchasing:
EBAN - Purchase requisition: items
EBKN - Purchase Requisition: account assignment
STXH - SAPScript Text Header
STXL - SAPScript Text Lines
EKKO - Purchasing document header
EKPO - Purchasing Document: Item
EKET - Purchasing Document: Delivery Schedules
MDBS - Material View of Order Item/Schedule Line (good to find open PO's)
EKKN - Account assignment in purchasing document
EORD - Purchasing Source List
EIPA - Order price history record
EKAB - Release documentation
EKBE - Purchasing document history
EKBZ - Purchasing document history: delivery costs
EKPB - "Material to be provided" item in purchasing document
ESKL - Account assignment specification for service line
ESKN - Account assignment in service package
ESLH - Service package header data
ESLL - Lines in service package
ESSR - Service entry sheet header data
ESUC - External services management: Unplanned limits for contract item
ESUH - External services management: unplanned service limits header data
ESUP - External services management: unplanned limits for service packages
ESUS - External services management: Unplanned limits for service types
EINA - Purchase Info Record: General
EINE - Purchasing info record: purchasing organization data
KONP - Condition Item
KONH - Condition Header
Inventory Management:
ISEG - Physical inventory document items
MKPF - Material document: Header
MSEG - Material document: item
RKPF - Reservation: Header
RESB - Reservation: Item
Invoice Verification
BSIM - Secondary index: documents for material
MYMFT - FIFO results table
MYML - LIFO material layer
MYMLM - LIFO material layer (monthly)
MYMP - LIFO period stocks, single material
MYMP1 - Receipt data LIFO/FIFO valuation
MYPL - LIFO pool layer
MYPLM - LIFO pool layer (monthly)
RBCO - Document item, incoming invoice account assignment
RBDIFFKO - Invoice Verification: conditions
RBDIFFME - Invoice Verification: quantity differences
RBDRSEG - Invoice Verification batch: invoice document items
RBKP - Document header: incoming invoice
RBKPB - Invoice document header (batch invoice verification)
RBTX - Taxes:incoming invoice
RBVD - Invoice document: summarization data
RBVDMAT - Invoice Verification: summarization data, material
RBWT - Withholding tax:incoming invoice
RKWA - Consignment withdrawals
RSEG - Document item, incoming invoice
Customising and Other Master Data:
MDLV - MRP Areas
MDLG - MRP Areas - Storage Locations
MDLW - MRP Areas - Plants
MDLL - MRP Areas - Subcontractor
T023 - Material Groups
T024 - Purchasing groups
T030 - Standard Accounts Table (Automatic Account Determination)
T156 - Movement Type
T156T - Movement Type: Text
AUSP - Release Procedure: Strategy values (cl20n, cl24n)
AGR_USERS - Assignment of roles to users
CDHDR & CDPOS - Change history of master data and documents
EDID4 - EDI information
TSTC - SAP Transaction Codes, lock/unlock: sm01, created: se93
TSTCT - Transaction codes TEXT
Thanks
Prasada -
Installing ASN functionality ( Points to consider) ???
Our client is in the process of installing ASN ( Advanced shipping notification) process for the procurement of items from vendors?
What are the design considerations that I need to keep in mind prior to installing ASN?
1) Does the vendor need to be using SAP system for this to happen?
2) Any enhancements that need to happen at the receiving end of SAP to receive the inbound ASN's?
3) Do we need EDI functionality in order for this ASN communication to happen?
4) How do we view the ASN data element on the MD04/MD06 stock requirements list? Would it have a expected date of receipt? Will the ATP take into account that ASN data ?
Please throw some lights into it. Appreciate all your feedbacks.. Some of them might be too simple for all the experts in the forum.
Thanks,
Drop in the oceanHi Drop in the ocean
1) Does the vendor need to be using SAP system for this to happen?
no need,they can use other erp system,if the system could send 856(ASN) to you.
2) Any enhancements that need to happen at the receiving end of SAP to receive the inbound ASN's?
you only config the background in you SAP. there are standard ASN function in SAP
3) Do we need EDI functionality in order for this ASN communication to happen?
same as above, SAP has this function, you need to active it,in addition, you could deveop some useful report to view EDI information, the SAP standrad tcode We02/BD87 could review EDI infirmation one by one.
4) How do we view the ASN data element on the MD04/MD06 stock requirements list? Would it have a expected date of receipt? Will the ATP take into account that ASN data ?
*When you receive a ASN,system will generate a Ship notification MRP element in MD04 and MD06.When you click that item,system will prompt a dialogue and you could see the inbound delivery number.you could check in VL33n
the expect receive date is a evaluate date,base on the vendor shipping date+planning delivery time.
regarding ATP check, you could investifate you check rule and Check group, if you tick the shipping notification,system will consider it*
Dick Hua -
i have popup codes like this (too many around 12-20 popup screens) painted for demo.
most of them have a kind of 1-2 layout ie
the fields come dynamically from a resultset
i am guessing i can change the SQL code so that i can get the proper field names
eg
SELECT
FIELD1 AS DisplayName1,
FIELD2 AD DisplayName2
is there a way to dynamically adjust the layout to set the fields in a good way according to the recordset returned.
| Label1: Field1 |
| Label1: Field1 |
| Label1: Field1 |
| Label1: Field1 |
| OK Cancel |
package com.samples.swingsamples;
import javax.swing.*;
import javax.swing.border.*;
import java.awt.*;
import java.awt.event.*;
public class clsClaimsEDI extends JDialog
public clsClaimsEDI( JFrame frame ) {
super( frame, true );
setTitle( "EDI Information" );
setSize( 500, 300 );
// Creates a panel to hold all components
JPanel panel = new JPanel( new BorderLayout() );
panel.setLayout( new GridBagLayout() );
// give the panel a border gap of 5 pixels
panel.setBorder( new EmptyBorder( new Insets( 5, 5, 5, 5 ) ) );
getContentPane().add( BorderLayout.NORTH, panel );
GridBagConstraints c = new GridBagConstraints();
// Define preferred sizes for input fields
Dimension shortField = new Dimension( 40, 20 );
Dimension mediumField = new Dimension( 120, 20 );
Dimension longField = new Dimension( 240, 20 );
Dimension hugeField = new Dimension( 240, 80 );
// Spacing between label and field
EmptyBorder border = new EmptyBorder( new Insets( 0, 0, 0, 10 ) );
EmptyBorder border1 = new EmptyBorder( new Insets( 0, 20, 0, 10 ) );
// add space around all components to avoid clutter
c.insets = new Insets( 2, 2, 2, 2 );
// anchor all components WEST
c.anchor = GridBagConstraints.WEST;
JLabel lbl1 = new JLabel( "Claim ID" );
lbl1.setBorder( border ); // add some space to the right
panel.add( lbl1, c );
JTextField txt1 = new JTextField();
txt1.setPreferredSize( longField );
c.gridx = 1;
c.weightx = 1.0; // use all available horizontal space
c.gridwidth = 3; // spans across 3 columns
c.fill = GridBagConstraints.HORIZONTAL; // fills the 3 columns
panel.add( txt1, c );
JLabel lbl2 = new JLabel( "External Reference Number" );
lbl2.setBorder( border );
c.gridwidth = 1;
c.gridx = 0;
c.gridy = 1;;
c.weightx = 0.0; // do not use any extra horizontal space
panel.add( lbl2, c );
JTextField txt2 = new JTextField();
txt2.setPreferredSize( mediumField );
c.gridx = 1;
c.ipadx = 0; // reset the padding to 0
c.ipady = 0;
c.weightx = 1.0; // use all available horizontal space
// c.weighty = 1.0; // use all available vertical space
c.gridwidth = 3; // span across 3 columns
// c.gridheight = 1; // span across 2 rows
c.fill = GridBagConstraints.HORIZONTAL; // fills the cols & rows
panel.add( txt2, c );
JLabel lbl3 = new JLabel( "Trading Partner" );
lbl3.setBorder( border );
c.gridx = 0;
c.gridy = 3;
c.gridwidth = 1;
c.gridheight = 1;
c.weightx = 0.0;
c.weighty = 0.0;
c.fill = GridBagConstraints.NONE;
panel.add( lbl3, c );
JTextField txt3 = new JTextField();
txt3.setPreferredSize( mediumField);
c.gridx = 1;
c.gridwidth = 3; // span across 3 columns
c.gridheight = 1; // span across 2 rows
c.fill = GridBagConstraints.BOTH; // fills the cols & rows
panel.add( txt3, c );
c.gridx = 2;
panel.add( Box.createVerticalStrut(1), c );
c.gridx = 3;
panel.add( Box.createVerticalStrut(1), c );
c.gridx = 0;
c.gridy = 4;
panel.add( Box.createVerticalStrut(1), c );
c.gridx = 1;
c.gridwidth = 3;
panel.add( Box.createVerticalStrut(1), c );
c.gridx = 0;
c.gridy = 5;
panel.add( Box.createVerticalStrut(1), c );
c.gridx = 1;
c.gridwidth = 3;
panel.add( Box.createVerticalStrut(1), c );
c.gridx = 0;
c.gridy = 6;
panel.add( Box.createVerticalStrut(1), c );
c.gridx = 1;
c.gridwidth = 3;
panel.add( Box.createVerticalStrut(1), c);
c.gridx = 0;
c.gridy = 7;
c.gridwidth = 1;
panel.add( Box.createVerticalStrut(1), c );
c.gridx = 1;
c.gridwidth = 3;
panel.add( Box.createVerticalStrut(1), c );
JButton submitBtn = new JButton( "Close" );
c.gridx = 4;
c.gridy = 0;
c.gridwidth = 1;
c.fill = GridBagConstraints.HORIZONTAL;
panel.add( submitBtn, c );
JButton cancelBtn = new JButton( "Help" );
c.gridx = 4;
c.gridy = 0;
c.gridwidth = 1;
c.fill = GridBagConstraints.HORIZONTAL;
panel.add( cancelBtn, c );
JButton helpBtn = new JButton( "Help" );
c.gridy = 1;
c.anchor = GridBagConstraints.NORTH; // anchor north
panel.add( helpBtn, c );
setVisible( true );any other popup samples :))
-
Information Messages while creation of the sales order thru EDI 850
Hello All,
I am trying to create a Sales Order using EDI 850. When i am doing the same i am getting the information messages and the Sales Order is not created and the IDOC is in 51 status. I am using the ORDERS05 Idoc Type.
Following are some of the messages i get: 1. Oldest of open items overdue; 2. Document Complete 3. ISO Country code not found.
some are valid message and i have already fixed them. But when i create the sales order manually it gives me the sales order number even though i get the information messages.
Please let me know is there any setting that i have to make for EDI process to counter the information messages.
Thank You,
Sureshwhats the final message you got? that will give you what is the issue.
in you look at IDOC_INPUT_ORDERS, it does some basic validations first, and collect those errors in ERRTAB and set the status to 51. for manual reprocessing of the IDOC, it doesnt care about those pre validations, and goes directly into VA01 processing -
Reg : SAP EDI/ALE or GIS 3.1 or 4.0 related information
Hi floks,
I need SAP EDI/ALE or GIS 3.1 or 4.0 related information Related links or documents Sent to me .mail Address [email protected] if any body work on this can u suggest me how to process idoc from sap to GIS few steps.
thanking you,
sureshAn AS Java is running if you have at least three "jlaunch" processes.
You can also do (as user <sid>adm)
cdpro
jcmon pf=<instance-profile>
20
Dispatcher, server and SDM should run.
Markus -
Send Wire information to Bank through EDI
Hello All,
I am trying to generate a file that will be send to the disbursement bank to wire money to our suppliers. This file will be generated by Payment batch and send to the back via EDI.
Can we use standard EDI outbound process to format this payments.
Any help will be appreciated.
Thank you
AshishPlease clarify what search has been done before posting the question.
If you know the EDI transmission number then simply typing in Google 'EDI <#> IDoc' finds all the information needed.
Maybe you are looking for
-
How do I find out the name if I on;y have a technical ID
I have a tech id but I do not know what object this refers to. Is there a way to find this
-
Mailbox size increased after removing attachments
Doing a little clean-up on my mail, I noticed my sent mailbox was 1.23 gigs. So, I went in saved several hundred attachments and then tried to remove attachments. It would only let me remove attachments about 5 messages at a time, so I moved over 300
-
How to get larger images in albums?
I just realized that when you click on a thumbnail in one of my albums, the larger image is actually smaller than the original photo! All the photos I've put into my web albums have been shrunk to fit into the album display area. For instance, a phot
-
how many MB iOS 7.0.2 takes, if i am downloading it from PC
-
IDocs have disappeared between ECC and PI
Hi All, A couple of days ago 3 idocs went missing between ECC and PI. That day 293 idocs of the same message type were sent to the same partner through PI. In PI we only found 290. The 3 IDocs were sent in the same second in the early afternoon. All