TRANSMISSION MEDIUM AND FORM ROUTINE IN CASE OF NACE TRANSACTION

While saving a invoice, I have created a routine which will pick an output type when a certain condition is met.
A custom report (Zprogram) needs to be triggered automatically during this invoice save. So we need to attach this Zprogram to output type.
Could anybody tell me the transmission medium to be selected and also what needs to be entered in the field Form routine for this program which I have created in the transaction NACE->V3(Billing)->Output types->Processing routines?
Thanks in advance.

HI Shah,
Form routine is nothing but a sub routine in your Z program (Driver Program). Simply one driver program can be used in multiple Layouts by using Form routines. If you are using the driver program only for one layout, then the routine declaration is not necessary.
Simply select the transmission medium as Print out in case of print. Special function means whether you want trigger this form for only Bill-to-party or Ship-to-party etc.. I hope you need to maintain as SH or BP, check with your functional people once.
You can check the below link for further customization reference.
Link: [output type configuration;
You can check the below link to know the exact meaning for Form routine.
Link: [https://forums.sdn.sap.com/click.jspa?searchID=13772541&messageID=5319599]
Regards,
Raghu..

Similar Messages

TRANSMISSION MEDIUM IN CASE OF NACE TRANSACTION

When do we use transmission medium as special function in case of NACE transaction?

HI Shah,
Form routine is nothing but a sub routine in your Z program (Driver Program). Simply one driver program can be used in multiple Layouts by using Form routines. If you are using the driver program only for one layout, then the routine declaration is not necessary.
Simply select the transmission medium as Print out in case of print. Special function means whether you want trigger this form for only Bill-to-party or Ship-to-party etc.. I hope you need to maintain as SH or BP, check with your functional people once.
You can check the below link for further customization reference.
Link: [output type configuration;
You can check the below link to know the exact meaning for Form routine.
Link: [https://forums.sdn.sap.com/click.jspa?searchID=13772541&messageID=5319599]
Regards,
Raghu..

Please explain what are form groups and form routines

Hello ABAP Experts,
Could you please explain what are form groups and form routines? I would certainly appreciate some examples.
Thank you in advance, Aleksandra

Hi,
I've found the Form Group in transaction J7LE. It is part of Industry Specific solution for hi tech companies, so I'm not sure if you'll be able to access it. In this tcode you define master data of your partner. The first step is to choose the Form Group - they simply group Form Routines. Depending on which one I choose, different entry fields get activated. However there are routines that will enable input to the same fields, so I suppose there must be some additional functionality behind it. Could you please specify what does it mean?
>>Form ROUTINES, are subroutines for modularizing your code<<
I'm afraid I have no ABAP experience at all...
Cheers, A.

Right transmission medium and communication in output determination

Hello Gurus,
I defined a new output type for shipping, wrote a requirement, but I don't know which transmission medium should I define in the output type and the right communication definition in the condition records.
I need this output to execute a program that calls a "proxy to file" method (interface).
Each transmission medium I used caused me a dump, so eather the program the ABAPer gave me is wrong, or my definition is wrong.
Regards,
Daphna

Apologies for previous response.
General for these kind of requirement. it could be either 1-Send with periodically scheduled job & 2-Send with job, with additional time specification as Dispatch time with either 5(External Send) or 6(EDI) or 7(simple mail) as Transmission Medium.
Don't forget to maintain relevant communication strategy, say, WEBM-Send external mail in communication method.
Regards
JP

Use of us_screen in the form routine : FORM entry USING retcode us_screen

Hello All,
I have one print program entry routine as below.
FORM entry USING retcode us_screen.
Some code to print the form data...
EndForm.
When i Check the value of us_screen in the debuging, its value is coming as blank.
When i checked the other form routine the value of us_screen is coming as 'X.
I am my getting why in my case value of us_screen is coming as blank.
What is significant of this field.
Thanks & Regards
Sachin Yadav

Cusomization might be missing for that output type in transaction NACE.
us_screen is blank because below query fails due to missing entry in table TNAPR.
SELECT SINGLE * FROM TNAPR WHERE KSCHL = P_KSCHL
AND NACHA = P_NACHA
AND KAPPL = P_KAPPL.
First assign the output type with a Transmission medium, Program, Form Routine, Form in transaction NACE
Take the help of your functional consultant.

How to send Mail in case of Output Determination - Transmission medium 5

Dear Friends,
I have a below requirement.
- Create custom output type having Transmission medium 5, which triggers on creation of order.
- Write driver program attached to that output type that sends e-mail to the person who has created the order.
- Mail contain information regarding pricing for individual line item wise.
I have gone through many posts but not sure about process of generate the mail in case of Transmission medium 5.
My query is:
Do we require to write FM (SO_NEW_DOCUMENT_ATT_SEND_API1) to send e-mail to respective person or it will take care by system (Transmission medium 5)?
If FM not required then how can we write code that triggers the mail to specific mail ID?
Nilay

Yes, for your custom requirement you will have to create a Z report.
LIke your requirement must be to put something specific in mail body or attach something with mail. All this will not be catered by the standard report maintained against your output type and transmission medium.
As i understand for any output type a message is triggerd and stored in database table (like NAST) and then these requests are picked by standard report (like RSNAST00). These reports then in return call the Program/form maintained against the ouptut type and transmission medium (table TNAPR).
So i would suggest that create a custom report and use the FM for sending mails. These FMs are pretty simple to use. Find a sample code in the below link:
[http://wiki.sdn.sap.com/wiki/display/ABAP/SendExternalMailwithattachment]

Form routine for ALE medium

Hi
can anyone tell me
whats the processing routine used for medium ALE.
is it ::logsys or ALE_PROCESSING for program RNASTED.
thanks
its very urgent, pls help me in rectifying it soon

Hi,
R/3 Side:
1. SM59 - Create & test RFC Configuration
2. WE21 - Create a tRFC Port in R/3 & give the RFC destination(logical name of XI)
3. WE20 - Create the partner profile for the partner type LS. Add the Outbound parameters, Message Type ORDERS, give the above created Receiver Port(tRFC).
4. Output Mode-choose radio button Transfer Idoc Immed.
5. Give the IDoc type - ORDERS05 (for version ECC 6.0).
XI Side:
1. SM59 - Create & test RFC Configuration
2. T.Code-IDX1, create the port, give R/3 client, give R/3 logical system as RFC Destination.
3. T.Code-IDX2, add the IDoc ORDERS05, for the above port.
R/3 Side:
1. Check in T.Code NACE, for output type NEU, for Medium, A Distribution ALE, Program RSNASTED & Form Routine ALE_PROCESSING is mentioned or not.
2. Create a PO in ME21N, before saving, in Messages, select the output type NEU, for Medium A, in further data, selct send immed.when saving, then SAVE the PO.
3. WE05 - Observe the created IDoc & the control record.
XI Side:
1. Create a scenario for imported IDoc-ORDERS05. Activate.
1. IDX5 - Check XML Messages
Regards,
Balaji

Transmission Medium 5 with one time customer..

Hi there, I have sent email from a smartform using a Z print program where I do all the coding to make the email go out. I really want to know how to use transmission medium 5 to do the same without making a Z print program and coding it all. SAP standard functionality allows this but I have seen many references of having to enter the email address on the customer master but in our case we are using a "one time Customer" for these documents where you wouldnt update the customer master, the email address is saved at the document level.
My question is: Does SAP allow for the use of transmission medium 5 for these one time customers.. If so what needs to be done for it to work?
We have the output type set up as 5, a print program and a smartform all ready.
Thanks In Advance .
TonyC

Hi,
To maintain addresses of the email you can maintain it in ADR6-SMTP_ADDR.You can fetch this address based on the addrnumber

Output - Transmission Medium - Special Function

Hi
In SD Billing output, Transmission Medium used as 8.Special Function. This is sending information to Oracle(Legacy). Now we need to make some changes in output. But, in tcode:NACE, there is no print program or form assigned to this output type. In table:TNAPR also, no program displayed.
Please provide info on how/where print program assign to output type for special functions. Or which program sends output/data to legacy
Regards
Uma

Hi,
I have small idea.I hope this will help you in identifying the program you want.
First goto VF02.Enter your billing document number.
Click on billing document-->Issue output to.
Selectyour output type.Goto Print preview.
press /h.Debugging will be switched on.
Double click on that message.
Click on break points.Select Break point at-->Breakpoint at statement.
Mention call function and press Enter.Press F8 and check for "CALL FUNCTION 'SSF_FUNCTION_MODULE_NAME'".
In this check for gv_fomname.
Get it.Goto SE16.Enter the table name as "TNAPR".
Enter this form name here and get the program name.
Please do this with the help of your ABAPer.
Reagrds,
Krishna.

Output - Transmission Medium 8 - Special Function Issue

Hi Experts,
I have created a Z-program and smartform fro Invoice print. This smartform should print based on the Output Type ZPDF. We have configured the program and the smartform in NACE for the Output type.
In Billing Header Output, Transmission Medium used as 8.Special Function is maintained for the Output type ZPDF.
But this Output type (ZPDF) is not getting reflected when i try to select it from the billing Tcode : VF03.
VF03-> Billing Document -> Issue Output to
Kindly guide.
Regards
Gopa

Hi Deepti,
Thanks a lot for you reply.
In my case the dispatch time(NAST-VSZTP) is getting updated as 1. And this value is getting updted into NAST table from Transparent Table T685B.
SAPDV70A                       / DV70AI0D
MODULE (PAI)    / D0100_PRUEFEN
MODULE D0100_PRUEFEN.
IF NAST-VSZTP = SPACE.
    NAST-VSZTP = T685B-VSZTP.
ENDIF.
How to proceed in this case. Can you plz suggest.
Regards
Gopa

Message transmission medium

Hello Friends,
Can you please tell me the procedure to achieve this.
How can you determine the message transmission medium while the
requirement subroutine (Requirements Output Control T-Code VOFM ) is running.
FORM KOBED_601.
get message transmission medium
ENDFORM.
FORM KOBEV_601.
get message transmission medium
ENDFORM.
Regards
Marco M

I think you handle this by handling the subrc and the condition types.
Check the following thread.
Re: Output Control
Hope it helps.

Form Routines

Hi ABAP Gurus,
                         i am new to abap.i Have some small doubts.please explain me some doubts.please do explain me in simple words dont send links.
1. what is a FORM Routine?
2. what is importing ,Exporting?
3. what is the diff. b/w exporting & Returning?
4.what is changing?
5. what is returning ,receiving?
6.what is PERFORM Statement?
7.explain me about public,protected and private?
note:please do explain me these with simple coding so that i can be familiar to know where to use them.

Check this link -
http://www.geocities.com/rmtiwari/Resources/Utilities/ABAPReference/ABAPReference.html
PERFORM
Variants:
1. PERFORM form.
2. PERFORM form IN PROGRAM prog.
3. PERFORM n OF form1 form2 form3 ... .
4. PERFORM n ON COMMIT.
5. PERFORM n ON ROLLBACK.
6. PERFORM form(prog).
Variant 1
PERFORM form.
Extras:
1. ... USING    p1 p2 p3 ... 2. ... CHANGING p1 p2 p3 ...
3. ... TABLES   itab1 itab2 ...
Effect
Calls the subroutine form defined usng a FORM statement. After the subroutine has finished, processing continues after the PERFORM statement. The parameters of the subroutine are position parameters, and must be passed in the call according to the definition of the formal parameters in the corresponding FORM statement.
Example
PERFORM HELP_ME.
FORM HELP_ME.
ENDFORM.
The PERFORM statement calls the subroutine HELP_ME.
Note
Non-Catchable Exceptions:
PERFORM_PARAMETER_MISSING: The subroutine called has more parameters than you passed to it.
PERFORM_TOO_MANY_PARAMETERS: You passed more parameters to the subroutine than it was expecting.
PERFORM_CONFLICT_TYPE,
PERFORM_CONFLICT_TAB_TYPE,
PERFORM_STD_TAB_REQUIRED,
PERFORM_CONFLICT_GENERIC_TYPE,
PERFORM_BASE_WRONG_ALIGNMENT,
PERFORM_PARAMETER_TOO_SHORT,
PERFORM_CAST_DEEP_MISMATCH,
PERFORM_TABLE_REQUIRED: The type of a parameter did not correspond to the type specified in the FORM statement.
Addition 1
... USING    p1 p2 p3 ...
Addition 2
... CHANGING p1 p2 p3 ...
Effect
These two additions have an identical function. However, you should always use the same addition as is used in the corresponding FORM definition (for documentary reasons).
The statement passes the parameters p1 p2 p3 ... to the subroutine. A subroutine may have any number of parameters.
The order in which you list the parameters is crucial. The first parameter in the PERFORM statement is passed to the first formal parameter in the FORM defintion, the second to the second, and so on.
You can specify offset and length of a parameter as variables. If you use the addition ' ...USING p1+off(*)', the parameter p1 will be passed with the offset off, but the length will not exceed the total length of the field.
Example
DATA: NUMBER_I TYPE I VALUE 5,
      NUMBER_P TYPE P VALUE 4,
      BEGIN OF PERSON,
        NAME(10)      VALUE 'Paul',
        AGE TYPE I    VALUE 28,
      END   OF PERSON,
      ALPHA(10)       VALUE 'abcdefghij'.
FIELD-SYMBOLS <POINTER> TYPE ANY.
ASSIGN NUMBER_P TO <POINTER>.
PERFORM CHANGE USING 1
                     NUMBER_I
                     NUMBER_P
                     <POINTER>
                     PERSON
                     ALPHA+NUMBER_I(<POINTER>).
FORM CHANGE USING VALUE(PAR_1)
                  PAR_NUMBER_I
                  PAR_NUMBER_P
                  PAR_POINTER
                  PAR_PERSON STRUCTURE PERSON
                  PAR_PART_OF_ALPHA.
ADD PAR_1 TO PAR_NUMBER_I.
PAR_NUMBER_P = 0.
PAR_PERSON-NAME+4(1) = ALPHA.
PAR_PERSON-AGE = NUMBER_P + 25.
ADD NUMBER_I TO PAR_POINTER.
PAR_PART_OF_ALPHA = SPACE.
ENDFORM.
Field contents after the PERFORM statement:
NUMBER_I    = 6
NUMBER_P    = 6
<POINTER>   = 6
PERSON-NAME = 'Paula'
PERSON-AGE = 25
ALPHA       = 'abcde    j'
Notes
   1. If you want to pass the body of an internal table itab that has a header line, you must use the notation itab[] (see Data Objects). If you do not use the brackets, the header line of the tabel is passed.
   2. The field types and lengths of the parameters remain the same. If a parameter is changed within the subroutine, it will still have the changed value after the subroutine has finished. This does not apply to parameters passed using VALUE. werden.
   3. If you pass literals, they may not be changed unless you pass them to a formal parameter defined with USING VALUE.
Addition 3
... TABLES itab1 itab2 ...
Effect
TABLES allows you to pass internal tables to a subroutine.
Example
TYPES: BEGIN OF ITAB_TYPE,
         TEXT(50),
         NUMBER TYPE I,
       END OF ITAB_TYPE.
DATA: ITAB TYPE STANDARD TABLE OF ITAB_TYPE WITH
                 NON-UNIQUE DEFAULT KEY INITIAL SIZE 100,
       BEGIN OF ITAB_LINE,
         TEXT(50),
         NUMBER TYPE I,
       END OF ITAB_LINE,
       STRUC like T005T.
PERFORM DISPLAY TABLES ITAB
                USING STRUC.
FORM DISPLAY TABLES PAR_ITAB STRUCTURE ITAB_LINE
             USING PAR      like      T005T.
DATA: LOC_COMPARE LIKE PAR_ITAB-TEXT.
WRITE: / PAR-LAND1, PAR-LANDX.
LOOP AT PAR_ITAB WHERE TEXT = LOC_COMPARE.
ENDLOOP.
ENDFORM.
Within the subroutine DISPLAY, you can use any internal table operation to work with the internal table that you passed to it.
Note
If you use TABLES, it must always be the first addition in a PERFORM statement.
Variant 2
PERFORM form IN PROGRAM prog.
Extras:
1. ... USING    p1 p2 p3 ... 2. ... CHANGING p1 p2 p3 ...
3. ... TABLES   itab1 itab2 ...
4. ... IF FOUND
Passsing SY-REPID not allowed and Receiving SY-SUBRC not allowed.
Effect
This variant is similar to variant 2 (external perform). However, here you can specify the names of both the subroutine and the program in which it occurs dynamically at runtime. If you do this, you should place the variables form and prog in parentheses. The names in form and prog must be entered in uppercase, otherwise a runtime error occurs. If you do not specify any additions (such as USING) you do not need to specify the program after IN PROGRAM. In this case, the system looks for the subroutine in the current program.
Example
DATA: RNAME(30) VALUE 'WRITE_STATISTIC',   "Form and program
                                           "names must
      PNAME(8) VALUE 'ZYX_STAT'.          "be written in
                                           "upper case
PERFORM (RNAME)         IN PROGRAM ZYX_STAT.
PERFORM WRITE_STATISTIC IN PROGRAM (PNAME).
PERFORM (RNAME)         IN PROGRAM (PNAME).
All three PERFORM statements have the same effect, that is, they call the subroutine 'WRITE_STATISTIC', which is defined in the program 'ZYX_STAT'.
Notes
Dynamic PERFORM statements require more CPU time, since the system has to locate the subroutine each time.
Note
Non-Catchable Exceptions:
PERFORM_NOT_FOUND: Unable to find the specified subroutine.
LOAD_PROGRAM_NOT_FOUND: Unable to find the specified main program.
PERFORM_PROGRAM_NAME_TOO_LONG: The specified program cannot exist because the program name is longer than 40 characters.
Addition 1
... USING p1 p2 p3 ...
Effect
See variant 1, addition 1.
Addition 2
... CHANGING p1 p2 p3 ...
Effect
See variant 1, addition 2.
Addition 3
... TABLES itab1 itab2 ...
Effect
See variant 1, addition 3.
Addition 4
... IF FOUND
Effect
The system only calls the subroutine if it and its main program exist. If this is not the case, the statement is ignored.
Variant 3
PERFORM n OF form1 form2 form3 ... .
Effect
Calls the subroutine with the index n from the list of subroutines in the statement. At runtime, n must contain a value between 1 (first name) and the total number of subroutines listed in the PERFORM statement (last name). The list can contain up to 256 subroutines.
Note
Non-Catchable Exceptions:
PERFORM_INDEX_0: The specified index was too small.
PERFORM_INDEX_NEGATIVE: The specified index was negative.
PERFORM_INDEX_TOO_LARGE: The specified index was too big.
Variant 4
PERFORM n ON COMMIT.
Extras:
1. ... LEVEL idx
Effect
Calls the specified subroutine at the next COMMIT WORK statement. This allows you to delay the subroutine until the logical transaction is finished. Even if you register the same subroutine more than once, it is only executed once. For further information, refer to COMMIT WORK. The ROLLBACK WORK statement deregisters all subroutines registered using this addition.
Notes
   1. You cannot use USING or CHANGING with the ... ON COMMIT addition. If you need to pass data to the subroutine, you must place it in global variables or use the EXPORT ... TO MEMORYstatement.
   2. The PERFORM ... ON COMMIT statement can also be used during update. The corresponding subroutine is called at the end of the update task.
Addition 1
... LEVEL idx
Effect
The LEVEL addition, followed by a field, determines the sequence in which the specified subroutines will be executed at the COMMIT WORK statement. The subroutines are called in ascending order of their level. If you do not use the LEVEL addition, the subroutine assumes the level zero. If two or more subroutines have the same level, they are executed in the sequence in which they are called in the program. You assign levels by defining constants in an include program. The level must have type I.
Variant 5
PERFORM n ON ROLLBACK.
Effect
The specified subroutine is executed if a ROLLBACK WORK occurs. This allows you, for example, to delete data, such as an internal table or data in memory, that was intended for use in PERFORM...ON COMMIT. If you register the same subroutine more than once, it will still only be executed once per ROLLBACK WORK.
Notes
   1. Subroutines registered using PERFORM... ON COMMIT cannot have USING or CHANGING parameters. Any data you want to pass to them must be contained in global variables or buffered using EXPORT ... TO MEMORY.
   2. If you catch a type A message ( MESSAGE) using the EXCEPTIONS..ERROR_MESSAGE addition in the CALL FUNCTION statement, a ROLLBACK WORK occurs, in which the subroutines registered using PERFORM ... ON ROLLBACK are executed.
Variant 6
PERFORM form(prog).
Extras:
1. ... USING    p1 p2 p3 ... 2. ... CHANGING p1 p2 p3 ...
3. ... TABLES   itab1 itab2 ...
4. ... IF FOUND
PERFORM form(prog) not allowed.
Effect
Calls the subroutine form defined in program prog ("external PERFORM").
Notes
   1. You pass parameters to the external subroutine as described in variant 1.
   2. However, you can also do it using a shared data area ( DATA BEGIN OF COMMON PART).
   3. Please consult Data Area and Modularization Unit Organization documentation as well.
   4. You can use nested calls, including several different subroutines in different programs.
   5. When you call a subroutine that belongs to a program prog, prog is loaded into the PXA buffer (if it has not been loaded already). To minimize the possibility of memory problems, try not to use too many external subroutines from a large number of different programs.
Hope this helps.
ashish

Difference between Start Routine and End Routine in Transformations

Hi Friends,
I'm using BI 7.0... here in Transformations step we have two options..that is START ROUTINE... and END ROUTINE... What is the Difference between Start Routine and End Routine in Transformations..
When we go for Start Routine.. and when we go for End Routine..
Plz clarrify... points will be rearded..
thanks
babu

Hi,
One real time scenario for End Routine.
We have a scenario where in a datasource field is mapped to three infoobjects on the datatarget side. There are 2 key figures which need to get data after these these Infoobjects are filled. The best place for this to happen would be in a End Routine, where in we would loop through the results package and using the values of the infoobjects from the data target ( Cube in this case).
Hope this helps,
HD

Design Time for Processes and Forms

Hi experts,
When trying to open "Design Time for Processes and Forms" in order to create a process, I get a dump.
Could you let me know what could be wrong ? config? etc..
Hereunder is a sample of what I found in T.code ST22
The following checkpoint group was used: "No checkpoint group specified"
If in the ASSERT statement the addition FIELDS was used, you can find
the content of the first 8 specified fields in the following overview:
" (not used) "
" (not used) "
" (not used) "
" (not used) "
" (not used) "
" (not used) "
" (not used) "
" (not used) "
    referenced node must exist
      READ TABLE object_hierarchy_nodes TRANSPORTING NO FIELDS
                 WITH KEY node_id = object_hierarchy_node_wa-ref_node_id
>>>      ASSERT sy-subrc = 0.
    ENDIF.
provider has to be specified (except in case of recursion)
    IF object_hierarchy_node_wa-ref_node_id IS INITIAL.
      ASSERT object_hierarchy_node_wa-provider_id IS NOT INITIAL.
    ENDIF.
Thanks in advance,
Louis

note: Note 1075650
Re: Assertion_Failed dump when accessing Design Time for Processes & Forms EP3
regards,
Prakesh.

Form routines in CRM down loaded from R/3 for pricing

Hi all,
we have the following scenario:
1) We have created an access sequence for tax condition in R/3 using standard form routines / requirements 7 (domestic) and 8 (export).
2) The cutsomizing and conditions are down loaded to CRM (4.0) and the prices are calculated using the IPC.
In R/3 the tax is determined correctly:
check: komk-aland = komk-land1 -> domestic tax is determined.
check: komk-aland ne komk-land1-> export tax is determined.
In VOFM (R/3) it is possible to see the ABAP code of the requirement and set break points to check how the access is fullfilled.
_Problem
In CRM domestic tax is determined even though sold-to and ship-to party have different country codes. The same scenario that determines export tax in R/3 determines domestic tax in CRM.
The pricing analysis in the transaction in CRM displays that the access is found and that requirement 7 is fullfilled which makes no sense.
Does any one know where to find the code of the requirement in CRM and make a similar analysis with break points as in R/3 to see how the fields of the access are filled and the requirements are checked ? In customizing and the IPC only the form routine number is displayed but the code is not visisble.
Thanks in advance,
/Annette

Hi Annette,
I do not know what version of CRM you are running but I assume it is > 4.0. In all circumstances we are talking Java IPC developments which are not as easy to debug as ABAP. I will refer you to OSS note 809820 for further info.
You can upload and download the Java devlopments to the CRM server in transaction /N/SAPCND/UE_DEV.
Debugging is unfortunately not as easy as in R/3. I have not done it myself but I think you have to install Eclipse or NWDS on your machine. And then it should be possible to link it to CRM.
There is some additional information here:
http://help.sap.com/saphelp_nw04s/helpdata/en/f7/928f9e77da4588b9bf5e65d73bd674/content.htm
But you definately need Java knowledge to do this
Br,
Anders

TRANSMISSION MEDIUM AND FORM ROUTINE IN CASE OF NACE TRANSACTION

Similar Messages

Maybe you are looking for