Restricting SRM attachments

Hi
we are trying to restrict attachments to shopping carts/PO's by file size and to specific file types.
Is there a badi that can raise an error when loading attachments for programable criteria
or
is there an area of config that controls this
thanks

Hi,
I think you can do this in BBP_DOC_CHECK_BADI.....
Call BBP_PD_SC_GETDETAIL in the function module using the guid and in the export parameters there is a table called ET_ATTACH. You can see all the details of the file in this table.
Hope this helps.
Regards,
Zubair

Similar Messages

Restrict email attachments if more than 1mb for internal and 250kb for external emails

Hi,
Restrict email attachments if more than 1mb for internal and 250kb for external emails ?
Can any one help me in this issue
Thanks
Deepan.T

Hi Deepan,
You can use transport rule to restrict the attachment size.
I use the following transport rule to reject the attachment size over 2MB with "5.7.1" information returned.
New-TransportRule "block large attach" -AttachmentSizeOver 2MB -RejectMessageEnhancedStatusCode "5.7.1"
For more information, here is an article for your reference.
New-TransportRule
http://technet.microsoft.com/en-us/library/bb125138(v=exchg.141).aspx
Hope it helps.
Best regards,
Amy
Amy Wang
TechNet Community Support

Restrict GOS attachments in IW32 for specific doc type

My requirement is we would like to restrict the Services for object
attachments for specific doc type in IW32 transaction.
Can blocking be made on doc type level?
In this case jpg, bmp, and gif should be allowed, but blocking dwg, doc, xls, pdf etc.
Didn't find any option in SGOS transaction or SGOSATTR table.
Any suggestions are welcome..

PARAMETERS: p_key TYPE swo_typeid OBLIGATORY,
p_type TYPE swo_objtyp OBLIGATORY,
p_file TYPE c LENGTH 100 OBLIGATORY,
p_desc TYPE so_obj_des OBLIGATORY.
data wa_kan1 type kna1.
DATA: ls_fol_id TYPE soodk,
ls_obj_id TYPE soodk,
ls_obj_data TYPE sood1,
ls_folmem_k TYPE sofmk,
ls_note TYPE borident,
ls_object TYPE borident,
lv_ep_note TYPE borident-objkey,
lv_offset TYPE i.
DATA: it_objhead TYPE STANDARD TABLE OF soli,
it_content LIKE STANDARD TABLE OF soli,
wa_content LIKE soli.
ls_object-objkey = p_key.
ls_object-objtype = p_type.
**if objtype = kna1 then
HERE I CHEK CUSTOMER NO U PUT YOUR OBJ ID AND USING SELECT QUERY U CAN CHECK DOC.TYPE
select *from kna1 into wa_kna1
where kunnr = p_key
if sy-subrc <> 0.
exit.
endif.
TRY.
OPEN DATASET p_file FOR INPUT IN BINARY MODE.
WHILE sy-subrc = 0.
READ DATASET p_file INTO wa_content.
APPEND wa_content TO it_content.
ENDWHILE.
CLOSE DATASET p_file.
CATCH cx_sy_file_access_error.
MESSAGE 'Error reading file' TYPE 'E'.
ENDTRY.
CALL FUNCTION 'SO_CONVERT_CONTENTS_BIN'
EXPORTING
it_contents_bin = it_content[]
IMPORTING
et_contents_bin = it_content[].
Edited by: kk.adhvaryu on Mar 9, 2010 10:54 AM

Restricting SRM confirmations to select PO types

Hi all,
We are on SRM 7 , ECS scenario.
We have single SC type but have created different PO types in SRM , and used BADI to convert SC to different PO type , like consumable PO, service PO, etc, based on some logic.
Now we want all the requisitioners to do the SRM confirmation only for service PO , not for consumable PO , and other PO. How can we achive this ?
Rgds
Sumendra

Hi Sumendra,
This can be easy.
Pl implement BBP_DOC_CHECK_BADI, where you can throw an error if user selects PO from any other PO type.
Best regards,
Ramki

SRM attachments transferred to ECC?

Hi all,
Can anyone confirm if the attachment from PO in SRM(ECS) are replicated to ECC PO with SRM 7.0 EHP1?

Hi,
It should be a standard functionality. If your backend ECC system is on ECC 6 enhancement pack 4 or higher, the transfer of attachment to backend system from SAP SRM system is standard one.
Thanks and regards,
Ranjan
Ranjan Sutradhar

SRM 7.0 extended classic - attachments to backend

Hi,
We are in SRM 7.0 and have a requirement to store SRM attachments in the backend ERP.
This is for the extended scenario going through Badi BBP_ECS_PO_OUT.
Has anyone got a solution for moving the attachments to the backend?
Kind regards,
Alexander

Hi,
The purchase order in the Extended Classic Scenario is transferred to the backend system with different Function Modules. The
attachment transfer logic was only implemented in the Classic Scenario.
One reason for this decision was, that the leading Purchase Order in the extended classic scenario is the local one, and in the local purchase order the attachments are available.
At the moment it is not planned to support the attachment transfer in the Extended Classic Scenario. The transfer of attachments to backend PO is developed only for Classic Scenario.
I am sorry that this is not the result that you wanted. This also explains why in the ECS PO transfer BADI BBP_ECS_PO_OUT_BADI does not have the parameters for attachments where as the Classic PO transfer
BADI does (BBP_CREATE_BE_PO_NEW).
We have some notes related to SC and POR reporting issues when transferring attachments to ECC side, but ther are related to Classic scenario:
1400088: SC attachments transferred to ECC PR are lost on EHP upgrade
1413792 Attachment deleted after changing purchase order
Ihope this information help you to understand this issue,
Kind Regards,
Rafael Rhoden

Attachments with KPRO / Content Server

Hello,
I am trying to store Shopping Cart's attachment in KPro using Archive Link on SRM 5.0 and ECC 6.0.
Here find what I did:
1. I created my Content Repository ZA (CSADMIN & OAC0) - All is green
2. I created a new Global Document ZBBPATT in TCODE OAC2.
3. I created the link between my document, the object type and the content repository as follow: ZBUS2121 | ZBBPATT | X | ZA | TOA03
But when I created a SC my attachment is store somewhere but not in CS.
What's wrong ? Did I miss something? - it seams yes
Next step is to transfer the SC in ECC.
Thanks
Regards
Chris

Please check this out
http://help.sap.com/saphelp_erp2005/helpdata/en/7a/973035624811d1949000a0c92f024a/frameset.htm
also
Configuring Attachment Transfer
Prerequisites
If you wish to store shopping cart attachments in the backend system, you must first activate the data transfer by creating an active method in the BAdIs BBP_CREATE_BE_PO_NEW (for purchase orders) or BBP_CREATE_BE_RQ_NEW (for purchase requisitions).
For more information, see the Implementation Guide (IMG) for Supplier Relationship Management: SRM Server ®Business Add-Ins (BAdIs) ® Follow-On Document Generation in the Backend-System ® Purchase Order in Backend System.
Or choose SRM Server ® Business Add-Ins (BAdIs) ® Follow-On Document Generation in the Backend-System ® Purchase Requisition in Backend-System.
Procedure
You have to configure the R/3 Document Management System (DMS) in transaction DC10:
       1.      Create document type SRM. Note that no flag is set in any of the columns.
       2.      Double-click in the detail view to define the new Doc. type desc. = SRM Documents. Set the Use KPro indicator.
¡        Enter 1 in the Number assignment field.
¡        Enter an internal number range interval. You can use an existing interval or create a new one in transaction CV90. The internal number range must be used, because the GUID of the SRM attachments has more digits than the number in the backend system.
¡        Maintain the number exit. The number exit is a program exit for document numbers. It controls number assignment and version numbering for documents. The default setting is MCDOKZNR. If you want to control the number assignment or the version increment via a USER_EXIT, then you have to replace the program MCDOKZNRwith a company-specific program. You can find further information in the field help for number exit.
¡        In the screen area Field selection, enter u2013 in the Document Status field.
       3.      Go to the dialog structure and double-click the entry Define object links. Define the new object links EKPO and EBAN. Maintain object link descriptions for EKPO (Purchase order item; Scr.no. 248) and EBAN (Purchase req. item; Scr. no. 247)
       4.      Define the workstation application in transaction DC30.
All required file types should be included in this list.

Exhange mail on iPhone5 - Cannot send attachments, only view

I have recently switched from BB to iPhone5....As per our Corporate Exchange server policy, there is No Restriction on attachments...I was able to send the same via BB and even today my firends on Android & MS phones are able to do so....in my case after configuring my exchange credentials in the default app, I am able to send & receive mails, view & forward attachments BUT Cannot send attachments to any New Mail or Reply Mail....
Please help in the same
Thanks
Atin

When I click "Reply" or "New Message", i do not get any icon for ading an attachment.
But when I am in separate app like "Photo" or "Adobe Reader", I am able to select the file and choose sent as mail.

Attachment transfer from SC to PO

Hi Everyone,
We have a requirement of transferring the attchments attched in SC to the PO or PR, i.e. to follow-on documents being created.
We are using SRM 7.0. Can anyone pls guide what are th steps for that. Is it a customization or we need to customize via a BADI.
I have found out that the documents can be transferred to PO from SC using DMS. Does anyone have a guide or document that can help me to configure the steps for the same???
Pls help.
Thanks & Regards,
Bhakti
Edited by: bhakti joshi on Aug 26, 2010 1:08 PM

Hi Jagadish,
you must configure the R/3 Document Management System (DMS) in transaction
DC10:
1. Create document type SRM. Note that no flag is set in any of the columns.
2. Double click in the detail view to define the new Doc. type desc. = SRM Documents.
Set the Use KPro indicator.
Enter 1 in the Number assignment field.
Enter an internal number range interval. You can use an existing interval or
create a new one in transaction CV90. The internal number range must be used,
because the GUID of the SRM attachments has more digits than the number in
the backend system.
Maintain the number exit. The number exit is a program exit for document
number. It controls number assignment and version numbering for documents.
The default setting is MCDOKZNR. If you want to control the number assignment
or the version increment via a USER_EXIT, then you have to replace the
program MCDOKZNR with a company-specific program. You can find further
information in the field help for number exit.
In the screen area Field selection enter in the field Document Status.
3. Go to the Dialog Structure and double-click on the entry Define object links. Define the
new object links EKPO and EBAN. Maintain object link descriptions for EKPO
(Purchase order item; Scr.no. 248) and EBAN (Purchase req. item; Scr. no. 247)
4. Define the workstation application in transaction DC30.
All required file types should be included in this list.
5. Activate Document Transfer
SPRO> Integration with other mySAP.com Components> Supplier Relationship Managemen> Message Control> Activate Document Transfer --> Execute
6. Assign the Document Type Define earlier and the Category to the Object type ex: BUS2012 (PO)
Ensure that you maintain a relation between BUS Object/ DMS Document Type/ Category.
Note: Check XML Monitor, make sure the attachment exist in Binary format.
Let me know if any questions!
Thanks
- netaji Gummadi

Content Repository vs Archive Link

We are using a third party content repository to store SRM attachments. We configured this through OACT OAC0 transactions. We are able to send attachments and retrieve from this content management system fine.
However, when the Content Repository is down for maintenance, if attachments are made in SRM, they are getting lost. Is there a way to queue up the failed attachments and reprocess?
Thanks,
SG

Hello,
You can achieve it with small alteration in your current program.
In transaction OAC0 you will be mentioning Physical & basic path.... This basic path will help in staging the attachment till your archive server is up-running.
It is not advisable to do any changes with current functionality of storing attachment but instead you can do all the maintanence activities at archive server (content repository) during off peak hours or weekends. Any activities at archive server will not take much time so you can plan to have it during off peak hours or weekends.
Hope your question is answered.
-Thanks,
Ajay

HT1338 Can't get many videos sent by email. Get movie format not recognized. Went to Tell me more, but don't understand the instructions.

Help me get videos and movies on my MacBook?

Hi Peter MacGregor,
That is odd, is there a restriction on attachments in the mail client?
View > View Attachments Inline?
Matt's blog is pretty awesome: [http://thunderbirdtweaks.blogspot.com/2011/07/file-attachments-in-thunderbird.html]
[http://forums.mozillazine.org/viewtopic.php?f=39&t=710775]

Attachment transfer from EBP V 5.0 to Backend SAP R/3

Hi,
We are going to activate the above functionality for our Classic Scenarion of implementation. In this regard,could anybody of you answer to my below given points in order to start working upon this and if possible ,please send the step wise implementaion of the functionality i.e. Transfer of Attachments in EBP V5.
Need to define the following:
1.How is the attachment sent to the suppliers? As a pdf document? Or an attachment in the mail?
2.How do we handle attachments to integrated suppliers?
3.What formats are applicable in the attachment? (.xls, .doc, .ppt, .mpp, other?)
4.How are attachments stored? In EBP? In SAP?
Thanks in advance.
Pranab

Hi
Which SRM version are you using ?
Help link To setup attachmnets in SRM
http://help.sap.com/saphelp_srm50/helpdata/en/f7/92dd3e6ecb1f39e10000000a114084/frameset.htm
1.How is the attachment sent to the suppliers? As a pdf document? Or an attachment in the mail?
Ans - Attachment can be in any format depending on SPRO settings (generally pdf documents).
2.How do we handle attachments to integrated suppliers?
Ans - See the links above and below
Q3.What formats are applicable in the attachment? (.xls, .doc, .ppt, .mpp, other?)
Ans - Any valid format defined in the system. See the links above and below
Q4.How are attachments stored? In EBP? In SAP?
Ans - In EBP system, attachments are stored on Application server.
Please go through other relevant details ->
Document for all type/extn can be stored provided their extension is mentioned in DC10 and DC30. And they are stored on Application server.
Transaction codes
DC10 - create a Document type for SRM
DC30 - Maintain all relevant extensions
In order to store shopping cart attachments in the backend system, you must first activate the transfer by creating an active method and by setting the indicator for parameter in BAdI .
Then you must configure the R/3 Document Management System (DMS) in transaction DC10:
Steps ->
1. Create document type SRM. Note that no flag is set in any of the columns.
2. Double click in the detail view to define the new Doc. type desc. = SRM Documents.
Set the Use KPro indicator.
Enter 1 in the Number assignment field.
Enter an internal number range interval. You can use an existing interval or
create a new one in transaction CV90. The internal number range must be used,
because the GUID of the SRM attachments has more digits than the number in
the backend system.
Maintain the number exit. The number exit is a program exit for document
number. It controls number assignment and version numbering for documents.
The default setting is MCDOKZNR. If you want to control the number assignment
or the version increment via a USER_EXIT, then you have to replace the
program MCDOKZNR with a company-specific program. You can find further
information in the field help for number exit.
In the screen area Field selection enter in the field Document Status.
3. Go to the Dialog Structure and double-click on the entry Define object links. Define the
new object links EKPO and EBAN. Maintain object link descriptions for EKPO
(Purchase order item; Scr.no. 248) and EBAN (Purchase req. item; Scr. no. 247)
4. Define the workstation application in transaction DC30.
All required file types should be included in this list.
Transferring Attachments (optional)
This is offered in SPRO itself. You can set up Web servers for exchanging documents. To do this you can define the following types of publishing:
Publishing Internally
This is the exchange of documents between systems that belong to your own area of responsibility (intranet).
Publishing externally
This is the exchange of documents with partners who should be given external access (from the extranet) to their own data.
If the publishing settings for external and internal access are identical, you can use a single Web server for exchanging data.
SPRO->Supplier Relationship Management->SRM Server->Define Setting for Attachments.
Related links ->
Re: Sending attachments from SRM to SAP Purchase Requisition
Re: redirect the shopping cart attachment from ebp doc server to file net serve
Re: Attachments in PR and PO
Re: Storing attachments
Re: Set up attachments for Purchasing docs
Re: Bringing attachments over to R3
http://help.sap.com/saphelp_nw04/helpdata/en/d6/205cfcc3b6bd44842866b2945dd869/content.htm
Internal & External Attachments
Re: Documents attachments in scenario standalone
Do let me know.
Regards
- Atul

Setup email account for my mother

I want to setup a email account for my mother on my broadband package. Can I do it, and how. Thanks
Solved!
Go to Solution.

There are other good sites for email, accessible anywhere and with plenty of gizmos, few restrictions on attachments and usage
www.mail.com
googlemail
www.gmx.com
to name but a few.
Hilary

Size limits Internally

Is there away to setup restriction of attachments internally between users?

On Fri, 18 Jul 2008 15:46:02 +0000, rdrucker wrote:
> Is there away to setup restriction of attachments internally between
> users?
Between GW domains, yes, via the link configuration between the domains.
Between users on the same PO? No.
Joe Marton
Novell Support Forum SysOp
Novell does not officially monitor these forums!
http://forums.novell.com/

Restricted access to attachments in SRM 7.0 web applications

Hi,
We have a very specific problem regarding the handling of attachments with SRM 7.0 web applications. The system is configured to use ArchiveLink for storing documents on a remote content server, which is working fine.
Now we have a requirement which should restrict access to certain documents to specific user groups. As an example you could say that a Purchase order has (besides others) two documents attached, e.g.
- signed contract
- meeting minutes
The contract should only be visible to a limited number of people, whereas the Meeting Minutes are accessible to everybody.
Our problem is that apparently only one Content Category ("BBPFILESYS") is used by the SRM web applications for an upload. When granting authorizations on this content category, we cannot distinguish between contracts and meeting minutes anymore.
Comparing this with the config in ECC we can freely define document types which can be used in AUTH profiles. Is there any similar solution that can be used in SRM 7.0?
Any help would be greatly appreciated.
Cheers,
Mark

Hello,
Have a look at note 1334202. It provides some inputs.
Regards,
Ricardo

Restricting SRM attachments

Similar Messages

Maybe you are looking for